| Siebel SQLs/Error Messages > Siebel Error Messages - SBL-GEN-03002, SBL-GEN-03006, SBL-GEN-03007, SBL-GEN-03008
SBL-GEN-02004 Message number was changed for %1SBL-GEN-02004 Message number was changed for %1
SBL-GEN-02005 Internal: language code specified was different from previous value
SBL-GEN-02006 Unrecognized language code %1 was specified
SBL-GEN-02007 Internal: message cache size specified was different from previous value
SBL-GEN-02008 Internal: message fac structure not found
SBL-GEN-02009 Could not open Siebel message file %1
SBL-GEN-02010 Error parsing Siebel message file
SBL-GEN-02011 Error parsing Siebel message file header: incorrect facility name
SBL-GEN-02012 Error parsing Siebel message file header: incorrect language code
SBL-GEN-02013 Error parsing Siebel message file header: facility name not found
SBL-GEN-02014 Error parsing Siebel message file header: file format not found
SBL-GEN-02015 Error parsing Siebel message file: bad message format
SBL-GEN-02016 Internal: message facility not initialized
SBL-GEN-02017 SQL error in message facility
SBL-GEN-02018 Unsupported database type: %1
SBL-GEN-02019 Internal: bad message count
SBL-GEN-02020 Internal: bad message macros
SBL-GEN-02021 Message string was truncated due to insufficient buffer space
SBL-GEN-02022 Msgfiles not found for lang '%1'. Please specify the language installed using the / l<lang> on the command line.#
SBL-GEN-03001 Error allocating %1
SBL-GEN-03002 Required parameter %1 is NULL
APPLIES TO:
Siebel Assignment Manager - Version 8.1.1.14.7 [IP2014] and laterInformation in this document applies to any platform.SYMPTOMSAssignment Manager failed to retrieve candidate id. During rule evaluation an error was raised and the default employee was not assigned. The following was logged in AsgnSrvr log file:
Match Criterion 4 000016cd55a408d0:0 2015-07-15 12:48:04 -------------------- END
CRITERIA EVALUATION
-----------------------Match Object 2 000016cd55a408d0:0 2015-07-15 12:48:04 Sql after substitute Parameters for Dynamica Candidate: SELECT A1.FRD_OWNER_EMP_ID FROM SIEBEL.S_ORG_EXT A1, SIEBEL.S_SRV_REQ A2 WHERE A1.PAR_ROW_ID = A2.CST_OU_ID AND A2.ROW_ID = ?GenericLog GenericError 1 000016cd55a408d0:0 2015-07-15 12:48:04 (asgnengi.cpp (2239) err=3002 sys=0) SBL-GEN-03002: Required parameter Candidate Id in the team table is NULLMatch Error 1 000016cd55a408d0:0 2015-07-15 12:48:04 Error loading dynamic candidate attribute values from the team table for object row id 1-RIN8L9 This can happen when dynamic candidates are based on a base table (e.g. S_ORG_EXT) instead of an intersection table (e.g. S_ACCNT_EMP) and a record in the base table is retrieved but the candidate id is not populated.
CAUSE
The problem was due to dynamic candidates based on base table S_ORG_EXT and Candidate Column S_ORG_EXT.FRD_OWNER_EMP_ID. Record is retrieved from S_ORG_EXT but column FRD_OWNER_EMP_ID is empty.If this is the case an error "SBL-GEN-03002: Required parameter Candidate Id in the team table is NULL" is received. With this error exception the evaluation is interrupted and the default employee is not assigned. reproduced and verified the problem in standard Siebel 8.1.1.14.7 [IP2014]
SOLUTION
In order to avoid this problem a criteria can be added to the rule such that the rule is not executed if the candidate id field is null:
1) Create a new Workflow Policy Column for the candidate id column.2) Create a new Assignment Criteria with this Workflow Policy Column.3) Create a new Assignment Attribute based on the Assignment Criteria.4) Use the Criteria in the Rule to avoid assignment if the column is null
SBL-GEN-03003 %1 (err=%sysError, sys=%2)
SBL-GEN-03004 Could not find message string for code=%1
SBL-GEN-03005 No data found for %1
SBL-GEN-03006 Error calling function: %1
SBL-GEN-03006 Error when Calling Function: DICInsRowExecStmt for Assignment (Doc ID 805265.1)
APPLIES TO:
Siebel Assignment Manager - Version 8.0.0.6 SIA [20423] and laterInformation in this document applies to any platform.
*** Checked for relevance on 20-July-2017 *** SYMPTOMSOn invoking Batch assignment for the standard "Order (Sales Credit Assignment)" assignment object, the following error is observed in the log :
SBL-GEN-03006 Error when calling the function: DICInsRowExecStmt for Assignment.
Additional Message: pfNativeError: -99999; szSQLState: 22007; szErrorMsg: [IBM][CLI Driver] CLI0113E SQLSTATE 22007: An invalid datetime format was detected; that is, an invalid string representation or value was specified. SQLSTATE=22007
SQLError Statement 0 0000000349d24d38:0 2009-03-31 13:10:55 SQL Statement: INSERT INTO SIEBEL.S_ORD_CRDT_ASGN ...
CAUSE
This is related to the S_ORD_CRDT_ASGN.START_DT field. This field is required, but no default has been set on the field.
Based on the INSERT statement, the field has been set with the null value which leads to the error :
[DataDirect][ODBC Oracle driver][Oracle]ORA-01400: cannot insert NULL into ("SIEBEL"."S_ORD_CRDT_ASGN"."START_DT")(asgnasgn.cpp (5357) err=3006 sys=0) SBL-GEN-03006: Error calling function: DICInsRowExecStmt
Additional Message: pfNativeError: -99999; szSQLState: 22007; szErrorMsg: [IBM][CLI Driver] CLI0113E SQLSTATE 22007: An invalid datetime format was detected; that is, an invalid string representation or value was specified. SQLSTATE=22007
SOLUTION
On the Assignment object, change the Position table to s_order_postn. In this case, a new workflow policy object has been created to accommodate a new Order assignment object referencing this position table, "s_order_postn"
Unpublished (Internal) Bug 10564768 has been logged to address the issue with the S_ORD_CRDT_ASGN position table when running assignment for "Order (Sales Credit Assignment)" object.
Error with running Assignment Manager, SBL-GEN-03006 (Doc ID 530830.1)
SYMPTOMSCustomer was using Assignment Manager with an organization workload distribution rule looking at Service Requests that have a status of "Submitted". When they tried to run a batch assignment job to test it, they got the error SBL-GEN-03006. The only change to the underlying Service Request Assignment Object was the default organization.
CAUSEFor the benefit of other readers, the requirement was to use Assignment Manager to assign Service Requests to Organizations, according to Workload Distribution Rules.
A Workload Distribution Rule was defined, with Service Request Status = “Submitted”, and this was included in an Assignment Rule. On running Batch Assignment, this resulted in the following error :-
SBL-GEN-03006: (attrapi.cpp: 953) error code = 3006, system error = 3756, msg1 = pLinkColInfo is NULL, SBL-GEN-03006: (asgnengi.cpp: 6002) error code = 3006, system error = 0, msg1 = WFGetCount,
In a similar reported issue, it was noted:
“Workload criteria should be associated ONLY when the Workload Rule Object has the team table (or Owner field) referenced under its Workflow Components. If the Workload Object Rule does not reference Team Table (or Candidate field) in the Workflow Components properly, Assignment Manager will encounter the errors mentioned above.
Bug 10500482 has been logged to document the above behavior in the Siebel Bookshelf.”
In this scenario, where Organization Workload is being implemented (under the Organization Distribution Workload tab), the Service Request Workflow Policy Object should contain a Workflow Policy Component for the S_SRV_REQ_BU table, and this should contain Workflow Policy Column S_SRV_REQ_BU.BU_ID.
SOLUTIONThe following were the suggested steps to do this :-
1. Create a new Workflow Policy Column, named 'Service Request Org Team', based on S_SRV_REQ_BU.BU_ID.
2. For Workflow Policy Object 'Service Request', add a new Workflow Component named 'SR Organization Team' with the following properties :-
Source Table Name=S_SRV_REQ_BUSource Column Name=SRV_REQ_IDTarget Component=Service RequestTarget Column Name=ROW_ID
3. For this Workflow Policy Component, add the Workflow Policy Column created in 1.
4. Shutdown and startup the Batch Assignment component.
5. Re-test.
This resolved the reported error. Bug 10500482 has been logged to provide a useful error message should the Workflow Policy Object be found not to include the required team objects.
Please also refer to: SBL-GEN-03006 when Attempting Campaign Contact or Asset Assignment with Workload Rules (Doc ID 831085.1)
Batch Assignment Component Is No Longer Running In Production with Error SBL-GEN-03006 (Doc ID 1338175.1) APPLIES TO:Siebel Assignment Manager - Version 7.8.2.14[19251] to 8.2.2.3 SIA [23021] [Release V7 to V8]Information in this document applies to any platform.**checked for currency 25-JUNE-2013**SYMPTOMSOn : 7.8.2.14[19251] version, Assignment Manager
When attempting to run batch assignment, the component job fails the following error occurs.
ERROR-----------------------SBL-GEN-03006
STEPS-----------------------The issue can be reproduced at will with the following steps:1. Start BatchAsgn.2. Error shows in log and component fails
CAUSE
There was a problem with the number of primary components in the TM Asset Workflow Policy Object. A workflow policy object can only have 1 workflow policy compoennt designated as primary.
The log showed the following error:
ProcReq GenericFatal 0 0 2011-07-11 09:10:22 TM Asset in LoadLink
GenericLog GenericError 1 0 2011-07-11 09:10:22 Message: Multiple primary tables defined for object,Additional Message: TM Asset
ProcReq GenericFatal 0 0 2011-07-11 09:10:22 TM Asset in LoadLink
GenericLog GenericError 1 0 2011-07-11 09:10:22 Message: Failed to load link information for object,Additional Message: TM Asset
ProcReq GenericFatal 0 0 2011-07-11 09:10:22 TM Asset in Load
GenericLog GenericError 1 0 2011-07-11 09:10:22 Message: Failed to load object definition,Additional Message: TM Asset
GenericLog GenericError 1 0 2011-07-11 09:10:22 (attrapi.cpp (733) err=700106 sys=2) SBL-ESC-00106: Error loading Attribute handle for Object TM Asset.
GenericLog GenericError 1 0 2011-07-11 09:10:22 (asgnobj.cpp (345) err=3006 sys=0) SBL-GEN-03006: (asgnobj.cpp: 345) error code = 3006, system error = 0, msg1 = WFObjectOpen, msg2 = (null), msg3 = (null), msg4 = (null)
SOLUTION
1. With Siebel Tools pointed at the server database go to Workflow Policy Object and query for TM Asset2. Expand on left and go to Workflow Policy Component3. Examine the component, 2 of the listed components (tables) have the primary column checked, there should only be one checked and there should be 1 active component marked primary. In general the correct one is for table s_asset. Clear the one that is checked as extra or activate the primary if marked inactive.4. Restart both assignment manager Nd batch assignment components and see if the error clears
AsgnSrgr Getting The Error, SBL-GEN-03006: Error Calling Function: DICFindTable Target Table (Doc ID 2096010.1)
APPLIES TO:
Siebel Assignment Manager - Version 8.1.1.14.11 [IP2014] and laterInformation in this document applies to any platform.SYMPTOMSOn : 8.1.1.14.11 [IP2014] version, Assignment Manager
AsgnSrvr component fails to start with an error.
ERROR-----------------------GenericLog GenericError 1 0001e01e566d0554:0 2015-12-15 11:28:45 pTableName is NULL or empty
GenericLog GenericError 1 0001e01e566d0554:0 2015-12-15 11:28:45 (asgnobj.cpp (2249) err=3006 sys=2) SBL-GEN-03006: Error calling function: DICFindTable Target Table
CAUSE
There can be some invalid configurations on assignment object(s) in Siebel Repository. In this case, the SQL proceeding to the error is for loading the dynamic candidate components for all assignment objects in 'Siebel Repository' for that environment. It can be one or more Assignment Object(s) having invalid dynamic candidate configuration. Here is the SQL:
SELECT DISTINCT AO.NAME, C.NAME, C.TM_TYPE_CD, DCC.NAME, DCC.PRIMARY_FLG, DCC.CNDT_TABLE_FLG, DCC.SRC_TBL_NAME, DCC.SRC_COL_NAME, DCC.TGT_DYN_COMP_NAME, DCCTT.SRC_TBL_NAME, DCC.TGT_COL_NAME, DCC.ADDL_JOIN_SPEC, DCC.CNDT_ID_COL, DCC.SCORE_COL, DCCCOL.ROW_ID, DCC.ROW_ID FROM SIEBEL.S_ASGN_OBJECT AO, SIEBEL.S_ASGN_CNDT C, SIEBEL.S_ASGN_DYN_COMP DCC, SIEBEL.S_ASGN_DYN_COMP DCCTT, SIEBEL.S_ASGN_DCMP_COL DCCCOL WHERE C.ASGN_OBJECT_ID = AO.ROW_ID AND C.ROW_ID = DCC.ASGN_CNDT_ID AND DCC.TGT_DYN_COMP_NAME = DCCTT.NAME (+) AND DCC.ASGN_CNDT_ID = DCCTT.ASGN_CNDT_ID (+) AND DCC.ROW_ID = DCCCOL.ASGN_DYN_COMP_ID (+) AND AO.INACTIVE_FLG= 'N' AND C.INACTIVE_FLG='N' AND DCC.INACTIVE_FLG='N' AND DCCTT.INACTIVE_FLG (+) = 'N' AND DCCCOL.INACTIVE_FLG (+) = 'N' AND AO.REPOSITORY_ID = C.REPOSITORY_ID AND C.REPOSITORY_ID = DCC.REPOSITORY_ID AND DCC.REPOSITORY_ID = ? ORDER BY AO.NAME, C.NAME, DCC.NAME
SQLSlowQuery Bind Variables 4 0001e01e566d0554:0 2015-12-15 11:28:45 01:1-4UR6-1
It can be the 'Source Column Name' of primary Dynamic Candidate Component, the primary component has the Primary flag checked. You can see in Siebel Tools > Workflow Policy Object > Assignment Object > Dynamic Candidate > Dynamic Candidate Component. The 'Source Column Name' should be set to ROW_ID of the table in 'Source Table Name'. If it is left blank then the message 'pTableName is NULL or empty' can fail the assignment component at component start-up.
Out of the box, Activity assignment object is the only one that has dynamic candidate configured. You can look at Activity assignment object to get an understanding how the Dynamic Candidate Components and the primary Dynamic Candidate Component are configured, and the 'Source Column Name'. For vanilla Activity assignment object's primary Dynamic Candidate Component, The Source Table Name = S_EVT_ACT, Source Column Name = ROW_ID, the primary flag is checked.
SOLUTION
2 Suggestions:
1. You can manually execute the above SQL with the bind variable substituted in the Siebel database for that environment:
SELECT DISTINCT AO.NAME, C.NAME, C.TM_TYPE_CD, DCC.NAME, DCC.PRIMARY_FLG, DCC.CNDT_TABLE_FLG, DCC.SRC_TBL_NAME, DCC.SRC_COL_NAME, DCC.TGT_DYN_COMP_NAME, DCCTT.SRC_TBL_NAME, DCC.TGT_COL_NAME, DCC.ADDL_JOIN_SPEC, DCC.CNDT_ID_COL, DCC.SCORE_COL, DCCCOL.ROW_ID, DCC.ROW_ID FROM SIEBEL.S_ASGN_OBJECT AO, SIEBEL.S_ASGN_CNDT C, SIEBEL.S_ASGN_DYN_COMP DCC, SIEBEL.S_ASGN_DYN_COMP DCCTT, SIEBEL.S_ASGN_DCMP_COL DCCCOL WHERE C.ASGN_OBJECT_ID = AO.ROW_ID AND C.ROW_ID = DCC.ASGN_CNDT_ID AND DCC.TGT_DYN_COMP_NAME = DCCTT.NAME (+) AND DCC.ASGN_CNDT_ID = DCCTT.ASGN_CNDT_ID (+) AND DCC.ROW_ID = DCCCOL.ASGN_DYN_COMP_ID (+) AND AO.INACTIVE_FLG= 'N' AND C.INACTIVE_FLG='N' AND DCC.INACTIVE_FLG='N' AND DCCTT.INACTIVE_FLG (+) = 'N' AND DCCCOL.INACTIVE_FLG (+) = 'N' AND AO.REPOSITORY_ID = C.REPOSITORY_ID AND C.REPOSITORY_ID = DCC.REPOSITORY_ID AND DCC.REPOSITORY_ID = '1-4UR6-1' ORDER BY AO.NAME, C.NAME, DCC.NAME
and inspect the results to see which assignment object (AO.NAME) having primary component (DCC.PRIMARY_FLG should show Y) has blank or invalid 'Source Column Name' (DCC.SRC_COL_NAME in the SQL). Those are the ones you need to correct in Siebel Tools > Workflow Policy Object > Assignment Object > Dynamic Candidate > Dynamic Candidate Component. . Make sure the changes are saved in the Siebel database. Restart Assignment Manager component to see if the error is resolved.
2.If you have another environment that doesn't have this problem, you execute the same SQL with the correct repository's ROW_ID substituted in the SQL and execute the SQL in the Siebel database for the working environment, and compare the SQL results from 2 environment. To get the repository's ROW_ID for the other environment, you can execute the following in the other Siebel database:
select ROW_IDfrom S_REPOSITORYwhere NAME = 'Siebel Repository'
SBL-GEN-03007 SQL error: native=%1, state=%2, message=%3
Siebel Remote: Transaction Merger failing with errors due to custom database trigger (Doc ID 1902896.1)
APPLIES TO:
Siebel Consumer Goods - Version 8.1.1.2 SIA[21215] and laterInformation in this document applies to any platform.SYMPTOMSSiebel Remote - on version 8.1.1.6 SIA [21233]:
Transaction Merger (TxnMerge) tasks are failing while processing DX files for certain remote user; component remains online.
Affected user's INBOX folder was temporarily renamed as per Document 475974.1 to allow processing of other users' data.However, if other users would generate similar txns, it would be expected that the same problem to affect many Remote users.
Impact of the issue: DX files from affected user(s) could not be imported into Server DB; user(s) should not be allowed to synchronize until issue is fixed.
CAUSE
Cause of the error:
SCENARIO 1 (Oracle RDBMS):a) based on provided TxnMerge_*.log files - the error is not actually caused by a problematic txn contained in the DX file; the error is related to execution of a custom trigger that is defined on that Siebel base table:
GenericLog GenericDetail 4 0000034c53723c60:0 2014-05-14 02:21:17 Processing operation: Operation: DRowId: 2EF-1451TableName: S_NOTE_ACCNTTrans RowId: 2EF-12Y8...SQLError Statement 0 0000034c53723c60:0 2014-05-14 02:21:17 SQL Statement:DELETE FROM SIEBEL.S_NOTE_ACCNTWHERE ROW_ID = ?SQLError Bind Variables 1 0000034c53723c60:0 2014-05-14 02:21:17 01:2EF-12Y8
DBCLog DBCLogError 1 0000034c53723c60:0 2014-05-14 02:21:17 [DataDirect][ODBC Oracle driver][Oracle]ORA-01427: single-row subquery returns more than one rowORA-06512: at "SIEBELETL.PROC_NOTE_ACCNT", line 27ORA-06512: at "SIEBELETL.Z_SIB_TRIG_NOTE_ACCNT", line 239ORA-04088: error during execution of trigger 'SIEBELETL.Z_SIB_TRIG_NOTE_ACCNT'
DBCLog DBCLogError 1 0000034c53723c60:0 2014-05-14 02:21:17 (dberror2.cpp(0) err=3007 sys=0) SBL-GEN-03007: SQL error: native=1427, state=S1000, message=[DataDirect][ODBC Oracle driver][Oracle]ORA-01427: single-row subquery returns more than one row
b) So whatever that trigger 'SIEBELETL.Z_SIB_TRIG_NOTE_ACCNT' was supposed to do - this is a custom trigger defined on a Siebel base table; this fails to execute the code it was supposed to due to an Oracle error:"ORA-01427: single-row subquery returns more than one row"
SCENARIO 2 (Microsoft SQL Server RDBMS):
a) In TxnMerge log file - error stack was like this:
...SQLError Statement 0 00000002554c374c:0 2015-05-08 10:22:31 SQL Statement:DELETE FROM dbo.S_EVT_ACTWHERE PAR_EVT_ID IN ('2IM-1RX', '')...DBCLog DBCLogError 1 00000002554c374c:0 2015-05-08 10:22:31 (dberror2.cpp(0) err=3007 sys=2) SBL-GEN-03007: SQL error: native=2601, state=23000, message=[Microsoft][SQL Native Client][SQL Server]Cannot insert duplicate key row in object 'dbo.DT_S_EVT_ACT_tbl' with unique index 'DT_S_EVT_ACT_tbl_Idx1'. The duplicate key value is (May 8 2015 10:22AM)....DBCLog DBCLogError 1 00000002554c374c:0 2015-05-08 10:22:31 (dberror2.cpp(0) err=3007 sys=0) SBL-GEN-03007: SQL error: native=3621, state=01000, message=[Microsoft][SQL Native Client][SQL Server]The statement has been terminated....GenericLog GenericError 1 00000002554c374c:0 2015-05-08 10:22:31 Message: GEN-10,Additional Message: Calling Function: TXMMainFunction; Called Function: MRGMainFunctionGenericLog GenericError 1 00000002554c374c:0 2015-05-08 10:22:31 (txnmerge.cpp (635) err=262149 sys=0) SBL-TXM-00005: Error in the main function. Please refer to the detailed log message elsewhere in this file.
b) Similarly here - problem is not related to S_EVT_ACT table DELETE operation, but appears as the custom trigger defined on the table would attempt to insert some data in a custom table and this would result into an unique index violation on that table.
SCENARIO 3 (DB2 RDBMS):
a) In TxnMerge log file - error lines were like this:
GenericLog GenericError 1 0000000256ca17e8:0 2016-02-22 05:15:02 Message: Generated SQL statement:,Additional Message: SQLExecute: INSERT INTO SBL.S_EVT_ACT (ACCNT_ISSUE_ID, ACCNT_OBJCTV_ID, ...GenericLog GenericError 1 0000000256ca17e8:0 2016-02-22 05:15:02 Message: Error: An ODBC error occurred,Additional Message: Function: DICInsRowExecStmt; ODBC operation: SQLExecuteSQLError Statement 0 0000000256ca17e8:0 2016-02-22 05:15:02 SQL Statement:INSERT INTO SBL.S_EVT_ACT (ACCNT_ISSUE_ID, ACCNT_OBJCTV_ID,... DBCLog DBCLogError 1 0000000256ca17e8:0 2016-02-22 05:15:02 [IBM][CLI Driver][DB2] SQL0723N An error occurred in a triggered SQL statement in trigger "SBL.S5I". Information returned for the error includes SQLCODE "57033", SQLSTATE "00C90088,00000D01,00000291.00000207" and message tokens "2". SQLSTATE=09000GenericLog GenericError 1 0000000256ca17e8:0 2016-02-22 05:15:02 Message: Error: An ODBC error occurred,Additional Message: pfNativeError: -723; szSQLState: 09000; szErrorMsg: [IBM][CLI Driver][DB2] SQL0723N An error occurred in a triggered SQL statement in trigger "SBL.S5I". Information returned for the error includes SQLCODE "57033", SQLSTATE "00C90088,00000D01,00000291.00000207" and message tokens "2". SQLSTATE=09000GenericLog GenericError 1 0000000256ca17e8:0 2016-02-22 05:15:02 Pessimistic Insert: unable to insert a row. Table S_EVT_ACT, RowId 4JEQ-8F.The row had the following <attribute, value> pairs:<ROW_ID, 1JEG-U2><CREATED, 2016-02-22 09:37:35.000000><LAST_UPD, 2016-02-22 09:37:35.000000>... GenericLog GenericError 1 0000000256ca17e8:0 2016-02-22 05:15:02 (mrgsins.cpp (660) err=1638558 sys=2) SBL-MRG-00158: Pessimistic Insert: unable to insert a row.
b) Similarly here - the problem is not related to S_EVT_ACT table INSERT operation, but due to the fact that the trigger defined on the base table would cause a deadlock condition on the DB.
Obvious reason for what happens in these cases is:- the DX file contained some perfectly valid txns to be applied by TxnMerge;- but due to some bad trigger logic, other non-Siebel tables involved (i.e. bespoke ETL functionality) or other DB specific conditions, the trigger returns DB errors preventing Merger to complete the operation - ORA-01427 in first case, duplicate key violation error in the second case or deadlocks in last example.
SOLUTION
The problem is not caused by the txns contained in DX file or by TxnMerge comp itself but by custom triggers defined on Siebel Base tables.
Normally it is not supported nor recommended to have such custom triggers in place; except for out-of-the-box triggers defined in Siebel schema, creating any other such trigger should only be made under supervision of or reviewed and approved by Oracle / Siebel ACS Expert Services team.
So in all cases it was suggested to involve the DBA team and/or SQL developer(s) who wrote those triggers / designed the custom tables and implemented those solutions to investigate why trigger execution fails and to find the best way to ensure that would complete fine to allow DX file being merged into database.
SBL-GEN-03008 Error calling %1 for %2
Siebel Application customers using Siebel Remote on version 8.x and 8.1.x may encounter some error conditions (Doc ID 956182.1)
DESCRIPTION
Customers using Siebel Remote may encounter various errors. These errors have been addressed in Fix Packs, Quick fixes or may have temporary workarounds available. Below is a list of the known defects, a clear description to help you identify if you have hit this defect and a table that lists in what fix pack (FP) or quick fix (QF) the defect has been fixed. This alert will be updated as required to keep customers informed of defects as well as fixed versions. FP's and QF's can be downloaded from My Oracle Support from the "Patches & Updates" tab
The below list is not exhaustive but includes the most critical defects that have been identified.
* Note that after installing the fix for CR # 12-1T2IN2L (Bug:10565949) some customer then experienced another behavior CR # 12-1U0AX75 (Bug:10570714) brought about by applying the fix.
As a result of this situation a new CR was created CR #12-1VNIMYR (Bug:10582025) to provide a thorough, redesigned and complete solution for these two behaviors. Therefore the fix for CR #12-1VNIMYR (Bug:10582025) is a complete solution for both CR # 12-1T2IN2L (Bug:10565949) and CR # 12-1U0AX75 (Bug:10570714)
Every customer that is running Siebel in version 8.0.x and 8.1.x should apply the complete solution. Please see the below table for details.
1) Change Request 12-1T2IN2L Bug:10565949Transaction Processor may encounter slow performance. Customer may notice this performance issue soon after moving to Siebel 8.x or 8.1. This behavior has been detailed in the following Alert: Transaction Processor can exhibit slow performance Note 841888.12) Change Request 12-1TUWRGV Bug:105695973) Change Request 12-1QVMO57 Bug:10555407
In certain situations .dx files can be malformed and missing the table name value. There are 2 Change Requests created to address this behavior. Though the end result is the same the behavior can occur in two distinct scenarios. The .dx file created looks similar and in both cases the TableName is missing.Example:Txn Type : STxn Id : 1176656580Src Node : 1-2PPG-2Created By : 1-2I2UDDLog Row Id: 1-R231-1
OperType : Cascade / MergeTableName: Txn Id: 1176656580File Table : UnknownCol 0 (C): CON_PER_IDCol 1 (C): ROW_IDOld 0 : 2IPQ-IAIOld 1 : Operation 0 (Cascade Delete ): S_CALL_LST_CON.CON_PER_ID
Customer will find the following errors in the Transaction Merger log file or the client applythrd_xxx_yyy.log file
GenericLog pTableName is NULL or emptyGenericLog SBL-GEN-03006: Error calling function: DICFindTable
4) Change Request 12-1L0YDDK Bug:10529443 Under certain conditions Transaction Merger or the client applythrd may fail when processing an update within a .dx file.The .dx file itself is not malformed but during the update process two system columns are listed twice in the update statement causing an error condition.DB_LAST_UPD and DB_LAST_UPS_SRCNote 848264.1
Set clause for column 'DB_LAST_UPD' used incorrectly for the client applythrd.log fileColumn name 'DB_LAST_UPD' appears more than once in the result column list. for the Transaction Merger log fileor[DataDirect][ODBC Oracle driver][Oracle]ORA-00957: duplicate column name5) Change Request 12-1RPD2ML Bug:10559246Customers have experienced visdata corruption while running Transaction Router and Transaction Processor in a Siebel 8 environment. This behavior has been detailed in the following Alert: Transaction Router and Transaction Processor may encounter visdata.dbf file corruption in Siebel 8 remote environment Note 763195.1
6) Change Request 12-1U0AX75 Bug:10570714After applying the fix for the Transaction Processor performance condition identified in 1) above it is possible another error can occur. After Transaction Processor restarts it will begin to read transactions from the Low Scan Mark (an internal marker). These transactions have already been routed by the Transaction Processor and the Transaction Router. The processor places these already routed transactions in the next sequential .dx file - example 101.dx file. Since the transactions within the dx file have already been routed the Transaction Processor will delete this dx file(s) once it starts the Clean File routine. The Transaction Router will start and will be looking for the next sequential dx file in the TXNPROC folder (101.dx). If Transaction Router cannot find the dx file (101.dx) it will fail with:
Read error - system error code 2Message: Unable to open User Txn Log file for reading or writing.,SBL-DCK-00142: Error opening transaction file (...) for read7) Change Request 12-1UP4EOX Bug:10574894Running the Database Extract task with certain parameter settings can cause the Transaction Router to fail. Using both the List method and the Optimal Mode=TRUE setting will cause this error condition.This behavior has been detailed in the following Alert: Running Database Extract with specific settings causes Transaction Router to fail Note 948203.1OCCURRENCECustomers using Siebel Remote and Replication on version 8 are likely to encounter these error conditions. Some of these Change Requests have been addressed in Fix Packs. In other cases a Quick Fix may be required on top of the current version.
SYMPTOMS
Here are the error messages you may find in each scenario.
The error message for Change Request 12-1TUWRGV Bug:10569597 and Change Request 12-1QVMO57 Bug:10555407
GenericLog pTableName is NULL or emptyGenericLog SBL-GEN-03006: Error calling function: DICFindTable
The error message for Change Request 12-1L0YDDK Bug:10529443
Set clause for column 'DB_LAST_UPD' used incorrectly. Found in the client applythrd.log file
Column name 'DB_LAST_UPD' appears more than once in the result column list.[DataDirect][ODBC Oracle driver][Oracle]ORA-00957: duplicate column name Found in the Transaction Merger log file
The error message for Change Request 12-1U0AX75 Bug:10570714:
Read error - system error code 2Message: Unable to open User Txn Log file for reading or writing.,SBL-DCK-00142: Error opening transaction file (...) for read.
The error message for Change Request 12-1RPD2ML Bug:10559246:
Unable to open visibility database in 10 of 10 tries....SBL-CSC-00213: Invalid visibility database.SBL-CSC-00200: Cannot acquire spinlock createLatch
The error message for Change Request 12-1UP4EOX Bug:10574894:
SBL-GEN-03006: Error calling function: GetNodeProcessPrefWORKAROUNDBug:10574894:In order to workaround this issue do not use both the list method of extracting users and the Optimal Mode setting together.
srvrmgr:app1> start task for comp dbxtract with client=@c:\clients.txtsrvrmgr:app1> start task for comp dbxtract with client=CLIENT1, optmode=TRUEThe default setting for Optimal Mode for the Database Extract component is FALSE
Bug:10559246:
Stop all running Routers and Processors. Uncheck ( set to FALSE) the Optimized Visibility Check preference. By default this Remote System Preference is TRUE. You can find this preference in Administration-Siebel Remote> Remote System Preferences > checkbox bottom left of this applet. Unchecking does not require service restart. In addition there is no negative impact of unchecking this preference. Start Processor and Router.
Bug:10570714: **(This is a manual workaround the complete and best solution for this behavior is to apply the fix for Bug:10582025)
Increase the TP parameter Clean .dx files iterations to a large value so it will not delete .dx files until the Transaction Router has had an opportunity to process them. Be sure to increase the parameter on each Transaction Processor in the environment. Increasing the value from 1 to a value between 100-200 for Clean .dx files iterations should prove effective. Do not run the Transaction processor without running the Transaction Router as well. There is no negative impact on processing. The TXNPROC directory will grow large until the Transaction processor purges the .dx files. For Example if setting the Clean.dx file iteration to 150
| 
