We initialize new DB by generating and extracting local DB again when we
forgot local DB user’s password. In this
situation we lose all our work which previously did in local DB.
To overcome this kind of problem there is simple below tip to reset
local DB user password.
1. Go to Siebel tool installdir like c:\siebel\8.1\tools_1\bin and open
dbisqlc.exe as shown in below
2. Enter Userid as “DBA” and password “your enterprise name” like CRMDEV81 3. Go database tab and select your local dbf file like below..
4. Click OK 5. Interactive sql window open saying connected to database.
6. Execute following query to reset password of userid “TEST”. grant connect to TEST identified by PASSWORD NOTE-Here PASSWORD is your new password and userid and password is in caps only.
Both are basically used for storing values which can be accessed from anywhere in the Application. Both are user and session specific.
a) Profile Attributes comes with Siebel Personalization. If EnablePersonalization = False in the CFG, Profile Attributes will not work. There are two types of Profile Attributes: 1) Persistent Profile Attributes 2) Dynamic Profile Attributes
Persistent Profile Attributes are mapped to the fields in the Business Component "Personalization Profile". Dynamic Profile Attributes are created at run time and are not based on any Business Component fields.
Dynamic profile attributes is generally what we use most of the time.
b) GlobalShared can not be used in browser scripts. Profile Attributes can be used in browser scripts. c) Profile Attributes are supported in Calculated Values, Search Specifications etc but GlobalShared is not. d) Profile Attributes are mainly used in Personlization Rules to control the Applet and View visibility
It is a common scenario in Siebel Implementations to use
‘RaiseErrorText()’ method for throwing Error Messages on UI when any Custom
Validations are not satisfied. However, Siebel suffixes the Error Code
‘SBL-EXL-00151’ along with the text passed to RaiseErrorText() Method. This
might be look cryptic, confusing & not acceptable to the Business Users,
many times.
Root Cause:
Every call to RaiseErrorText() Method indeed raises an Exception
and the Exception Code for the Custom Error Messages hard-coded internally is
SBL-EXL-00151. It is not possible to suppress this with any coding changes.
The Challenge:
In multiple Business Cases, there would be pre-defined Business
Codes for Errors and the Siebel Specific Error Code might not be acceptable to
the Business Users as it is not as per the Standard Business Codes defined.
The Solution:
Siebel has identified this as a Product Defect and provided a Fix
from Version 7.7.2 onwards.
·Login to your Siebel Client
·Navigate to Application
Administration > System Preferences View
·Add a new System Preference with
Name ‘Suppress Scripting Error Code’ & Value ‘TRUE’
·Restart your Enterprise Server
·Further Concatenate Business
Specific Error Codes along with Validation Messages in the Text Message
argument to RaiseErrorText() Method
