Local Database 8.x Login Issue error SBL-DAT-00559: No positions associated with login user
(Doc ID 534364.1)
Last updated on APRIL 26, 2021
Applies to:Siebel Remote Server - Version 220.127.116.11  to 18.104.22.168  [Release V7 to V8]
z*OBSOLETE: Microsoft Windows Server 2003
User had completed Database Extract for a User Id "<Username>" in Server. The user has valid Responsibilities and position and able to login ok in Web Client.
The sse_data.dbf Extract was successful in local. The Siebel Remote Client fails for User Id / Password when trying to Login .
For other users Id's the DB Extract/ initialization / Login to Remote is OK.
Logging into the database trough dbisqlc.exe using the mobile client’s login and password was successful.
On the log file found the following messages were found:
ObjMgrSessionLog Error 1 0 2005-09-23 13:51:56 (dmsessionusercontext.cpp (1414)) SBL-DAT-00559: No positions associated with login user '<Username>'.
ObjMgrSessionLog Error 1 0 2005-09-23 13:51:56 (dmsessionusercontext.cpp (1440)) SBL-DAT-00558: An error occurred that prevented setting a primary position for the login user.
This operation was being attempted because the no primary position was found for the user '<Username>'. See additional error messages for more information.
ObjMgrSessionLog Error 1 0 2005-09-23 13:51:56 (dmsessionusercontext.cpp (1766)) SBL-DAT-00556: The position related context could not be established for login name '<Username>'.
The following queries were executed and showed that the position entry in the local database was correct:
SELECT * FROM SIEBEL.S_USER WHERE LOGIN = '<Username>'
SELECT * FROM SIEBEL.S_POSTN WHERE ROW_ID='1-MR6O5'
SELECT * FROM SIEBEL.S_NODE
SELECT * FROM SIEBEL.S_PARTY WHERE ROW_ID='1-MR6O5'
The behavior was reproducible after the mobile user’s re-extraction.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document