Applies to:
Product Release: V7 (Enterprise)Version: 7.5.3.4 [16180]
Database: Oracle 9.2.0.4
Application Server OS: HP-UX 11i
Database Server OS: HP-UX 11i
This document was previously published as Siebel SR 38-1195487851.
Symptoms
SBL-DAT-00254, SBL-DAT-00369After installing the Siebel Industry Applications Sample Database the user accounts noted in the
Siebel Release notes do not work for Siebel Communications, Media, and Energy.
eg.
CCORWIN, PCARR, etc.
Only the sadmin account works. Other verticals seem to work fine.
Solution
Message 1
For the benefit of other readers:The Customer was attempting to use the Siebel Version 7.5.3.4 SIA (Industry Apps - Comms / Media / Energy) client Application with Sample Database System which worked fine with 'SADMIN / SADMIN' User_ID and Password. However, when the Customer used these User_ID Login's "CCORWIN or PCARR" - then they would be presented with this error message instead : "The User ID or Password is not recognised"
This was similar error behavior to Service Request Number 38-1038794181 available out on SupportWeb. However, the workaround solution presented in this SR did not work as expected and this error message was presented instead :
"An Internal Error with the Connector DLL '<?>' has occurred, preventing one of the following export functions from being loaded: _SSACreateSqlObj@12 or SSASQLObjLogon@24. Please verify that the correct version of the runtime client specific to your database platform is installed on the machine where your Siebel Server is running. If this problem still persists, please verify that the Database Connectivity Settings are correct ? (SBL-DAT-00369)"
"The User Name you have entered is invalid or your user position is not defined. Please try and logon again or contact your systems adminstrator for assistance. (SBL-DAT-00254)"
Following on from my research and testing, I discovered that these User_ID's 'CCORWIN and PCARR' have been marked as inactive and are no longer required for the Siebel Version 7.5.3.x release.
Message 2
Continued...The workaround solution this time was to use the other Login User_ID's such as TBALL (Tom Ball) or WBECKER (William Becker).
I have raised Product Defect Change Request Number 12-JZ7A1Z to have this new matter addressed.
Keywords: Siebel 7.5.3.x, CME - Comms / Media / Energy, User_ID, Login, Password, Sample, Database, System, Connector, DLL, SBL-DAT-00369, SBL-DAT-00254
Applies to:
Siebel Sales - Version: 7.7 [18026] BETA to 8.1.1 [21112] - Release: V7 to V8Information in this document applies to any platform.
Symptoms
User is encountering the following error when trying to run the encryptupg utility:The user-context could not be established. Something is wrong with the assigned primary position or login related repository objects. See additional error messages for more information.(SBL-DAT-00546)The username you have entered is invalid. Please try to log on again or contact your system administrator for assistance.(SBL-DAT-00254)
Cleaning up... this may take a while.
Cleaning up... this may take a while.
Cause
This behavior is most likely caused by the tableowner database userID not having a corresponding Siebel account and/or that account not having adequate responsibilities / positions.
The error messages are actually pretty self-explanatory:
The user-context could not be established. Something is wrong with the assigned primary position or login related repository objects. See additional error messages for more information.(SBL-DAT-00546)The username you have entered is invalid. Please try to log on again or contact your system administrator for assistance.(SBL-DAT-00254)
The presence of the second message leads us to believe that the tableowner does not have a matching record in the OLTP's S_USER table. This is not uncommon since, by default, the tableowner is not created as a Siebel userID.
Solution
The most likely cause of the behavior you are seeing is that the user you are using to run the encryptupg.exe is the tableowner for your Siebel on-line transactional processing (OLTP) database. While that is actually a good way of running the encryptupg.exe utility (in Oracle it actually is required), there is an issue that the tableowner database account is not by default a Siebel application login. This is why you are seeing the SBL-DAT-00546 and SBL-DAT-00254 errors.The solution for this is to create a Siebel login for the tableowner account (the default tableowner is SIEBEL). The easiest way to do this and get adequate permissions is to simply copy the SADMIN user.
1. Log into an employee facing, high interactivity Siebel application such as Sales or Call Center using an administrator ID such as SADMIN.
2. Navigate to Site Map > Administration - Users > Employees.
3. On the Employees screen do a query for the login SADMIN (or whatever your administrator user's login is).
4. Click the little Menu button on the list applet and select Copy Record.
5. Fill in the required fields making sure you use the tableowner (SIEBEL in a default implementation) as the login / userID.
6. Save the record.
After doing this, please retest the use of the encryptupg.exe utility.
Also, although not directly related to this behavior, I would like to proactively call your attention to Note 551663.1 on Metalink 3. This discusses a specific issue when using encryption with Oracle databases.
References
NOTE:551663.1 - Error loading dictionary file diccache.dat.(SBL-DAT-60237) when running KEYDBMGRApplies to:
Siebel Sales - Version: 7.7 [18026] BETA to 8.1.1 [21112] - Release: V7 to V8Information in this document applies to any platform.
Symptoms
User is encountering the following error when trying to run the encryptupg utility:The user-context could not be established. Something is wrong with the assigned primary position or login related repository objects. See additional error messages for more information.(SBL-DAT-00546)The username you have entered is invalid. Please try to log on again or contact your system administrator for assistance.(SBL-DAT-00254)
Cleaning up... this may take a while.
Cleaning up... this may take a while.
Cause
This behavior is most likely caused by the tableowner database userID not having a corresponding Siebel account and/or that account not having adequate responsibilities / positions.
The error messages are actually pretty self-explanatory:
The user-context could not be established. Something is wrong with the assigned primary position or login related repository objects. See additional error messages for more information.(SBL-DAT-00546)The username you have entered is invalid. Please try to log on again or contact your system administrator for assistance.(SBL-DAT-00254)
The presence of the second message leads us to believe that the tableowner does not have a matching record in the OLTP's S_USER table. This is not uncommon since, by default, the tableowner is not created as a Siebel userID.
Solution
The most likely cause of the behavior you are seeing is that the user you are using to run the encryptupg.exe is the tableowner for your Siebel on-line transactional processing (OLTP) database. While that is actually a good way of running the encryptupg.exe utility (in Oracle it actually is required), there is an issue that the tableowner database account is not by default a Siebel application login. This is why you are seeing the SBL-DAT-00546 and SBL-DAT-00254 errors.The solution for this is to create a Siebel login for the tableowner account (the default tableowner is SIEBEL). The easiest way to do this and get adequate permissions is to simply copy the SADMIN user.
1. Log into an employee facing, high interactivity Siebel application such as Sales or Call Center using an administrator ID such as SADMIN.
2. Navigate to Site Map > Administration - Users > Employees.
3. On the Employees screen do a query for the login SADMIN (or whatever your administrator user's login is).
4. Click the little Menu button on the list applet and select Copy Record.
5. Fill in the required fields making sure you use the tableowner (SIEBEL in a default implementation) as the login / userID.
6. Save the record.
After doing this, please retest the use of the encryptupg.exe utility.
Also, although not directly related to this behavior, I would like to proactively call your attention to Note 551663.1 on Metalink 3. This discusses a specific issue when using encryption with Oracle databases.
No comments:
Post a Comment