Siebel SQLs/Error Messages >  Errors SBL-ESC-00006 and SBL-ADM-60070 when running Generate Triggers Server Task

Errors SBL-ESC-00006 and SBL-ADM-60070 when running Generate Triggers Server Task

APPLIES TO:
Siebel Communications, SPE - Version 8.0 [20405] to 8.2.2 SIA[22320] [Release V8]
Information in this document applies to any platform.

SYMPTOMS

Generate Trigger task exits with following error,

SBL-ESC-00006: Unable to connect to Database.
When tried to run the Generate Trigger task from command prompt, following error occured.

SBL-ADM-60070: Error reported on server 'icare-desk02' follows:
The following is the command was used to run GenTrig.

start task for component GenTrig with EXEC=True, Remove=False, PrivUser=SIEBEL, PrivUserPass=SIEBEL
CAUSE

As per the analysis of the environment following information was gathered.

Analysis of the GenTrigger Task log:

Enterprise : DEVSBL12
Server : icare-desk02
ODBC Data Source : DEVSBL12
Privileged User : SIEBEL

Error:

[Oracle][ODBC][Ora]ORA-01017: invalid username/password; logon denied
Unable to connect to the database...
Error in Connect
Message: ESCL-66, Additional Message: Error, Function: Connect
(gentrig.cpp (168) err=458758 sys=0) SBL-ESC-00006: Unable to connect to the database.

ODBC Data Source used by GenTring task was "DEVSBL12" where as it should be "DEVSBL12_DSN".

Secondly, there is "-" (Hyphen) character in Siebel Server name and hence when command is submitted to srvrmgr, it takes it as switch.

SOLUTION

Out of two solutions provided, Solution-1, resolved the issue.

Solution-1:

1. Connect to srvrmgr using following command.

srvrmgr /g /e DEVSBL12 /s "icare-desk02" /u sadmin /p xxxxx(password for sadmin)
Note, YOUR_GATEWAY_ADDRESS is hostname where your gateway is installed.

In command suggested, please note the double quote (") around the Siebel Server name.

2. Run the command to start GenTrig job.

start task for comp GenTrig with EXEC=True, Remove=False, PrivUser=SIEBEL, PrivUserPass=SIEBEL
3. Verify the result.

Solution-2:

It seems that GenTring Job is trying to connect to DSN which does not exist.

To verify what we can do is, create the new DSN with exactly same parameter and name it "DEVSBL12" and again run the job from UI. If at all GenTring refers to wrong DSN, it should work once you define the DSN.