Applies to:
Siebel Communications, SPE - Version: 8.0 [20405] - Release: V8Information 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 follwoing 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.
Please also try following command line and let me know if it helps to resolve the issue.
Solution-1:
1. Connect to srvrmgr using following command.
srvrmgr /g
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.
Applies to:
Siebel System Software - Version: 8.0.0.2 [20412] - Release: V8Siebel Remote - Version: 8.0.0.2 [20412] - Release: V8
HP-UX Itanium (32-bit)
Symptoms
Running the
Generate New Database Template job from the GUI
(without any parameters set)
failed,
and running the srvrmgr command
start task for comp gennewdb
resulted in
SBL-ADM-60070: Error reported on server 'siebsrvr1' follows:
SBL-SVR-01014: Internal: Could not send the HELLO message: (null)
SBL-NET-01023: Peer disconnected
GenNewDb_*.log (all event log levels set to 5)
showed the following errors:
GenericLog GenericError 1 00008b84496a5269:0 2009-01-13 08:08:57 SQL Message, 08001: [Siebel Database][ODBC Driver][Adaptive Server Anywhere]Unable to start database server
DBCLog DBCLogError 1 00008b84496a5269:0 2009-01-13 08:09:07 [Sybase][ODBC Driver][Adaptive Server Anywhere]Unable to start database server
GenericLog GenericError 1 00008b84496a5269:0 2009-01-13 08:09:07 SQL Message, 08001: [Siebel Database][ODBC Driver][Adaptive Server Anywhere]Unable to start database server
GenericLog GenericError 1 00008b84496a5269:0 2009-01-13 08:09:17 Error creating SQL Anywhere database template file (UTLOdbcConnect DBA/siebelmobiledb).
GenericLog GenericError 1 00008b84496a5269:0 2009-01-13 08:09:17 Error in MainFunction (CreateDbTemplateFile)
GenericLog GenericError 1 00008b84496a5269:0 2009-01-13 08:09:17 (gennewdb.cpp (610) err=524292 sys=2) SBL-GDB-00004: Error in Main function.
RecovTry RecovDBConn 1 00008b84496a5269:0 2009-01-13 08:09:23 Attempting to recover from a DB Connection Loss
Changes
The customer solved the error by
"adding lib server to SHLIB_PATH."
Now the database server can start the [Adaptive Server Anywhere] database
and the gennewdb task completes successfully.
Further details were not provided - the HP-UX environments in Tech Support already have the following settings in their siebenv.csh:
setenv SQLANY ${SIEBEL_ROOT}/SYBSsa90
and
setenv SHLIB_PATH ${SHLIB_PATH}:${SQLANY}/lib
on a standard installation,
so these settings MAY earlier have been manually removed.
Cause
not having
setenv SQLANY ${SIEBEL_ROOT}/SYBSsa90
and
setenv SHLIB_PATH ${SHLIB_PATH}:${SQLANY}/lib
in the siebenv.sh
or not sourcing siebenv.sh
may cause the errors above
Solution
make sure
setenv SQLANY ${SIEBEL_ROOT}/SYBSsa90
and
setenv SHLIB_PATH ${SHLIB_PATH}:${SQLANY}/lib
are included in your siebenv.sh
and the Siebel Server is restarted after changes.
Apologies for having partially duplicate information in the various sections of this document - the Metalink3 publishing "wizard" requires this separation, even if it may make published information more confusing than one combined solution text. Also apologies for the poor formatting - the wizard adds or removes line feeds on every update, so even after several corrections the formatting remains sub-optimal.
References
NOTE:503915.1 - Genewdb problemNOTE:522207.1 - Generate New Database Exits in Error
NOTE:523007.1 - S_SRM_REQUEST not cleaned up
Applies to:
Siebel Enterprise Integration Manager - Version: 7.7.2.5 SIA [18368] to 8.1.1.2 SIA[21215] - Release: V7 to V8Information in this document applies to any platform.
Symptoms
Exporting Attachments via EIM_CON_DTL leads to the following error messages seen for example in the Server Manager Command line window:SBL-ADM-60070: Error reported on server 'srvr1' follows:
SBL-SVR-01042: Internal: Communication protocol error while instantiating new task
SBL-EIM-00101: Invalid arguments passed to EIM.
SBL-EIM-00101: Invalid arguments passed to EIM.
IFB-File used:
----------------
[Siebel Interface Manager]
USER NAME = "SADMIN"
PASSWORD = "SADMIN"
PROCESS = Export
[Export]
TYPE = EXPORT
BATCH = 99
TABLE = EIM_CON_DTL
ATTACHMENT DIRECTORY = C:\temp
EXPORT MATCHES = S_CONTACT, (PERSON_UID = '1-2PGD')
Cause
The following extract of the resulting EIM-Log file is relevant in this regard:
UPDATE IT
SET IT.CON_BI = BT.BU_ID,
IT.CON_PERSON_UID = BT.PERSON_UID,
IT.CON_PRIV_FLG = BT.PRIV_FLG
, CON_PRIV_FLG = BT.PRIV_FLG
FROM dbo.EIM_CON_DTL IT, dbo.S_CONTACT BT
WHERE (BT.ROW_ID = IT.T_CONTACTTN_PARROW AND
T_CONTACTTN_PARROW IS NOT NULL AND
IF_ROW_BATCH_NUM = ?)
and error message:
[Microsoft][ODBC SQL Server Driver][SQL Server]Column name 'CON_PRIV_FLG' appears more than once in the result column list.
OR
[Microsoft][SQL Native Client][SQL Server]The column name 'CON_PRIV_FLG' is specified more than once in the SET clause. A column cannot be assigned more than one value in the same SET clause. Modify the SET clause to make sure that a column is updated only once. If the SET clause updates columns of a view, then the column name 'CON_PRIV_FLG' may appear twice in the view definition.
The matter has been reproduced
Solution
Although the EIM export task errored out the attachment was exported to the folder specified in the ATTACHMENT DIRECTORY IFB-parameter and the IF_ROW_STAT column of the EIM_CON_DTL table had a value of EXPORTED.
Product Defect 12-1OFLUGT has been raised to address the matter.
References
BUG:12-1OFLUGT - "SBL-EIM-00101: INVALID ARGUMENTS PASSED TO EIM" WHEN EXPORTING ATTACHMENTSApplies to:
Siebel Enterprise Integration Manager - Version: 8.0.0.2 [20412] - Release: V8Information in this document applies to any platform.
Symptoms
The EIM DELETE task does not complete successfully when deleting rows from S_CON_ADDR using EIM_ADDR_PER. The following errors are seen in the Server Manager Command line window when the EIM task is executed from the same:
SBL-ADM-60070: Error reported one server “SIEBEIM8” follows:
SBL-SVR-01054: The task exited without sending has response.
In attachment, a file log, a print screen and an ifb.
Cause
The following entry in the EIM-Log file is relevant:
"...
* [Del MyDelete] batch 100, step 2, pass 107: locate by user key
* (started at 6/9/08 3:03)
*/
UPDATE dbo.EIM_ADDR_PER
SET T_CON_ADDR__RID =
(SELECT MIN(BT.ROW_ID)
FROM dbo.S_CON_ADDR BT
WHERE (BT.RELATION_TYPE_CD = IT.CONADDR_RELATIONTY AND
(BT.START_DT = IT.CONADDR_START_DT OR
(BT.START_DT IS NULL AND IT.CONADDR_START_DT IS NULL)) AND
BT.ADDR_PER_ID = IT.T_CON_ADDR_ADDRPE AND
(BT.ACCNT_ID = IT.T_CON_ADDR_ACCNTI OR
(BT.ACCNT_ID IS NULL AND IT.T_CON_ADDR_ACCNTI IS NULL)) AND
(BT.CONTACT_ID = IT.T_CON_ADDR_CONTAC OR
(BT.CONTACT_ID IS NULL AND IT.T_CON_ADDR_CONTAC IS NULL)) AND
(BT.ORG_GROUP_ID = IT.T_CON_ADDR_ORGGRO OR
(BT.ORG_GROUP_ID IS NULL AND IT.T_CON_ADDR_ORGGRO IS NULL))))
FROM dbo.EIM_ADDR_PER IT
WHERE (CONADDR_RELATIONTY IS NOT NULL AND
T_CON_ADDR_ADDRPE IS NOT NULL AND
IF_ROW_BATCH_NUM = ? AND
IF_ROW_STAT_NUM = 0 AND
T_CON_ADDR__STA = 0)
?1: 100
go
..."
The problem is that the UPDATE statement from above is also checking for
S_CON_ADDR.ACCNT_ID/EIM_ADDR_PER.T_CON_ADDR_ACCNTI
and
S_CON_ADDR.START_DT/EIM_ADDR_PER.CONADDR_START_DT
respectively.
If those columns are not considered for the EIM_ADDR_PER load then the DELETE EXACT operation is failing as seen in the EIM-Log file:
"...Process [Del MyDelete] had 1 row fail
on EIM_ADDR_PER for batch 100 in step 2, pass 107:
Exact specification of rows were not found. (severity 4, row eliminated)
Rows which were specfied using exact deletion were not found by the user keys
specified in the interface table. Check that the key values specified in the IF
table exactly match a row in only one base table.
The rows were eliminated from further processing in this IF table. Processing
will continue for other rows in this interface table..."
Solution
Considering the S_CON_ADDR.ACCNT_ID and S_CON_ADDR.START_DT columns via their respective EIM_ADDR_PER columns resolves the behaviour. A sample script and IFB-File is shown below:
INSERT INTO EIM_ADDR_PER
(ROW_ID,
IF_ROW_BATCH_NUM,
IF_ROW_STAT,
AP_ADDR_NAME, -- S_ADDR_PER
AP_ALIGNMENT_FLG,
AP_DISACLEANSE_FLG,
AP_NAME_LOCK_FLG,
AP_PREMISE_FLG,
CONADDR_RELATIONTY, --S_CON_ADDR
CONADDR_START_DT,
CONADDR_ACTIVE_FLG,
CONADDR_BLADDR_FLG,
CONADDR_FRAUD_FLG,
CONADDR_MAINADDRFL,
CONADDR_SHIPADDRFL,
CONADDR_ACCNT_BU, -- S_CON_ADDR.ACCNT_ID
CONADDR_ACCNT_LOC,
CONADDR_ACCNT_NAME
)
VALUES
(1,
100,
'FOR_DELETE',
'MyAccntStreetAddress1, MyAccntCity1', -- S_ADDR_PER
'N',
'N',
'N',
'N',
'ContactPointUsage',
'2008-06-09',
'Y','N','N','N','N',
'Default Organization',
NULL,
'MyAccnt1'
)
-------
[Siebel Interface Manager]
USER NAME="SADMIN"
PASSWORD="SADMIN"
PROCESS = Del MyDelete
[Del MyDelete]
TYPE = DELETE
BATCH = 100
TABLE = EIM_ADDR_PER
DELETE EXACT = TRUE
ONLY BASE TABLES = S_CON_ADDR
References
Bookshelf, EIM Administration Guide, Chapter 7 Deleting Data, DELETE EXACT ParameterApplies to:
Product Release: V8 (Enterprise)Version: 8.0.0.1 [20408] Life Sci
Database: Microsoft SQL Server 2005
Application Server OS: Microsoft Windows 2003 Server SP2
Database Server OS: Microsoft Windows 2003 Server SP2
This document was previously published as Siebel SR 38-3460398791.
Symptoms
I'm getting the following error when trying to run EIM. This .ifb used to work.SBL-ADM-60070: Error reported on server 'SblCRMDev01' follows:
SBL-SVR-01054: The task exited without sending a response.
The only difference that I know of is that we have extended EIM_CONTACT several times. We didn't have a problem for the other ones, though.
I've attached the ifb file I'm using, the log file produced when logging was turned up and the crash file.
Let me know if you have any questions. Thanks.
425-478-1951
Solution
Message 1
For the benefit of othere readers,Customer experienced issues with columns created with the 'Case Insensitivity' wizard.
It has been determined that Customer ran the 'EIM Mapping Wizard' sometime after running the 'Case Insensitivity' wizard. For this reason the EIM mapper created eim columns and mappings for the case insensitive columns.
In order to avoid the above issue you should always make sure that the EIM Mapping wizard does not take such columns in account.
Additional Keywords: Case Insensitivity, EIM Mapping