Issues SES Table Source

Hi All,
I am using Table Source to add have following questions..
1.I have added new table source (which is a materialized view) and then added 2 new "Search Attributes" and mapped them to the "Table Column Mapping" against two columns. Now when I try to get the Custom Attribute size using "resElemArray.getCustomAttributes()", it is always null..
2. Also, when searching, I would like to add a condition to the seach query which would be one of the new "Search Attribute" using Filter. Do you have example for that.
3. We have one of the column Content Type and when user searches for something, we would like to display the content grouped by content type. So search results would be as follows
All "Content Type 1" "Content Type 2" "Content Type 3" etc..
By default we will display all, but user can click on Content Type 1" link and see only search results of that content type..
If you have any examples that would be great..
Thank you.
Vasu.

Question 1: The first thing to do here is to make sure the attribute is set. The easiest way to do this is in the standard query interface, but means of a customized hitlist. Go to Global Settings -> Out of box Query Application / Configure Search Result List. Select "Use Advanced Configuration". Move your custom attributes from "Not Included" to "Included". Edit the XSL to add your custom attribute into the hitlist. For example the code:
 <xsl:if test="myattribute[.!='']">
 
 <xsl:text>My Attribute: </xsl:text>
 
 
 <xsl:value-of select="myattribute" />
 
 
 </xsl:if>would display an attribute called MyAttribute (use of the class "author" here is just to avoid you having to create a new CSS stylesheet entry).
2. I don't have an example of this, hopefully someone else can help.
3. You need to use doOracleOrganizedSearch to do a "facet search" like this.

Similar Messages

Need help with date range searches for Table Sources in SES

Hi all,
I need help, please. I am trying to satisfy a Level 1 client requirement for the ability to search for records in crawled table sources by a date and/or date range. I have performed the following steps, and did not get accurate results from Advanced searching for date. Please help me understand what I am doing wrong, and/or if there is a way to define a date search attribute without creating a LOV for a date column. (My tables have 500,00 rows.)
I am using SES 10.1.8.3 on Windows 32.
My Oracle 10g Spatial Table is called REPORTS and this table has the following columns:
TRACKNUM Varchar2
TITLE Varchar2
SUMMARY CLOB
SYMBOLCODE Varchar2
Timestamp Date
OBSDATE Date
GEOM SDO_GEOMETRY
I set up the REPORTS table source in SES, using TRACKNUM as the Primary Key (unique and not null), and SUMMARY as the CONTENT Column. In the Table Column Mappings I defined TITLE as String and TITLE.
Under Global Settings > Search Attributes I defined a new Search Attribute (type Date) called DATE OCCURRED (DD-MON-YY).
Went back to REPORTS source previously defined and added a new Table Column Mapping - mapping OBSDATE to the newly defined DATE OCCURRED (DD-MON-YY) search attribute.
I then modified the Schedule for the REPORTS source Crawler Policy to “Process All Documents”.
Schedule crawls and indexes entire REPORTS table.
In SES Advanced Search page, I enter my search keyword, select Specific Source Group as REPORTS, select All Match, and used the pick list to select the DATE OCCURRED (DD-MON-YY) Attribute Name, operator of Greater than equal, and entered the Value 01-JAN-07. Then the second attribute name of DATE_OCCURRED (DD-MON-YY), less than equals, 10-JAN-07.
Search results gave me 38,000 documents, and the first 25 I looked at had dates NOT within the 01-JAN-07 / 10-JAN-07 range. (e.g. OBSDATE= 10-MAR-07, 22-SEP-07, 02-FEB-08, etc.)
And, none of the results I opened had ANY dates within the SUMMARY CLOB…in case that’s what was being found in the search.
Can someone help me figure out how to allow my client to search for specific dated records in a db table using a single column for the date? This is a major requirement and they are anxiously awaiting my solution.
Thanks very much, in advance….

raford,
Thanks very much for your reply. However, from what I've read in the SES Admin Document is that (I think) the date format DD/MM/YYYY pertains only to searches on "file system" sources (e.g. Word, Excel, Powerpoint, PDF, etc.). We have 3 file system sources among our 25 total sources. The remaining 22 sources are all TABLE or DATABASE sources. The DBA here has done a great job getting the data standardized using the typical/default Oracle DATE type format in our TABLE sources (DD-MON-YY). Our tables have anywhere from 1500 rows to 2 million rows.
I tested your theory that the dates we are entering are being changed to Strings behind the scenes and on the Advanced Page, searched for results using OBSDATE equals 01/02/2007 in an attempt to find data that I know for certain to be in the mapped OBSDATE table column as 01-FEB-07. My result set contained data that had an OBSDATE of 03-MAR-07 and none containing 01-FEB-07.
Here is the big issue...in order for my client to fulfill his primary mission, one of the top 5 requirements is that he/she be able to find specific table rows that are contain a specific date or range of dates.
thanks very much!

