Getting hard time opening DBISQLC ?

Whenever you need to run a query in your Siebel Local database, sometimes it feels bad as we need to follow the below steps everytime :

1. Navigate to SiebSrvr/Bin folder.

2. Open DBISQLC

3. Need to fill in the followig fields in Connection window :

a) Under Login Tab: fill in User Id and Password (in CAPS)

b) Under Database Tab : Click on Browse and locate the SSE_DATA.dbf file.

4. Click on "Ok".

hhmmmm, following the above steps everytime is not a good choice, isn't it?

okayyy.. lets automate this and try to open dbisqlc in just a button click, sounds good !! I know :)

Here are the steps : (taking the assumption Siebel is installed in "E:\Siebel\8.1\Client", "E:\Siebel\8.1\Tools")

1. Create a new batch file (for eg: "mydbisqlc.bat") on the desktop.
2. Copy paste the below lines of text in it.

cd E:\Siebel\8.1\Client_1\BIN
e:
dbisqlc -c
userid=SIEBELMANTRA;password=MYPASSWORD;databasefile=E:\Siebel\8.1\Tools_1\LOCAL\sse_data.dbf

.........................Note : Please change your user name and password in the above command.

3. Save the file on Desktop for keep it handy.
4. Double click on it and enjoy.

I know you must be smiling now after getting this cool tip !!!!

Check it out !!!!!!

.

Vanilla Views not visible in Local Dedicated Client

One of my colleague got his new Local database extracted and when he tried connecting to the Local Database via dedicated client, found that lot many views are not visible on the UI. Just to double check, he also confirmed from one another colleague who also got his new database and same problem was there with his dedciated client as well.

Now few more things I asked him to confirm :

1. Connect to Thin-Client and check whether the views are visible : Yes, views are visible in the thin-client.

2. Connect to Server Database via dedicated client and check whether the views are visible. Yes, views are visible via Server dedicated client.

This problem occurs when : "User is possessing any one of the responsibility associated with the view and having "Local Access" flag unchecked."

Solution :
Being a developer, you should have access to all the views, so better to have visibility for all the views instead of findings specific views which are not visible and fixing those.

1. Open "DBISQLC.exe" and connect to the Local Database.
2. Run the following command :
a) update siebel.S_APP_VIEW_RESP
set LOCAL_ACCESS_FLG = 'Y'

b) Commit

3. Restart the dedicated session and you should see all the views on the UI.

Hope this helps.

.

SBL-DBX-00083: Unable to start due to incorrect system preference setting

No Parameter has been changed on the Siebel Server and no settings has been touched and suddenly this error started coming while running "Database Extract" component. So the way everybody's next step is to search for "SBL-DBX-00083" in Metalink, I also tried the same thing and very easily got to know that the solution for this problem can achieved by following the below steps :

a) Go to "Administration - Application -> System Preferences"
b) Query for : "Docking: Transaction Logging" parameter and change the value to "True"

c) Restart the Siebel Server

d) Restart the "Transaction Processor" component.

You must be thinking when the resolution is already available in Metalink, then why I am explaining that here..... :), because there is something new I observed.

Let me tell you what exactly happened and I think you might be interested in reading that. When I went to "Administration-Application -> System Preferences" view and queried for "Docking: Transaction Logging" parameter, I found none.

So I thought it might not be there (just a guess), finally I decided to create a new one with the value "TRUE". Hope I am going into the right direction as I was just following what is written in Metalink. After that restarted the Siebel Server and want to check if "Transaction Processor" component was running, but it wasn't. So I just restarted it, but I saw that the "Transaction Manager" has again got errored out with the error : "SBL-TXP-00011: Unable to Start the APIs". hmmmmm... I haven't got rid of one error and I found another one. This is what Siebel world is :)

Again went to the Support Web to check for the resolution and this is something strange now. The resolution for this error is also the same that I need to have "Docking: Transaction Logging" parameter to "TRUE". But I have already created that one, right?

I am not sure what is going on? Why Siebel is not accepting the parameter value that I have just mentioned under System Preferences view?

Idea came into my mind and here below is what it was :

a) Go to Adminitration-Application -> System Preferences view.

b) Do a "About View" to check for the Business Component Name. It was "System Preferences".
c) Go to Siebel Tools, check for the table name. It was "S_SYS_PREF".

d) Run the below query :

Select * from siebel.s_sys_pref

where sys_pref_cd like 'Dock%'

I got surprised, when I saw two records returned with the following names :

a) Docking:Transaction Logging with Value = "FALSE"

b) Docking: Transaction Logging with Value = "TRUE"

Can you observe the difference in the name of the parameters above two. Second one have a space after "Docking: ".

That means the parameter was already existing but not displayed on the UI and by mistake I have created a new one. So I deleted the one I created from UI and changed the value for the exiting one from backend like this :

update siebel.S_SYS_PREF
set val = 'TRUE'
where sys_pref_cd like 'Dock%'

restarted the Siebel Server and found that Transaction Processor is also running fine. Tried with a new Database Extract again and it went fine.

Be careful from now on, it may happen with you as well. If something is not available on the UI, that doesn't mean it is not available in the database. :)