B 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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 theLIVE
workspace. - WM_ERROR_10 unique key violation
-
Cause: An insert operation failed because it violated the table's primary key constraint.
- 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. - 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. - 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. - 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.
- WM_ERROR_15 "/" is not allowed in a workspace name
-
Cause: CreateWorkspace failed because the workspace name contained a "/".
- WM_ERROR_16 "WM_ADMIN" system privilege is required to version disable a table in another schema
-
Cause: DisableVersioning failed because only a user with the
WM_ADMIN
system privilege can version-disable a table in another schema. - WM_ERROR_17 "WM_ADMIN" system privilege is required to version enable a table in another schema
-
Cause: EnableVersioning failed because only a user with the
WM_ADMIN
system privilege can version-enable a table in another schema. - WM_ERROR_18 "WM_ADMIN" system privilege or ownership is required to alter workspace attributes
-
Cause: AlterWorkspace failed because only a user with the
WM_ADMIN
system privilege or the owner of the workspace can alter workspace attributes. - WM_ERROR_19 "WM_ADMIN" system privilege or ownership is required to freeze a workspace
-
Cause: FreezeWorkspace failed because only a user with the
WM_ADMIN
system privilege or the owner of the workspace can freeze a workspace. - WM_ERROR_20 "WM_ADMIN" system privilege or ownership is required to set workspace lock mode
-
Cause: SetWorkspaceLockModeOn failed because only a user with the
WM_ADMIN
system privilege or the owner of the workspace can set the workspace lock mode. - WM_ERROR_21 insufficient privileges to change savepoint attributes
-
Cause: AlterSavepoint failed because only a user with the
WM_ADMIN
system privilege or the owner of the workspace or savepoint can alter the savepoint attributes. - WM_ERROR_22 insufficient privileges to delete savepoint
-
Cause: DeleteSavepoint failed because only a user with the
WM_ADMIN
system privilege or the owner of the workspace or savepoint can 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.
- 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.
- 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. TheLIVE
workspace is the root workspace in the workspace hierarchy tree. - 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. TheLIVE
workspace is the root workspace in the workspace hierarchy tree. - 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.
- 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.
- 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.
- 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.
- WM_ERROR_32 An index-organized table cannot be version enabled.
-
Cause: Workspace Manager does not support index-organized tables.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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. - 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.
- 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.
- WM_ERROR_41 unable to set workspace lock mode
-
Cause: SetWorkspaceLockModeOn failed because the workspace contained modifications from one or more version-enabled tables.
- WM_ERROR_42 cannot version enable tables owned by 'string'
-
Cause: EnableVersioning failed because Workspace Manager cannot version-enable tables owned by the specified user.
- 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.
- WM_ERROR_44 insufficient privileges to merge data
-
Cause: The merge operation failed because the user does not have both
ACCESS
andMERGE
privileges on the workspace on which it was invoked; or, in a multiparent workspace environment, the user does not have bothACCESS
andMERGE
privileges on the non-root workspaces andACCESS
privilege on the root workspace of the multiparent workspace graph. - 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. - WM_ERROR_46 commit/rollback open short transactions before calling CommitResolve
-
Cause: CommitResolve failed because open database transactions existed.
- WM_ERROR_47 commit/rollback open short transactions before calling CompressWorkspace
-
Cause: CompressWorkspace failed because open database transactions existed.
- WM_ERROR_48 commit/rollback open short transactions before calling CompressWorkspaceTree
-
Cause: CompressWorkspaceTree failed because open database transactions existed.
- WM_ERROR_49 commit/rollback open short transactions before calling DeleteSavepoint
-
Cause: DeleteSavepoint failed because open database transactions existed.
- WM_ERROR_50 commit/rollback open short transactions before calling GotoWorkspace
-
Cause: GotoWorkspace failed because open database transactions existed.
- WM_ERROR_51 commit/rollback open short transactions before calling RollbackResolve
-
Cause: RollbackResolve failed because open database transactions existed.
- WM_ERROR_52 CommitResolve can be called only after BeginResolve has been invoked
-
Cause: CommitResolve failed because BeginResolve was not previously invoked.
- WM_ERROR_53 CompressWorkspace operation requires ACCESS and MERGE privileges on the workspace
-
Cause: The operation invoked failed because it required both
ACCESS
andMERGE
privileges on the workspace on which it was invoked. - 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. - WM_ERROR_55 conflicts detected for workspace: 'string' in table: 'string'
-
Cause: An operation failed because there were conflicts detected for the table.
- WM_ERROR_56 conflicts detected for workspace: 'string' in table: 'string'.'string'
-
Cause: An operation failed because there were conflicts detected for the table.
- 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. - WM_ERROR_58 RemoveWorkspace operation requires ACCESS and REMOVE privileges on the workspace
-
Cause: The operation invoked failed because it required both
ACCESS
andREMOVE
privileges on the workspace on which it was invoked. - 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.
- WM_ERROR_60 user must call BeginResolve or have "WM_ADMIN" system privilege 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
system privilege. - 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.
- 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.
- 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. - 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. - 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.
- 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
orVIEW_W_OVERWRITE
option and the cumulative length of the names of the primary key columns was greater than 600. - 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.
- 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.
- 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. - 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- WM_ERROR_79 WM internal error ['string']
-
Cause: A Workspace Manager operation resulted in an internal error.
- WM_ERROR_80 invalid "hist" parameter for EnableVersioning
-
Cause: An invalid value was specified for the
hist
parameter of procedure EnableVersioning. - 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. - 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.
- WM_ERROR_83 invalid user specified for the freezewriter parameter
-
Cause: The FreezeWorkspace procedure was called with an invalid
freezewriter
parameter. - 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. - 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. - 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. - WM_ERROR_87 IsWorkspaceOccupied cannot be used for the 'string' workspace
-
Cause: A user attempted to invoke IsWorkspaceOccupied on the default 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. - 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 inNO_ACCESS
mode. Workspace Manager does not support this mode for theLIVE
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.
- 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.
- 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.
- 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. - WM_ERROR_94 non-existent versioned table: 'string'.'string'
-
Cause: This operation was invoked on a non-version-enabled table.
- 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.
- WM_ERROR_96 null workspace name passed in as input
-
Cause: A null value was passed in as input to a Workspace Manager operation
- WM_ERROR_97 null table name parameter passed in
-
Cause: MergeTable was invoked with a null table name.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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. - 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 the specified privilege on the child table.
- 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 the specified privilege on the child table.
- WM_ERROR_108 triggering event 'string' not allowed
-
Cause: A triggering event of the form "insert OR update OR delete" was specified.
- 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.
- WM_ERROR_112 insufficient privileges to refresh data
-
Cause: The refresh operation failed because the user does not have both
ACCESS
andMERGE
privileges on the child workspace on which it was invoked; or, in a multiparent workspace environment, the user does not have bothACCESS
andMERGE
privileges on the non-root workspaces andACCESS
privilege on the root workspace of the multiparent workspace graph. - 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. - 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. - WM_ERROR_115 ResolveConflicts can be called only after BeginResolve is invoked
-
Cause: The ResolveConflicts procedure was invoked without calling the BeginResolve procedure first.
- 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.
- WM_ERROR_117 RollbackResolve can be called only after BeginResolve has been invoked
-
Cause: RollbackResolve procedure was invoked without calling the BeginResolve procedure first.
- 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.
- 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-".
- 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.
- 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.
- 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.
- 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.
- WM_ERROR_124 workspace name may not be "BASE"
-
Cause: A user attempted to create a workspace with the name
BASE
. - WM_ERROR_125 workspace name may not be "LIVE"
-
Cause: A user attempted to create a workspace with the name
LIVE
. - 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.
- 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.
- 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.
- 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.
- 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.
- WM_ERROR_131 table 'string' is already version enabled
-
Cause: The specified table is already version-enabled.
- WM_ERROR_132 table 'string' is not version enabled
-
Cause: This operation can only be invoked on a version-enabled table.
- 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.
- 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.
- 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.
- 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, or to perform another action (such as an export from a staging table) where the table name was longer than 25 characters.
- 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.
- WM_ERROR_140 invalid value for FreezeMode parameter
-
Cause: An attempt was made to invoke the FreezeWorkspace procedure with an invalid
freezemode
parameter. - 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. - WM_ERROR_142 the keep parameter must be one of ("PARENT","CHILD","BASE")
-
Cause: The ResolveConflicts procedure was called with an invalid
keep
parameter. - 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 theLIVE
workspace. - WM_ERROR_144 the "LIVE" workspace cannot be merged
-
Cause: A user attempted to 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. - WM_ERROR_147 the "LIVE" workspace cannot be refreshed
-
Cause: A user attempted to 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.
- WM_ERROR_149 the lock mode must be one of ("C","D","E","S","VE","WE")
-
Cause: The user invoked a SetLockingON operation with an invalid
lockmode
parameter. - 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.
- 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.
- 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.
- WM_ERROR_153 the workspace: 'string' has savepoints in the branch specified
-
Cause: A CompressWorkspace or CompressWorkspaceTree operation resulted in this internal error.
- 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.
- 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. - WM_ERROR_156 there are active sessions using 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).
- 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 theLATEST
version of the workspace. - 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. - 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.
- 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.
- 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.
- 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. - 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.
- 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.
- 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.
- WM_ERROR_166 only a BeginResolve invoker or a user with the "WM_ADMIN" system privilege can call CommitResolve
-
Cause: A user attempted to invoke CommitResolve without having initiated the BeginResolve operation earlier and without having the
WM_ADMIN
system privilege. - 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. - WM_ERROR_168 Cannot disable workspace lockmode
-
Cause: An attempt was made to disable the workspace lock mode, but this is not supported.
- WM_ERROR_169 "WM_ADMIN" system privilege or ownership is required to UnFreeze a workspace
-
Cause: UnfreezeWorkspace failed because only a user with the
WM_ADMIN_ROLE
role orWM_ADMIN
system privilege or the owner of the workspace can unfreeze a frozen workspace. - 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.
- WM_ERROR_171 WM error: 'string'
-
Cause: A Workspace Manager error occurred.
- 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.
- 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. - 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.
- 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.
- WM_ERROR_176 A user-defined 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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_.
- 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$.
- 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.
- 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. - 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. - 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.
- 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.
- 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.
- WM_ERROR_191 LWDisableVersioning not called on the table 'string'
-
Cause: Internal error during the upgrade or downgrade.
- WM_ERROR_192 At least one table failed during temporary disable-versioning 'string'
-
Cause: Internal error during downgrade.
- 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.
- 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.
- WM_ERROR_196 'string' operation requires ''FREEZE_WORKSPACE'' privilege on the workspace or ''FREEZE_ANY_WORKSPACE'' or ''WM_ADMIN'' system privilege
-
Cause: Insufficient privilege for freezing or unfreezing a workspace.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- WM_ERROR_204 beginDDL not called on 'string'
-
Cause: BeginDDL needs to executed on the table before the current operation can be performed.
- 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.
- WM_ERROR_206 column reordering is not supported
-
Cause: Columns of the skeleton table associated with a version-enabled table were reordered.
- 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.
- 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.
- 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. - 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.
- WM_ERROR_211 DDL is being done on 'string'
-
Cause: A DDL session has already been started on the table.
- 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.
- 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.
- 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.
- WM_ERROR_215 A savepoint cannot be created with the name "LATEST"
-
Cause: A savepoint cannot be named "LATEST".
- 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.
- 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.
- 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.
- WM_ERROR_223 "WM_ADMIN" system privilege is required to invoke this procedure
-
Cause: A Workspace Manager operation was invoked without the requisite privileges.
- WM_ERROR_226 Nested Tables must have a primary key constraint
-
Cause: An attempt was made to execute EnableVersioning on a table that contained a nested table column that did not have a primary key.
- 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.
- WM_ERROR_229 statement 'string' failed during EnableVersioning. Error: string'
-
Cause: Version-enabling of the table failed due to some error. This may occur due to insufficient resources or some unexpected Oracle 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.
- 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.
- 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.
- 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 ofTRUE
is invalid if the current session has an open database transaction on that workspace. - 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
- 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.
- 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 toPESSIMISTIC_LOCKING
. - 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.
- 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.
- 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.
- WM_ERROR_240 reserved character found in workspace name
-
Cause: The name of a workspace contains one or more of these 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- WM_ERROR_250 workspace name may not be "NULL"
-
Cause: An attempt was made to name a workspace "NULL".
- 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. - 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. - WM_ERROR_253 lock_mode of only ''VE'' is allowed when workspace is "NONE"
-
Cause: A value of
NONE
for theworkspace
parameter is permitted only withVE
as the value forlock_mode
. - 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
orNONCR_WORKSPACE_MODE
is set toPESSIMISTIC_LOCKING
and the DML operation violates the system setting. - WM_ERROR_255 insufficient privileges ['string']
-
Cause: An attempt was made to invoke an import or export operation without the required privileges.
- WM_ERROR_256 'string' cannot be invoked with a null 'string' parameter
-
Cause: The specified parameter cannot be null.
- 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.
- WM_ERROR_258 specified system where clause is invalid ['string'']
-
Cause: An import or export operation was invoked with an invalid system
WHERE
clause. - 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.
- WM_ERROR_260 Export error ['string']
-
Cause: Unable to perform the export operation due to the specified error.
- WM_ERROR_261 Import error ['string']
-
Cause: Unable to perform the import operation due to the specified error.
- 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. - WM_ERROR_272 invalid event name: 'string'
-
Cause: An invalid Workspace Manager event name was passed as an argument to the function.
- 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 toOFF
. - 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.
- 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.
- 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
toOFF
when one or more multiparent workspaces existed in the system. - 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
toOFF
when one or more version-enabled tables contained 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 toOFF
. - 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.
- 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
. - WM_ERROR_281 batch_size parameter must be 'TABLE' or 'PRIMARY_KEY_RANGE'
-
Cause: The batch_size parameter value was invalid.
- 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. - WM_ERROR_283 invalid 'string' parameter specified
-
Cause: The value specified for the parameter was invalid.
- WM_ERROR_284 the length of the 'string' parameter cannot exceed 'string' characters
-
Cause: The value of a specified parameter exceeded the allowable length.
- WM_ERROR_285 the 'string' parameter must be set to 'string'
-
Cause: The value specified for the parameter was invalid.
- WM_ERROR_286 quoted identifiers are not supported
-
Cause: A quoted identifier was used.
- WM_ERROR_287 the 'string' parameter must be specified
-
Cause: The specified parameter was omitted.
- WM_ERROR_288 'string' privilege(s) needed
-
Cause: The executing user did not have the specified privileges.
- WM_ERROR_289 insufficient privileges on 'string'
-
Cause: The executing user did not have the necessary privileges on the object.
- WM_ERROR_290 only the table owner or a user with the "WM_ADMIN" system privilege can invoke this procedure
-
Cause: The procedure invoker had insufficient privileges.
- WM_ERROR_291 deadlock detected while trying to acquire lock on 'string'
-
Cause: A deadlock was encountered when acquiring a lock using the DBMS_LOCK package.
- WM_ERROR_292 error while trying to acquire lock on 'string', status='string'
-
Cause: A required lock could not be obtained when using the DBMS_LOCK package.
- WM_ERROR_293 error while trying to release lock on 'string', status='string'
-
Cause: The required lock could not be released when using the DBMS_LOCK package.
- WM_ERROR_294 open short transaction exists on 'string'
-
Cause: An open transaction had a lock on the specified object.
- WM_ERROR_295 the 'string' schema cannot contain dependent objects
-
Cause: The specified schema contained a dependent object when trying to version-enable a table.
- WM_ERROR_296 topology 'string' does not exist
-
Cause: The specified topology did not exist.
- WM_ERROR_297 object 'string' already exists
-
Cause: A required object already exists.
- WM_ERROR_298 object 'string' does not exist
-
Cause: The specified object did not exist.
- WM_ERROR_299 tablespace 'string' does not exist
-
Cause: The specified tablespace did not exist.
- WM_ERROR_300 the 'string' workspace cannot be renamed
-
Cause: The specified workspace cannot be renamed.
- WM_ERROR_301 workspace names cannot include the character 'string'
-
Cause: A workspace name contained the invalid specified character.
- WM_ERROR_302 the new name must be distinct from the old name
-
Cause: When renaming an object, the old name and the new name must be distinct.
- WM_ERROR_303 a workspace cannot be added as a parent workspace of itself
-
Cause: An attempt was made to add a workspace as a parent workspace of itself.
- WM_ERROR_304 cannot add a parent workspace to LIVE
-
Cause: An attempt was made to add a workspace as a parent workspace of the
LIVE
workspace. - WM_ERROR_305 'string' cannot be called on a topology feature table
-
Cause: An invalid operation was attempted on a topology feature table.
- WM_ERROR_306 MergeTable with remove_data on a parent table of a referential constraint is not supported for multi-parent workspacese
-
Cause: The MergeTable operation was executed on an unsupported table.
- WM_ERROR_307 workspace 'string' has a crstatus that is not supported for this operation
-
Cause: The operation attempted to use a workspace that is not currently supported.
- WM_ERROR_308 a 'string' with more than 'string' characters in its name was found - rename to a shorter name
-
Cause: The object's name exceeded the specified number of characters.
- WM_ERROR_309 some tables have already been version enabled with a different validtime option
-
Cause: An attempt was made to modify an topology feature table in an optimistic mode.
- WM_ERROR_310 a topology feature table can be modified only in pessimistic mode - set locking ON
-
Cause: An attempt was made to modify an topology feature table in an optimistic mode.
- WM_ERROR_311 feature tables cannot be deleted from this topology
-
Cause: An attempt was made to remove the last feature table from the topology.
- WM_ERROR_312 topology 'string' does not have a feature table
-
Cause: EnableVersioning was being executed on a topology without a feature table.
- WM_ERROR_313 the 'string' parameter is incompatible with the other options
-
Cause: The specified parameter was not compatible with the other parameters.
- WM_ERROR_314 'string' is not a version-enabled topology
-
Cause: The topology specified has not been version-enabled.
- WM_ERROR_315 this operation is not allowed during bulk loading
-
Cause: An unsupported operation was executed during bulk loading.
- WM_ERROR_316 wm_version column should not be specified when bulk loading
-
Cause: The
wm_version
column was specified in the control file. - WM_ERROR_317 cannot bulk load into a table with a self-referential integrity constraint
-
Cause: An attempt was made to bulk load into a table that contained a foreign key constraint that referenced a column in the same table.
- WM_ERROR_318 bulk loading into only the latest version of a workspace is supported
-
Cause: An attempt was made to bulk load into a version that is not supported.
- WM_ERROR_319 this operation is not supported while 'string' is in 'string' state
-
Cause: An operation was executed while the specified table was in an unsupported state.
- WM_ERROR_320 Workspace Manager must first be uninstalled from CDB$ROOT
-
Cause: An attempt was made to uninstall Workspace Manager from a PDB (pluggable database) before uninstalling it from the CDB$ROOT.
- WM_ERROR_321 nested tables cannot themselves contain a nested table
-
Cause: An attempt was made to version-enable a table that contained a nested table that also contained a nested table.
- WM_ERROR_322 nested tables contained in objects are not supported
-
Cause: An attempt was made to version-enable a table that contained a column whose data type contained a nested table.
- WM_ERROR_323 system parameter 'string' must be set to 'string'
-
Cause: An operation was executed that required a system parameter to match a specific value.
- WM_ERROR_324 the following index tables were unable to be DisableVersioned: 'string'
-
Cause: During a downgrade operation, there were errors when attempting to disable version the specified index table.
- WM_ERROR_325 the following index tables were unable to be EnableVersioned: 'string'
-
Cause: During an upgrade operation, there were errors when attempting to version-enable the specified index table.
- WM_ERROR_326 null value not allowed for a primary key column
-
Cause: A DML operation resulted in the primary key value being set to null.
- WM_ERROR_327 the child table 'string' contains a record outside the specified valid time range
-
Cause: A constraint violation occurred as a result of adding the
validtime
option to a parent table in a foreign key relationship. - WM_ERROR_328 all child tables must be valid-time enabled
-
Cause: An attempt was made to add the
validtime
option to a table that is the parent table in a foreign key constraint, without first adding the option to all child tables. - WM_ERROR_329 this index operation is not currently supported while 'string' is version enabled
-
Cause: An attempt was made to perform an unsupported DDL operation on an index due to the table being version-enabled
- WM_ERROR_330 multi-transaction update not supported for a clustered table - specify 'UNLIMITED' undo space
-
Cause: An invalid
undo_space
parameter value was specified for a clustered table. - WM_ERROR_331 object tables cannot be version enabled
-
Cause: An attempt was made to version-enable an object table.
- WM_ERROR_332 One of the rows in the lineage to be removed has a createtime greater than the specified instant
-
Cause: The PurgeTable procedure was unable to complete due to existing data.
- WM_ERROR_333 teferential constraints on object attributes not supported
-
Cause: An attempt was made to version-enable a table that contained a referential integrity constraint on an object attribute.
- WM_ERROR_334 savepoint names cannot include the character 'string'
-
Cause: A savepoint name contained the invalid specified character.
- WM_ERROR_335 this operation is not currently supported while 'string' is version enabled
-
Cause: An unsupported DDL statement was executed while the table is version-enabled.
- WM_ERROR_336 the index 'string' cannot be renamed
-
Cause: An attempt was made to rename an index that cannot be renamed.
- WM_ERROR_337 this table can only be dropped by dbms_wm.rollbackDDL/commitDDL
-
Cause: An attempt was made to drop the skeleton table created by the BeginDDL procedure.
- WM_ERROR_338 skeleton tables used by beginDDL/commitDDL cannot be version enabled
-
Cause: An attempt was made to version-enable the skeleton table created by the BeginDDL procedure.
- WM_ERROR_339 this table is not available for queries and DML operations
-
Cause: An attempt as made to issue a DML statement on a table that is currently unavailable.
- WM_ERROR_340 this table is used by Workspace Manager for referential integrity checking
-
Cause: An attempt was made to drop a table required by Workspace Manager for referential integrity checking.
- WM_ERROR_341 check constraint 'string' violated
-
Cause: When executing CommitDDL, a check constraint was violated.
- WM_ERROR_342 trigger creation on this object is not supported
-
Cause: An attempt was made to create a trigger directly on the base table used by Workspace Manager.
- WM_ERROR_343 types contained in versioned tables cannot be dropped
-
Cause: An attempt was made to drop a type required by a version-enabled table.
- WM_ERROR_344 unable to create _LCK table
-
Cause: An index necessary for the creation on the _LCK table was unable to be created due to an existing object.
- WM_ERROR_345 unable to support unique index due to naming conflict
-
Cause: An attempt was made to version-enable a table containing an index name that has a naming conflict.
- WM_ERROR_346 insufficient privileges to revoke 'string'
-
Cause: An attempt was made to invoke the RevokeWorkspacePriv or RevokeSystemPriv procedure without the required privileges to do so.
- WM_ERROR_347 the object definition exceeds the maximum allowed length
-
Cause: The search_condition for a check constraints exceeded the supported length.
- WM_ERROR_348 constraint 'string' exists on another table
-
Cause: A foreign key constraint was unable to be created due to the existence of another constraint with the same name.
- WM_ERROR_349 constraint enforcement on existing versioned data not supported in the presence of multi-parent workspaces
-
Cause: Enforcement of a foreign key constraint was not possible due to the presence of a multiparent workspace.
- WM_ERROR_350 hint cannot contain 'string'
-
Cause: An unsupported hint was specified when executing the AdduserDefinedHint procedure.
- WM_ERROR_351 implicit savepoints cannot be renamed
-
Cause: An attempt was made to rename an implicit savepoint.
- WM_ERROR_352 'string' not granted to 'string'
-
Cause: An attempt was made to revoke privileges from a user that did not have them.
- WM_ERROR_353 instant can be specified only for a table with history option
-
Cause: The
instant
parameter was not null for a table that did not have thehistory
option. - WM_ERROR_354 only LATEST data is currently supported
-
Cause: An attempt was made to import or export non-LATEST data.
- WM_ERROR_355 overlapping periods found for column wm_valid of table 'string'
-
Cause: When version-enabling a table with
validtime
, a constraint violation was found within the table. - WM_ERROR_356 referential constraint 'string' exists with another parent table
-
Cause: A foreign key constraint was unable to be created due to the existence of another constraint with the same name.
- WM_ERROR_357 referential constraint with a non-primary-key constraint 'string' detected
-
Cause: A referential integrity constraint was found within the table that referenced a column that was not part of the primary key.
- WM_ERROR_359 incompatible options specified
-
Cause: Options were specified that are incompatible with each other.
- WM_ERROR_360 this release only supports changing to the workspace type: DBMS_WM.CR_WORKSPACE_TYPE
-
Cause: An attempt was made to change a workspace into a non-continually refreshed workspace.
- WM_ERROR_361 unable to import this table
-
Cause: An attempt was made to import a table that required unsupported operations.
- WM_ERROR_362 unsupported options specified while multi-parent workspaces exist
-
Cause: The parameters specified for the PurgeTable procedure are not supported when a multiparent workspace exists.
- WM_ERROR_363 unable to create workspace with the same name as a workspace whose removal has been deferred
-
Cause: A workspace was removed using by specifying either 'FAST' or 'REMOVE_LOCKS' for the defer_option parameter. Until the workspace has been completely cleaned up, a new workspace with the same name cannot be created.
- WM_ERROR_364 'string' not supported on a table with valid time
-
Cause: The operation was not supported for table with the
validtime
option. - WM_ERROR_365 'string' and 'string' have an identical column name
-
Cause: A nested table had a column with the same name as a column that is contained in its parent table.
- WM_ERROR_366 'string' is already version enabled with valid time option
-
Cause: An attempt was made to add the validtime option to a table that already has the option enabled.
- WM_ERROR_367 invalid active date for DML
-
Cause: An invalid time was specified when modifying a table.
- WM_ERROR_368 a referential integrity constraint will be violated between 'string' and 'string' in the workspace 'string' or one of its descendants - child record found
-
Cause: The operation could not be completed due to a constraint violation of a foreign key constraint in the specified workspace (or one of its descendants).
- WM_ERROR_369 a referential integrity constraint will be violated between 'string' and 'string' in the workspace 'string' or one of its descendants - parent key not found
-
Cause: The operation could not be completed due to a constraint violation of a foreign key constraint in the specified workspace (or one of its descendants).
- WM_ERROR_370 invalid values contained in the wm_valid column
-
Cause: When executing EnableVersioning, a row with an invalid
wm_valid
column was found. - WM_ERROR_371 privileges on 'string' policy must be granted using dbms_wm.grantPrivsOnPolicy
-
Cause: A table with an OLS policy was being version-enabled before executing the grantPrivsOnPolicy procedure for the table.
- WM_ERROR_372 Workspace Manager is not properly installed
-
Cause: An import operation was being performed with an invalid installation of Workspace Manager.
- WM_ERROR_373 unsupported version of Workspace manager detected
-
Cause: An import operation was being performed with an incompatible version of Workspace Manager installed.
- WM_ERROR_374 Datapump job did not successfully complete
-
Cause: An error was encountered during the Oracle Data Pump job.
- WM_ERROR_375 invalid datapump job specified
-
Cause: The specified Oracle Data Pump job could not be used for the operation due to incompatible options.
- WM_ERROR_376 the 'string' schema does not contain the necessary data
-
Cause: The schema contained in the dump file did not contain the necessary data to complete the import_schemas procedure.
- WM_ERROR_377 Export and Import operations cannot be run simultaneously
-
Cause: An attempt was made to run simultaneous export and import operations.
- WM_ERROR_378 Removing a workspace that was a parent of a workspace whose removal has been referred is not supported
-
Cause:An attempt was made to remove a workspace that has a child workspace that had its removal deferred.
- WM_ERROR_379 a workspace with a 'string' lockmode cannot be merged or refreshed
-
Cause: An attempt was made to merge or refresh a workspace with the specified lockmode.
- WM_ERROR_380 the 'string' lockmode cannot be set for a continually refreshed workspace or the 'LIVE' workspace
-
Cause: An attempt was made to set the lockmode of a continually refreshed workspace or the 'LIVE' workspace to an unsupported mode.
- WM_ERROR_381 all child workspaces must have their lockmodes set to 'D'
-
Cause: An attempt was made to set the lockmode of the specified workspace to 'D', even though a child workspace of the specified workspace had a different lockmode.
- WM_ERROR_382 range partitioning is not supported for version enabled tables
-
Cause: An attempt was made to version-enable a table that uses range partitioning.
- WM_ERROR_383 Workspace Manager must first be uninstalled from each PDB prior to uninstalling from CDB$ROOT
-
Cause: An attempt was made to uninstall Workspace Manager from CDB$ROOT while it still exists in one or more PDBs.
- WM_ERROR_384 This operation cannot be executed while the DEFAULT_WORKSPACE system parameter is set to 'string'
-
Cause:An attempt was made to modify the workspace defined by the DEFAULT_WORKSPACE system parameter in an unsupported manner.
- WM_ERROR_385 The workspace 'string' must have the ACCESS_WORKSPACE privilege granted to PUBLIC
-
Cause: An attempt was made to change the DEFAULT_WORKSPACE system parameter to a workspace that lacked access by PUBLIC..
- WM_ERROR_386 Invisible columns are not supported
-
Cause: An attempt was made to version-enable a table that contained an invisible column.
- WM_ERROR_387 This procedure has been deprecated
-
Cause:This procedure is no longer supported in this version of Workspace Manager.
- WM_ERROR_388 Column value has been improperly modified within a user-defined trigger
-
Cause: Either a primary key column value was being updated by a user-defined trigger in an unsupported manner, or a :NEW value was being modified in a delete trigger.
- WM_ERROR_389 Only identity columns defined as ''always'' or ''by default on null'' are supported
-
Cause: An attempt was made to version-enable a table that contained an identity column that was not one of the listed types. (For example, it might have been a “generated always” identity column, which is not supported for version-enabling.)
- WM_ERROR_390 Redaction policies are not currently supported for version-enabled tables
-
Cause: An attempt was made to version-enable a table that has a redaction policy defined on it.
- WM_ERROR_391 The isTopology parameter is required for the 'string' table
-
Cause: Either enableversioning or disableversioning was executed on a table that is part of a topology.
- WM_ERROR_392 A virtual column that is part of the primary key cannot reference non-primary key columns
-
Cause: EnableVersioning failed due to a virtual column that is included in the primary key and references unsupported columns.
- WM_ERROR_393 A virtual column that is part of the primary key cannot reference non-primary key columns
-
Cause: The LIVE workspace cannot be the source or target workspace Cause: When executing CopyWorkspace, either the source workspace or the target workspace parameters was set to the 'LIVE' workspace .
- WM_ERROR_394 Virtual column expression cannot be modified because a constraint is defined on the column
-
Cause: A DDL operation attempted to modify the virtual column expression of a column that has a referential integrity constraint defined on it.
- WM_ERROR_395 Deferrable constraints are not supported
-
Cause:EnableVersioning or a DDL operation was executed on a table containing a deferrable constraint.
- WM_ERROR_396 Deferrable constraints are not supported
-
Cause:When executing CopyWorkspace, both the source workspace and the target workspace parameters were specified to be the same workspace.