Alter table source in SES

Hi!
We have a lot of table sources in SES and need to change database host in source definition but unfortunatly source is read only and no supported way described in docs.
Updating EQ$_DATA_SOURCE_PARAM_VAL with new value seems to be proper way - in administration UI source shown with new value but crawler is unable to connect to DB and using old value with old setting.
What else should I fix?
Thanks!
Regards,
iRAV

Hi,
The designer generate alter statements for you.
e.g You have a table emp with empno number(8) in designer and in your application database. You cahnged empno to number(12) in designer. Generate ddl pointing to your application database. Designer generate an ALTER table script for you.

Neen help with date range searches for Table Sources

Hi all,
I need help, please. I am trying to satisfy a Level 1 client requirement for the ability to search for records in crawled table sources by a date and/or date range. I have performed the following steps, and did not get accurate results from Advanced searching for date. Please help me understand what I am doing wrong, and/or if there is a way to define a date search attribute without creating a LOV for a date column. (My tables have 500,00 rows.)
I am using SES 10.1.8.3 on Windows 32.
My Oracle 10g Spatial Table is called REPORTS and this table has the following columns:
TRACKNUM Varchar2
TITLE Varchar2
SUMMARY CLOB
SYMBOLCODE Varchar2
Timestamp Date
OBSDATE Date
GEOM SDO_GEOMETRY
I set up the REPORTS table source in SES, using TRACKNUM as the Primary Key (unique and not null), and SUMMARY as the CONTENT Column. In the Table Column Mappings I defined TITLE as String and TITLE.
Under Global Settings > Search Attributes I defined a new Search Attribute (type Date) called DATE OCCURRED (DD-MON-YY).
Went back to REPORTS source previously defined and added a new Table Column Mapping - mapping OBSDATE to the newly defined DATE OCCURRED (DD-MON-YY) search attribute.
I then modified the Schedule for the REPORTS source Crawler Policy to “Process All Documents”.
Schedule crawls and indexes entire REPORTS table.
In SES Advanced Search page, I enter my search keyword, select Specific Source Group as REPORTS, select All Match, and used the pick list to select the DATE OCCURRED (DD-MON-YY) Attribute Name, operator of Greater than equal, and entered the Value 01-JAN-07. Then the second attribute name of DATE_OCCURRED (DD-MON-YY), less than equals, 10-JAN-07.
Search results gave me 38,000 documents, and the first 25 I looked at had dates NOT within the 01-JAN-07 / 10-JAN-07 range. (e.g. OBSDATE= 24-MAR-07, 22-SEP-), 02-FEB-08, etc.)
And, none of the results I opened had ANY dates within the SUMMARY CLOB…in case that’s what was being found in the search.
Can someone help me figure out how to allow my client to search for specific dated records in a db table using a single column for the date? This is a major requirement and they are anxiously awaiting my solution.
Thanks, in advance….

raford,
Thanks very much for your reply. However, from what I've read in the SES Admin Document is that (I think) the date format DD/MM/YYYY pertains only to searches on "file system" sources (e.g. Word, Excel, Powerpoint, PDF, etc.). We have 3 file system sources among our 25 total sources. The remaining 22 sources are all TABLE or DATABASE sources. The DBA here has done a great job getting the data standardized using the typical/default Oracle DATE type format in our TABLE sources (DD-MON-YY). Our tables have anywhere from 1500 rows to 2 million rows.
I tested your theory that the dates we are entering are being changed to Strings behind the scenes and on the Advanced Page, searched for results using OBSDATE equals 01/02/2007 in an attempt to find data that I know for certain to be in the mapped OBSDATE table column as 01-FEB-07. My result set contained data that had an OBSDATE of 03-MAR-07 and none containing 01-FEB-07.
Here is the big issue...in order for my client to fulfill his primary mission, one of the top 5 requirements is that he/she be able to find specific table rows that are contain a specific date or range of dates.
thanks very much!

