Skip to main content

Error SBL-DAT-00523 or SBL-DAT-00523 Occurs When Modify Objects On My Workspace (Doc ID 2527635.1)

APPLIES TO:

Siebel Tools - Version 18.12 and later
Information in this document applies to any platform.
SYMPTOMS

Using SADMIN user can not modify any object, following error is displayed:

ERRORS:
----------------
The state of selected workspace has been modified by another user , workspace will refresh itself and proceed .(SBL-DAT-60295)

OR

The selected record has been modified by another user since it was retrieved.  Please continue. (SBL-DAT-00523)


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Log in to Siebel Tools using SADMIN
2. Try to modify an object
3. Above error is displayed

CAUSE
In the siebdevopenWS.log, there are below error messages:
ObjMgrLog Error 1 000000025ca60cc4:0 2019-04-04 08:12:11 (workspacemgr.cpp (2672)) SBL-DAT-00523: The selected record has been modified by another user since it was retrieved. Please continue.

ObjMgrBusCompLog Error 1 000000025ca60cc4:0 2019-04-04 08:12:11 (sqlobj.cpp (43149)) SBL-DAT-00523: The selected record has been modified by another user since it was retrieved. Please continue.

ObjMgrSessionLog Warning 2 000000025ca60cc4:0 2019-04-04 08:12:11 (physmod.cpp (5186)) SBL-DAT-00473: No transaction is in progress

ObjMgrLog Error 1 000000025ca60cc4:0 2019-04-04 08:12:11 (bcrepos.cpp (9534)) SBL-DAT-00523: The selected record has been modified by another user since it was retrieved. Please continue.

From my research, error SBL-DAT-00523: The selected record has been modified by another user since it was retrieved. Please continue." is generally caused by blank STATUS_CD in the S_WORKSPACE table.

Please find below INSERT statement from siebdev_creatednewWS.log:

INSERT INTO SIEBEL1.S_WORKSPACE (
CONFLICT_ID,
DB_LAST_UPD_SRC,
DB_LAST_UPD,
LAST_UPD,
CREATED,
LAST_UPD_BY,
CREATED_BY,
MODIFICATION_NUM,
ROW_ID,
COMMENTS,
INACTIVE_FLG,
LATEST_VER,
NAME,
OBJ_LOCKED_FLG,
PAR_WS_ID,
PAR_WS_VER,
REPOSITORY_ID,
BUILD_BRANCH_FLG)
VALUES (:1, :2, current_date, :3, :4, :5, :6, :7, :8, :9, :10, :11, :12, :13, :14, :15, :16, :17)

Note, there is no STATUS_CD column in the INSERT statement.
In vanilla, STATUS_CD is bind variable 18 in the in the INSERT statement when creating a new workspace.

This is caused by setting the Workapce Name to a dev_* workspace:
[Workspace]
Name = dev_sadmin_test2
Version = Latest

Although, it is able to go the correct workspace. when you open tools, setting Workapce Name to a dev_* workspace is not supported.

It's should set to Main or a Integration Workspace. Please see below example on setting the Workapce Name in a .cfg file:
Using Siebel Tools > Parallel Development Using Workspaces > Administering Parallel Development using Workspaces > Launching the Web Client with a Specified Workspace
https://docs.oracle.com/cd/E88140_01/books/UsingTools/parallel_development_using_workspaces9.html#wp1010563



SOLUTION

To fix the error,   please follow the below steps:
1) Open tools.cfg

2) Change tools.cfg to point to Main or a Integration Workspace.

Change from:
Workspace]
Name = dev_sadmin_test2
Version = Latest

To:
Workspace]
Name = Main
Version = Latest

3) Log in to Tools and test the behavior.

Source:
https://support.oracle.com/ Doc ID 2527635.1

Comments