Does DDLSYNC/ Apply Activate Drop Tables or Columns after they were deleted from the Siebel repository?

Does DDLSYNC/ Apply Activate Drop Tables or Columns after they were deleted from the Siebel repository?

DLSYNC / "Synchronize Schema Definitions" will NOT drop CX_ tables at DB level
(it will also not delete CX_ columns from DB tables when deleting them in the Siebel repository) 

Typically, you will only add tables, so this normally not an issue. Also this is expected / intended functionality:
just imagine what would happen if someone accidentally deleted a table or column in Siebel Tools and that would result in all your data in that table or column automatically being dropped being lost. 

To delete custom tables or columns, the developers would need to delete or inactivate them in the Siebel repository,
and the DBA would need to drop / remove them at physical DB level - please note that standard Siebel tables or columns (that cannot be removed from the Repository) also must not be dropped at DB level.

WfProcMgr error Database connection was lost, please retry.(SBL-DAT-00175)"(SBL-EAI-04376)

Issue: Siebel Workflow process manager shows below error in the log files

Database connection was lost, please retry.(SBL-DAT-00175)"(SBL-EAI-04376)

This issue is related to IDLE_TIME parameter of user profile at the Oracle database.

Check the IDLE_TIME parameter

select profile from dba_users where username = 'SADMIN';

select profile, resource_name, limit from dba_profiles where resource_name ='IDLE_TIME'

Set IDLE Time to UNLIMITED on the Oracle database

ALTER PROFILE app_user2 LIMIT IDLE_TIME UNLIMITED;

Change File System parameter from *FSM* to actual server path Siebel 7.8

Change File System parameter from *FSM* to actual server path Siebel 7.8

Check current value of File System

Login to srvrmgr and use below command to display current value of file system parameter

> list advanced param DSFileSystem for named subsystem ServerDataSrc

Changing the parameter to actual server path

> change param dsfilesystem='\\\\\\WINDOWSSRVR111\\\sea78files\\\att' for named subsystem ServerDataSrc

Siebel Client-Side Logging for High-Interactivity Applications

 

Siebel Client side logging can help you to diagnose situations in which your browser freezes or aborts while using Siebel Application.

Below table illustrates settings to be done on Application Object Manager to enabling Client Side logging.

Parameter	Description	Possible Values	Default Value
ClientSideLogging	Enable/Disable Client Side logging	True/False	False
ClntTraceMode	Set this parameter to enable or disable logging.	1 - Enable 0 - Disable	0
ClntLogFileSize	Size of the log file in MB. Minimum log file size is 50 MB.	50 MB or more	50
ClntLogArchiveCount	Number of files to be archived.	2, 5, 10, and so on.	5
ClntLogDirectory	Directory where the log file is created.	D:\SiebelLogs	C:\SiebelLogs
ClntTraceUnicode	Set this parameter to turn on or off Unicode trace.	True—Unicode trace is on False—Unicode trace is off	False

Alternately if you want to enable Client logging for single High Interactivity client you can do so by setting below environment variables on local machine running Siebel Web Client(HI).

Environment Variable	Possible Values
SEBLCL_TRACEMODE	1—Enable 0—Disable
SEBLCL_LOGDIR	Directory where the log file is created
SEBLCL_LOGFILESIZE	Size of the log file in megabytes (MB) NOTE:  If a log file size exceeds the value in the SEBLCL_LOGFILESIZE environment variable, a new log file is created.
SEBLCL_LOGARCHIVECOUNT	Maximum number of files to be archived
SEBLCL_TRACEUNICODE	True—Unicode trace is on False—Unicode trace is off

Please close all Internet Explorer Sessions and open new IE session after setting above environment variables.

If settings are done both at Server and Client the behavior is defined by below table.

Value on Client (SEBLCL_TRACEMODE environment variable)	Value on Server (ClntTraceMode parameter)	Client Output
Not Set	0	No log file
Not Set	1	Log file for all users
0	0	No log file
0	1	No log file for the current user
1	1	Log file for the current user and all users
1	0	Log file for the current user only

Please refer “Examples of Log Files for Client-Side Logging” to read the log file created

http://docs.oracle.com/cd/E14004_01/books/SysDiag/SysDiagClientSideLogging12.html

Configuring Standard Error Files

Standard error files contain process messages that are directed to standard error and standard out

1. On the computer running the Siebel Server, set the following environment variable to the given value:

SIEBEL_STDERROUT = 1

2. Stop and restart the computer running the Siebel Server for the environment variable to take effect.

Allow Admin users to Insert/Update/Delete on certain table

Allow Admin users to Insert/Update/Delete on certain table

How to create a trigger in oracle which will restrict insertion and update queries on a table based on a condition

CREATE OR REPLACE TRIGGER SIEBEL.BLOCK_NON_ADMIN_ACCESS

BEFORE DELETE OR INSERT OR UPDATE

ON SIEBEL.CX_ERROR_LOG

REFERENCING NEW AS NEW OLD AS OLD

FOR EACH ROW

begin

    IF sys_context('USERENV','SESSION_USER') NOT IN ('SADMIN', 'EIMUSER') THEN

        RAISE_APPLICATION_ERROR(-20000, 'You are not allowed to update table CX_ERROR_LOG. Please contact Application Support.');

    END IF;

END;

Forgot password of old Siebel DBF file sse_data.dbf

If you have an old Siebel database and you have forgotten the user id and password you can execute below set of command on that dbf to get your user id created on the dbf. Please find the steps as below.

Steps:

1)      Copy the .dbf to Tools\LOCAL

2)      Launch dbisqlc.exe from tools\bin

UserName = DBA

Password = ENTRPRISENAME

Click On Database Tab -> Select Database File as the .dbf in the Tools\LOCAL

Click on OK

3)      Once connected run below mentioned command.

grant connect to SSE_ROLE

grant connect to USERNAME identified by PASSWORD

grant connect to SIEBEL identified by PASSWORD

grant group to SSE_ROLE

grant membership in group SSE_ROLE to USERNAME

Commit

NOTE: USERNAME & PASSWORD Need to be in CAPITAL CASE

4)      Make environment specific changes in your Tools.cfg and create a local DSN to connect the .dbf file