Logical level for logical fact table sources

it is clear that for fact aggregates, we should use the Content tab of the Logical Table Source dialog to assign the correct logical level to each dimension.
question is : is it mandatory to assign even for non-aggregates fact tables the logical level for each dimension (which normally should be set to the most detailed level of each dimension) ? is it any known issue if "logical levels"in content tab are not set ?
the reason I'm asking this is a strange bug I have (I'm not going to discuss it here) and then only workaround seems to be NOT setting the logical levels (on content tab) for logical fact table sources.
thank you !

If levels are not set: By default levels are considered as lowest level
It should not matter if you set or not
Generally we set for facts explicitly when we are using Aggregate tables.
Your current issue might be a case by case; I would suggest to check implicit fact, any table mapped to the source to force a join etc
Mark if helps
Let me know how it helps
Edited by: Srini VEERAVALLI on Feb 5, 2013 8:33 AM
Any updates on this?+_
Edited by: Srini VEERAVALLI on Feb 14, 2013 9:09 AM

How to get all the column values from a table source

Hi,
I have created one table source on a employee table and some customized attributes using global settings>search attributes.
Now these customized attributes mapped with the table columns through attribute mapping from the sorce tab.
Using doOracleSearch method i passed last parameter i.e. Integer array of customized attributes.
After execution of doOracleSearch method i am getting the results but customized attributes are not coming.
getCustomAttributes method returns null instead of some values.
Please refer following code for more info:
Integer[] fetchAttr=new Integer[2];
fetchAttr[0]=new Integer(137);
fetchAttr[1]=new Integer(138);
result =
stub.doOracleSearch("BTM",
new Integer(1),
new Integer(10),
Boolean.TRUE,
Boolean.TRUE,
group,
"en",
"en",
Boolean.TRUE,
null,
null,
fetchAttr);
ResultElement[] resElements = result.getResultElements();
for(int i = 0; i < resElements.length; i++)
System.out.println("Title : " + resElements[0].getTitle());
System.out.println("Snippet : " + resElements[0].getSnippet());
System.out.println("URL : " + resElements[0].getUrl());
System.out.println("non default : " + resElements[0].getCustomAttributes()); // it returns null here
}

Confirm the attributes you are asking SES for match those on the data source being searched. One thing to try is to simply tell SES to return all custom attributes for your search. Here is a snippet to build a list of all attribute IDs and pass them to your search...
// Create and set SOAP URL
OracleSearchService searchService = new OracleSearchService();
searchService.setSoapURL("http://myserver:7777/search/query/OracleSearch");
// Set attributes to fetch (all)
Attribute[] attributesAll = searchService.getAllAttributes("en");
ArrayList<Integer> attributeIds = new ArrayList<Integer>();
for(Attribute a: attributesAll)
attributeIds.add(a.getId());
Integer attributeIdArrayAll[] = new Integer[attributeIds.size()];
attributeIdArrayAll = attributeIds.toArray(attributeIdArrayAll);
// Query
OracleSearchResult result = searchService.doOracleSearch("some text", ..........[other params], attributeIdArrayAll);
// Print out results
ResultElement[] resElements = result.getResultElements();
for(int i = 0; i < resElements.length; i++)
// Get document
ResultElement doc = resElements;
// Print Title
System.out.println("Title: " + doc.getTitle());
// Print custom attributes
CustomAttribute[] attributes = doc.getCustomAttributes();
for(int j = 0; j < attributes.length; j++)
CustomAttribute attr = attributes[j];
System.out.println("[Custom Attribute] " + attr.getName() + ": " + attr.getValue());
Hope this helps.

No Fact table Exists and [nQSError: 14070] Cannot find logical table source

Hi,
I have 3 tables A(fact),B(dim) and C(dim). there are some other dims. i am getting Errors here.
A is joined with B and B is joined with C .
1) In report if i pull columns from A and B its giving data. If i include C table Columns in the report i am getting Error like
No Fact table Exists.
2) If i pull the C table columns only in the Criteria i am getting error [nQSError: 14070] Cannot find logical table source
How can i resolve this.
Thanks

In Logical table B source properties general tab ->Click on Add button and add table C and pull required columns from Physical layer table C.
If helps mark for any issues let me know.
Edited by: Srini VEERAVALLI on Feb 13, 2013 6:42 AM

