Table 2. Message Categories
---------------------------------------------------
Message Number Message Category
---------------------------------------------------
11xxx - 12xxx Siebel Analytics Communications Messages
13xxx General Security Messages
14xxx - 15xxx Internal Navigation Messages
16xxx ODBC Access Messages
17xxx - 18xxx Oracle Access Messages
19xxx - 27xxx SQL Preparation Messages
28xxx UDML Parser Messages
29xxx Repository Metadata Messages
30xxx - 32xxx Join and UDML Generation Messages
34xxx - 40xxx General Administration Tool Messages
41xxx Siebel Analytics Client Messages
42xxx Request Generation Messages
43xxx Siebel Analytics Server Access Messages
44xxx Exception Messages
46xxx - 48xxx Utility and Configuration Messages
49xxx Communication Access Messages
51xxx General Siebel Analytics Server Messages
52xxx Cache Storage Messages
53xxx LDAP Security Messages
54xxx Connection Pool Messages
55xxx - 58xxx Cache Management Messages
59xxx Query Execution Messages
60xxx External Access Messages
61xxx File Management Messages
62xxx Metadata Import Messages
63xxx - 64xxx XML Gateway Messages
65xxx Relational Datasource Adapters Messages
66xxx - 68xxx Siebel Analytics Scheduler Messages
69xxx - 72xx Siebel Analytics Cluster Server Messages
73xxx Siebel Analytics Client Communication Messages
75xxx Siebel Analytics Scheduler Mail Access Messages
76xxx Siebel Analytics Scheduler Client Messages
77xxx Siebel iBot API Messages
.
Thursday, August 28, 2008
Siebel Analytics Answers Erros out ORA-03113
ORA-03113: end-of-file on communication channel errors in Siebel Answers
Running a Request in Siebel Answers gives Oracle Error.
1: Select Few columns from opportunity, position dimension and Revenue Fact in siebel Answers, when we ran the Request it gives Odbc Erros saying ORA-03113: end-of-file on communication channel errors.
2: when we Take the Physical SQL from the log file and Ran the same query in toad, here too it gave the same Error.
3: when we checked with the DBA it was giving an Oracle Internal Error "Core dump"
4: After debugging the SQL in Toad with Trial and error method, came to conclusion that the 2 conditions used for a column in opty DX was causing the Error.
ie( Column with " IS NOT NULL" AND "<>'N' " for an attribute.
5: when we removed any of the condition the SQL runs fine in Toad, then after further analysis , by adding the same attribute which has the same two conditions in the select list ,
the issue got resolved in Oracle Toad as well as in Siebel Analytics Answers.
Running a Request in Siebel Answers gives Oracle Error.
1: Select Few columns from opportunity, position dimension and Revenue Fact in siebel Answers, when we ran the Request it gives Odbc Erros saying ORA-03113: end-of-file on communication channel errors.
2: when we Take the Physical SQL from the log file and Ran the same query in toad, here too it gave the same Error.
3: when we checked with the DBA it was giving an Oracle Internal Error "Core dump"
4: After debugging the SQL in Toad with Trial and error method, came to conclusion that the 2 conditions used for a column in opty DX was causing the Error.
ie( Column with " IS NOT NULL" AND "<>'N' " for an attribute.
5: when we removed any of the condition the SQL runs fine in Toad, then after further analysis , by adding the same attribute which has the same two conditions in the select list ,
the issue got resolved in Oracle Toad as well as in Siebel Analytics Answers.
Monday, August 25, 2008
The Siebel Analytics attempts to execute query using the W_INS_CLAIM_F table by default.
How to remove the Default Join Path from LTS:
i): By Default when Employee name is selected the join path traverse to insurance fact ratter than expected Join Path.
ii): This Issue Arises when we have both the horizontal and vertical in the siebel analytics RPD.
iii): The requirement was to Get the name of the Sales Rep based on the Login from employee and their associated territory.
iv): This has been fixed by removing the reference in the Insurance Source of the FACTS (W_INS_CLAIM_F) table in the content tab of the LTS to the Horizontal dimensions so that it will choose the most economical sources as what is expected.
v): Employee and opportunity Relation is Many to many between these two. so the relation goes like the parent held position id in s_contact and row_id in the s_opty tables to the Intersection table of S_opty_postn through the Opty_id and Position_id).
i): By Default when Employee name is selected the join path traverse to insurance fact ratter than expected Join Path.
ii): This Issue Arises when we have both the horizontal and vertical in the siebel analytics RPD.
iii): The requirement was to Get the name of the Sales Rep based on the Login from employee and their associated territory.
iv): This has been fixed by removing the reference in the Insurance Source of the FACTS (W_INS_CLAIM_F) table in the content tab of the LTS to the Horizontal dimensions so that it will choose the most economical sources as what is expected.
v): Employee and opportunity Relation is Many to many between these two. so the relation goes like the parent held position id in s_contact and row_id in the s_opty tables to the Intersection table of S_opty_postn through the Opty_id and Position_id).
Subscribe to:
Posts (Atom)