Invalid data from serveral fact logical table sources after upgrade to 11g

Hi,
We have a situation after upgrade from 10g to 11g. Answers' querys works fine in 10g environment, but in 11g, generated SQL is not correct.
Our example is something like that: we have orders fact table, customers and time dimensions. Customer have an hierarchy like: Customer Total -> Customer Country -> Customer Region -> Customer Detail (each level in one different physical table).
Order's logical table source has two table sources. One sets to Customer Country level, second one Customer Region level, both with different WHERE clauses in Content tab inside LTS configuration. Both at same level of Time dimension.
The issue is that, at dimension level, SQL is getting correct table to resolve Customer data (Customer Region level), but then, is getting the WHERE clause sets in LTS set to Customer Country level, so we are getting error data. Priority is the same to both LTS at fact table, sets to 0 (default).
How to know the way Oracle BI Server takes one LTS instead of another one? It's supposed to take the LTS defined at the same granularity level... but is not correct this case.
Thanks.

Can you try one of these options:
Try to set the priority group of lowest granular dimension to 1
or disable the LTS that is getting the where clause and check if it works fine and then enable again.

Table Source encoding

Hello all,
I was able to configure table source and access a table inside CQL Processor.
The problem is that some of the fields in my table contains data in language that not English.
When I trying to select this field - I get '?' (question mark) instead.
PL/SQL Developer returns the data from this field correctly.
Using JDBC also returns correct data.
Database encoding is AMERICAN_AMERICA.IW8ISO8859P8.
Any help in fixing the issue will be appreciated .
Regards,
Dmitry
Edited by: dmitryz1 on Dec 12, 2012 4:37 AM

The dev are quite busy these days, I am not sure if they have time to take a look at this. Could you elaborate what you have done? So that we can help you.
Regards
Junger

NQSError 15018 Incorrectly defined logical table source error

Hi,
I am getting the following error when I am building one of my reports.
I have 3 dimensions - Time, customer and Product and two facts F1 and F2. Both F1 and F2 are joined to all three dimensions
The part I dont understand is that when I built a report with columns from all 3 dimensions and 2 facts it worked fine. But as soon as I added a new column from the customer dimension I am getting the below error. When I remove this specific column the report works fine.
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 15018] Incorrectly defined logical table source (for fact table F1) does not contain mapping for [Time.Mth_name, Time.Year]. (HY000)
Please help me figure out the issue.

Hello All,
I am also getting the same error.
I have one dim table d1 and 2 fact tables f1 and f2.
f1 contains 5 columns and f2 contains 2 columns. I created a logical table source between f1 and f2. Column mapping is done between f1.agency_no and f2.agency_no.
Columns in f1 : agency_no, agency_name,source, proj#, proj_phase
Columns in f2: agency_no, manager
Columns in d1: agency_no, agency_shortname, agency_name
Now, when i select f1.agency_no and f2.agency_no in the report. It is working fine, because the column mapping is defined between these 2 columns.
When i drag f2.manager into the report (report contains f1.agency_no, f2.agency_no, f2.manager) i am getting the following error.
[nQSError: 15018] Incorrectly defined logical table source (for fact table f2) does not contain mapping for [f1.agency_no]. (HY000)
Please help me out with this issue.
Thanks in advance.

NQSError: 10058 Incorrectly defined logical table source

Hi All,
i am trying to join two facts using a dimension. If i run report having one column from dimension & one from fact it works. But when i run a report having 1 column from first fact & 2nd column from second fact i get the below error.
I am sure this has something to do with the content tab under sources in BMM later.
But can anyone me what exactly i need to do.
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 15018] Incorrectly defined logical table source (for fact table DWH_PA_MBR_PA_TMP_NEW) does not contain mapping for [DWH_PA_MBR_PA_TMPT_NEW.PERIOD_CODE]. (HY000)
SQL Issued: SELECT DWH_PA_MBR_PA_TMPT_NEW.PERIOD_CODE saw_0, DWH_PA_MBR_PA_TMP_NEW.CURRENCY_ID saw_1 FROM DWH ORDER BY saw_0, saw_1
Thanks,
Pankaj

yes i have the following
Facts
1) DWH_PA_MBR_PA_TMP_NEW
2) DWH_PA_MBR_PA_TMPT_NEW
Dim
1) PA_PERIODS_ALL
Join 1) PA_PERIODS_ALL.PERIOD_NAME = DWH_PA_MBR_PA_TMPT_NEW.PERIOD_NAME
Join 2) PA_PERIODS_ALL.PERIOD_NAME = DWH_PA_MBR_PA_TMP_NEW.PERIOD_NAME
When i run report with columns from Fact 1 & Fact 2 i get the error.
else if i run report with column from Fact 1 & Dim it works fine.
Note: here Period Name is the key.
I guess we need to define the LTS, colmn mappings.
Thanks,
Pankaj

Incorrectly defined logical table source error

Hey ,I am very new to obiee and getting an error
A general error has occurred. [nQSError: 15018] Incorrectly defined logical table source (for fact table Fact - D) does not contain mapping for [case when Dim - Account. Account Number in ([ 11500, 11501, 11502, 11503, 11504] ) then 'ABC'
Can you tell me how to resolve this issue and what things should I look for

In that case you are not the one to handle the issue.
No point to respond to this post
Check this
ANNOUNCEMENT:Forums Etiquette/Reward Points
~ http://cool-bi.com

Repos - logical table source does not contain mapping

Hi,
I have a repository question?
I do not have a fact table in my physical layer. Do I have to have one? I thought the fact table got created in the BM.
I do have a date table in the physical layer, but it isn't joined to any other table.
I added the PK from the date_dimention to my logical fact table.
when I open the properities of my logical date table it is mapped to the physical date table.
Now in answers, I can query the date_dimension without error.
But, when I query the fact table using the date key, I get this error.
Error Details
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 15018] Incorrectly defined logical table source (for fact table CRTK_FACTS) does not contain mapping for [CRTK_FACTS.MASTER_AI_ID, CRTK_FACTS.INT_DOC_ID, CRTK_FACTS.DATE_KEY]. (HY000)
SQL Issued: SELECT CRTK_FACTS.MASTER_AI_ID saw_0, CRTK_FACTS.INT_DOC_ID saw_1, CRTK_FACTS.DATE_KEY saw_2 FROM CRTK ORDER BY saw_0, saw_1, saw_2
Anyone have any suggestions on what I am missing?
thanks,
Kathy

I don't have a fact table in the physical layer. Do you mean join between the date table and other dimension tables?
or do I have to build the fact table in the physical layer?
I have not built any hierarchies yet, working on it.

RE:[nQSError: 15018] Incorrectly defined logical table sourc

Hi Experts,
Actually we have a report by using X subject area and there are two users(Y,Z) accessing the report but for one user(Y) the report is looking fine for other user(Z) it is showing the below error
but for both users having same permission on the X subject area.
*[nQSError: 15018] Incorrectly defined logical table source (for fact table ABC) does not contain mapping for .ROW_ID)*
here in the report does not contain any column from the ABC fact table .
weather this is an security issues or any technical issue because one user is getting the report and other user is not getting the report.
Can any one guide me regarding the above issue...
Regards,

Since you have formatted the error message its not clear ROW_ID is from which table.
Here I'll give few hints to cross check.
1 There should be no key on fact tables in the Business Model.
2 Use Complex joins, not Foreign Key joins, in the Business Model.
3 All dimensions should have hierarchies defined
4 Content tab settings
Edited by: Srini VEERAVALLI on Mar 26, 2013 10:03 AM
It would be nice if you update your old post before you post new one, that helps you to get responses
Edited by: Srini VEERAVALLI on Apr 18, 2013 6:32 AM
Whats the solution or fix?
Edited by: Srini VEERAVALLI on Apr 18, 2013 6:55 AM

Logical Table source source query

In OBIEE 10g we can have multiple logical table sources and we can also add multiple tables into a single logical table source(logical table source source). I wanted to know the difference between doing so and having multiple logical table sources for each logical source.
Hope I made myself clear.
Cheers
Rem

Hi Rem,
When data is duplicated across different physical tables add them as separate LTS with column mapping pointing to most economical sources. Specifying the most economical source is about the idea that a single column exists in more than one table, based on the column mappings BI server picks up those LTS's which could satisfy the request with minimal joins.
When the data is not duplicated add them in a single LTS source. When the physical sources are added in a single LTS, you have the flexibility of using outer joins. But specifying a join as outer join makes BI Server to include this source even if its not required otherwise when the join is inner, the sources will not be included if not required to satisfy the query.
Hope this helps.
Thanks!

Issues SES Table Source

Similar Messages

Maybe you are looking for