BI Publisher 10g - Limit to the size of the data model?

Hello,
We are using OBIEE 10g 10.1.3.4.1 in our organization and have a problem when working on a large report in BI Publisher. It seems that once our data model gets large enough, we are no longer able to edit the report. When we click on the Edit link to load the report editor, the side menu that lists the data model, parameters, bursting, etc does not load, preventing us from making any changes to the report.
At first we thought it was a timeout issue and changed the following:
$J2EE_HOME/applications/xmlpserver/xmlpserver/js/XDOReportModel.js
Property name : XDOReportModel.TIMEOUTMSEC
set value in Milli seconds as " XDOReportModel.TIMEOUTMSEC = 15000
After making the change and restarting the services, it did not help. Is there a different place for the timeout of loading the report editor? What about some kind of cap to the size of the data model? We have one large data template that is used to generate a report. I tried breaking the large data set into multiple, smaller data sets (still using data tempalte) and that didn't seem to help any. Is there a limit the size of the data model BI Publisher can return?
Any help would be greatly appreciated! Thanks!

Hello,
I think you should create a recordStore with RMS and use it like a string array. You can store huge amount of data and the time access when request data from recordStore is very similar as if it is store on the RAM memory with recent devices.
And if it is not persistent data you can delete the recordStore when closing the midlet.

Similar Messages

"An error occured while working on the Data Model in the workbook" on some workbooks published to Power BI site

Hello,
I am using the Power BI for Office 365, and I have published several Excel 2013 workbooks having Power Pivot Data Models.
I have a problem on some of the workbooks, once a slicer is selected, I get the error: "An error occurred while working on the Data Model in the workbook" and the slicers do not affect the charts.
Some workbooks work perfectly fine. I am using the same user for all workbooks when creating and publishing. I tried with small workbooks less than < 10 MB size and larger workbooks > 10 MB. There is no rule, some workbooks larger than 10 MB work perfectly
with the slicers effecting the charts, and some don't. Similarly for smaller size.
Any ideas of how I can debug the cause of the issue?
Appreciate any feedback,
Thanks,
Grace

Hi Grace,
I assume that the experience in the Excel client is working fine, right?
Are you getting a correlation id with the error?
Please send us a bit more information / samples to reproduce over email to
this address.
thanks,
Guy
GALROY

How to fix the limit of the date entering in a parameters

How to fix the limit of the date entering in a parameters,
I.e i want to make parameters doesnot exceed 31.12.9999 in date and another parameter which is used to add no of days to this so it should not allow to add the no of days to given date as 31.12.9999

parameter : p_date like sy-datum
at selection-screen on date1.
if date1 GT 31.12.9999.
message(e01).
end if.
reward with points if helpful.

Including table and column comment in the Data Modeler

Hi all,
I used Oracle's SQL Developer Data Modeler (Version 3.0.0.665) and created a data model for my project. I e-mailed a PDF format of the data model to our Systems Analyst. She asked if I could re-create the data model and include table and column comments. Is this a possibility and if so how is this done?
Thank you for your input,
Seyed

Hi Kent,
Using the information you provided and Oracle’s Working with SQL Developer Modeler Reporting I did the following:
1) Created a Reporting Schema User
1.1) Using my Oracle 10g Personal Edition, I created a new user and gave him DBA administrative privileges
2) Exported Relational Design to Reporting Schema
2.1) Opened the Relational Design
2.2) Exported it to the Reporting Schema. Note, I never got a message ‘Design has been exported successfully’.
3) Reviewed the Report Results
I think exporting the relational design was not successful, and didn’t get any error messages. Had step 2 completed successfully, I would have reviewed the Report Results in SQL Developer. By the way, I know I have marked this topic as closed, but would like to learn your method too.
Thank you for your help,
Seyed

Printing the data model?

Hello,
Is it possible to print the data model from Reports Builder 10g?
Regards,
- Alan

Awesome.
this Document may be handy.
-D

Can "trigger" management be addressed in the data modeler?

Please add an easier way to add/modify triggers.
I reverse-engineered my model into the data modeler and my triggers all migrated correctly to the model but, for the life of me, had no idea how to view, modify or create triggers. After extensive research, I found that they can be accessed in the left-hand Browser by drilling some 8 levels to view the triggers for each table - why? Why can't this functionality be added to properties context menu for the table. I'm not a big advocate for triggers but if I need to work on one, the current methodology is tedious at best.
Of course, if there's some other way to do this, please inform...
Accessing Triggers via the Browser
Design -> Relational Model -> APEX_DEMO -> Physical Model -> Oracle Database 11g -> Tables -> ACTIVITY_LOG -> Triggers

Thanks Joop and Phillip...
While I occasionally use SQL Developer, I currently use PL/SQL Developer (Allround Automations) as my development tool of choice and bringing a 3rd tool as SQL Developer into the mix, makes no sense to me.
I completely agree that managing a trigger via a development tool is much easier but one occasionally wants to quickly add a trigger either manually or via a template and this is not easy currently.
While functions, procedures, package, etc. are all important to a data model, the existence of most triggers are completely dependent on a table and are a critical component in any model that uses them. The ability to access and modify them easily in Data Modeler is important and shouldn't be an afterthought as is perceived here. If trigger access cannot be added to the Table Properties (as noted in the image below), at the very least, please provide a shortcut methodology to do so.

PowerPivot removed table replicated into the data model on refresh

Hey
I am facing the following problem which is absolutely persistent and annoying in nature. I am using a data model created with PowerPivot with connections to three different SQL servers and 25 tables. The bug is that every time I refresh my data, a table
that was initially added to the data model (and later removed) is replicated in equivalent number of tables that use this connection, which is currently around 12 tables, so I get 12 duplicates of the same unnecessary table on every refresh, named with the
name of the schema on the SQL server that is followed by a running number. Removing these from the data model on every refresh simply takes too much time on a daily basis. The additional undesired table which is created is what is defined in the SQL query
of the connection string of this connection.
I tried to solve this problem by zipping the Excel file and modifying this SQL statement present in the connection string in the connections.xml file in a way that it would not return anything, but this always leads into a corrupted workbook.
After encountering this I have managed to avoid this problem by making sure that the initial table I'm adding to the data model will remain in the model, but I really don't want to rebuild this current model. Is there any fix for this issue without
rebuilding the data model?
Thanks for all the help in advance!

I am using 64-bit Office 2013 with the recent SP1 upgrade and the included PowerPivot plug-in on a Windows 8.1 machine.
I always create the connection by using "From SQL server" then fill in the server and log in details and use a ready SQL statement that I have written by using SQL Server Management Studio to import the initial table. For all the preceding tables
using the same server and schema, I always select it from existing connections and just paste the SQL queries required for any additional tables to the "Write a query that will specify the data to import", rather than using the table import tool.
I am not sure if it could have any effect that I've been using the type connection "From SQL server" although the database is really running on Azure (there is a possibility to select From Other sources > Microsoft SQL Azure, but the functionality
seems the same).
I don't really understand what I should edit from the existing connections section. Just to clarify, apparently the Connection String parameters can be edited from PowerPivot, but not the Command Text which can be viewed from Excel Data > Connections
> Properties, but is shown in gray with a message "Some properties cannot be changed because this connection was modified using the PowerPivot add-in."
In the data model I am using two sets of identical tables, but connected to two different servers that are running a database 1:1 in structure. Initially the problem considered only the other of these, but I accidentally reproduced it by, again, editing
the SQL query in the table that was initially imported when that connection was created (PowerPivot > Design > Table Properties). Now when refreshing I get tables that are structured as in what the "Connection Text" part of the connection would
produce, which replicated for the equivalent amount of additional tables using the same connection, so now I'm getting 12 tables (the number of tables using the same connection) each named "*schemaname1* Query", "*schemaname1* Query2",
"*schemaname1* Query3" "*schemaname2* Query" and so on.
Personally I can definitely see a pattern here. If there isn't a table matching what has been specified in the "Command Text" that was described when the connection was created, then it for some reason runs this query anyway on every table that
is using the connection.

Powerpivot Error on Refresh -- "We couldn't get data from the data model..."

I'm using Excel 2013 and Windows 8.1. I have a spreadsheet I've been using for over a year, and I've just started getting this error message when I try to refresh the data.
"We couldn't get data from the Data Model. Here's the error message we got:
The 'attributeRelationship' with 'AttributeID' - 'PuttDistCat9' doesn't exist in the collection"
Any idea how I can fix this problem? I haven't changed anything related to that particular attribute. All the data is contained in separate sheets in the workbook, so there are no external sources of data.
Thanks.
Jean

Thanks for all the suggestions.
I found a slightly older version of the spreadsheet that still refreshes properly, so I don't think I have any issues with the version of Excel or Power Query. (I've had this same error before, and I believe I applied the hotfix at that time.)
I think this problem started after I updated a number of the date filters in the pivot tables. I haven't made any changes to the data model, and the only updates I've made were to add data (which I do all the time), and to change the date filters on
the pivot tables.
As suggested, I added a new pivot table querying one table (the table with the attribute that shows up in the error message), and it worked fine. I can also refresh this pivot table.
Then I tried adding a pivot table which went against several tables in the data model (including the table in question). The pivot table seemed to return that data properly. However, when I tried to refresh it, I got the same error message ("we
couldn't get data from the data model...").
Dany also suggested running the queries one at a time to see which one is in error. Without checking all the pivot tables, it appears that any which use the table "HolePlayedStrokes" generate the error (this is the table with the attribute
mentioned in the error message). Pivot Tables without that particular table seem to refresh OK. Unfortunately, that is the main table in my data model, so most of the pivot tables use it.
Any other suggestions? I'd be happy to send a copy of the spreadsheet.
Thanks for all the help.
Jean

Excel 2013 PowerPivot Error - "PowerPivot is unable to load the Data Model"

I'm attempting to use the PowerPivot add-on in Excel. When clicking 'Manage Data Model' or attempting to 'Load to data model,' I receive the error 'We couldn't load the Data Model. This may be because the Data Model in this workbook is damaged.',
followed by 'PowerPivot is unable to load the Data Model.' This happens irrespective of data source type. I have Excel 2013 32-bit, PowerPivot 32-bit, running on Windows 7 OS 64-bit. I am not running an SSAS instance on my machine.
Any suggestions?

Hi
Have you ever tried to repair your office?
Also we may refer to the following blog :
http://blogs.technet.com/b/the_microsoft_excel_support_team_blog/archive/2013/11/12/powerpivot-for-excel-2013-errors-after-october-update-kb-2825655.aspx
This issue seems to be caused by the October 2013 update (KB 2825655) for Excel 2013. Try to remove it or restore the system to an earlier point and check the result.
Regards
Tylor Wang
TechNet Community Support

Questions on select statement in the data model

Hi,
In the select statement, the order by statement seems only to work at the lowest level of the select statement. Is this true?
What is the the purpose of the group by statement in the select statement?
As far as I understand, the grouping is catered for in the data model.....
Regards,
Kin

From the oracle report docs:
The order of column values in a default group is
determined by the ORDER BY clause of the query for
SQL queries and by the sort column for Express queries.
For column values in user-created groups, however, you
must use Break Order to specify how to order the break
column's values.So order by in your sql query is affected by groups in your data model.
The purpose of a group by statement in your select statement is to group values for aggregation purposes, like
select department_id,
       min(salary),
       max (salary)
from employees
group
    by department_id
order
    by department_id;Grouping in the data model of a report is a little different than a group by clause, but not entirely.

Use a multiple selection parameter in the data model

Hi
i have created a parameter with the property multiple selection.
This parameter i use in the Data Model where area,
if i just mark one value the report works well if i mark more the one
the report run into a error.
WHERE PSNR IN :ma
the xdo looks like
<?xml version = '1.0' encoding = 'utf-8'?>
<report version="1.1" xmlns="http://xmlns.oracle.com/oxp/xmlp" defaultDataSourceRef="tisoware">
<title>BDE Nettozeit</title>
<properties>
<property name="showControls" value="true"/>
<property name="online" value="true"/>
<property name="parameterColumns" value="2"/>
<property name="openLinkInNewWindow" value="true"/>
</properties>
<dataModel defaultDataSet="BDERUECK">
<dataSet id="BDERUECK">
<sql dataSourceRef="tisoware">
<![CDATA[SELECT (SUBSTR(DATUM,1,6)) AS DATUM, SUM(NTTOZEIT) AS ZEIT,
TRUNC(SUM(NTTOZEIT)/60) AS STUNDE
FROM BDERUECK
WHERE (DATUM >= :datev) AND (DATUM <= :dateb) AND (KZDELETE = 'N') AND FIRMA = '1' AND ((PSNR IN :ma))
GROUP BY (SUBSTR(DATUM,1,6))]]>
</sql>
<input id="datev" value="${datev}" dataType="xsd:string"/>
<input id="dateb" value="${dateb}" dataType="xsd:string"/>
<input id="ma" value="${ma}" dataType="xsd:string"/>
</dataSet>
</dataModel>
<valueSets>
<valueSet id="date">
<sql dataSourceRef="tisoware">
<![CDATA[SELECT DISTINCT DATUM
FROM BDERUECK]]>
</sql>
</valueSet>
<valueSet id="employee">
<sql dataSourceRef="tisoware">
<![CDATA[select      PERSTAMM.PSPERSNR as PSPERSNR,
      PERSTAMM.PSNR as PSNR
from      TISOWARE.PERSTAMM PERSTAMM
where    PERSTAMM.FIRMA = '1'
order by PERSTAMM.PSPERSNR]]>
</sql>
</valueSet>
</valueSets>
<parameters>
<parameter id="datev" defaultValue="20050103">
<select label="Datum von : " valueSet="date" multiple="false" all="false" refreshParameters="false"/>
</parameter>
<parameter id="dateb" defaultValue="20060930">
<select label="Datum bis : " valueSet="date" multiple="false" all="false"/>
</parameter>
<parameter id="ma" defaultValue="152">
<select label="Mitarbeiter : " valueSet="employee" multiple="true" all="false"/>
</parameter>
</parameters>
<templates default="BDE Nettozeit">
<template label="BDE Nettozeit" type="rtf" url="BDE Nettozeit.rtf"/>
</templates>
</report>

Alex,
the missing thing in your example is the fact, that if only one value is selected, the parameter has exact this value like BOSTON. If you choose more than one value, the parameter includes the *'*, so that it looks like *'BOSTON','NEW YORK'*. So you need to check in the package, if there's a *,* in the parameter or not. If yes there's more than one value, if not it's only one value or it's null.
So change your package to (you need to expand your variables)
create or replace package bip_departments_2_parameters
as
p_dep_2_param varchar2(1000);
p_loc_1_param varchar2(1000);
p_where_clause varchar2(1000);
function beforereporttrigger
return boolean;
end bip_departments_2_parameters;
create or replace package body bip_departments_2_parameters
as
function beforereporttrigger
return boolean
is
l_return boolean := true;
begin
p_where_clause := ' ';
if p_dep_2_param is not null then
if instr(p_dep_2_param,',')>0 then
p_where_clause := 'WHERE DNAME in ('||p_dep_2_param||')';
else
p_where_clause := 'WHERE DNAME = '''||p_dep_2_param||'''';
end if;
if p_loc_1_param is not null then
if instr(p_loc_1_param,',')>0 then
p_where_clause := p_where_clause || ' AND LOC IN ('||p_loc_1_param||')';
else
p_where_clause := p_where_clause || ' AND LOC = '''||p_loc_1_param||'''';
end if;
end if;
else
if p_loc_1_param is not null then
if instr(p_loc_1_param,',')>0 then
p_where_clause := p_where_clause || 'WHERE LOC in ('||p_loc_1_param||')';
else
p_where_clause := p_where_clause || 'WHERE LOC = '''||p_loc_1_param||'''';
end if;
end if;
end if;
return (l_return);
end beforereporttrigger;
end bip_departments_2_parameters;
I've written a similar example at http://www.oracle.com/global/de/community/bip/tipps/Dynamische_Queries/index.html ... but it's in german.
Regards
Rainer

SQL Developer - problems with the Data Modeller part

Hi SQL Developer users,
I can open the Data Modeler pane, but I can't insert any object into the logical model or into the relational model. Any ideas about what I'm doing wrong? Do I need specific privileges to the database, or do I need to install SQL Developer in a different way?
Thanks,
Csisz

Hi Csisz,
as Ivaylo wrote - it's Data Modeler Viewer into SQL Developer.
I can't insert any object into the logical model or into the relational modelYou can drag tables from SQL Developer browser and drop them on relational model diagram. If you keep Ctrl key pressed then all child tables also will be imported and shown on diagram.
Philip

Why do I get the symbol data link in the query_name of the data model

If I use an inline subquery within the SELECT of a data model query, the symbol data link appears in the query_name of the data model.
This causes the data link between two queries not to be used even if there is an existing link between the two. The trace file doesn't
have that join condition and so the child query in which the inline subquery was added fetches many redundant data.
Any idea what that symbol represents and how to get rid of it. It also appears during other times, not only when we use inline subquery
within a SELECT. Not sure if it can cause any harm to the report.
The problem is seen in Report Builder 6.0.8.19.0. Not sure if the problem is with other releases also.
Any suggestions are welcome.

I am living with the symbol in the query box as well, because my report only has a single query. My query also has several inline subqueries. I had never seen this before last week, spent a day re-reading the manuals and couldn't figure it out.
My post is not a solution, but a "me too" echo that could use an answer.
Troy Tremble
If I use an inline subquery within the SELECT of a data model query, the symbol data link appears in the query_name of the data model.
This causes the data link between two queries not to be used even if there is an existing link between the two. The trace file doesn't
have that join condition and so the child query in which the inline subquery was added fetches many redundant data.
Any idea what that symbol represents and how to get rid of it. It also appears during other times, not only when we use inline subquery
within a SELECT. Not sure if it can cause any harm to the report.
The problem is seen in Report Builder 6.0.8.19.0. Not sure if the problem is with other releases also.
Any suggestions are welcome.

Is it proper for an application module has 300 views in the data model?

Based on my understanding, all view object instances are initialized at the same time as the application module.
It follows that when an application module is associated with a user session, the queries of each view object in the data model are executed.
ie. if the data model has 325 view object instances, 325 queries will be executed.
This doesn't seem efficient:
1. As each user session only need to access a subset of the view objects (for examples 35 views), the rest of view objects need not be instantiated for that session.
2. Performance may be slow on executing all 325 queries at one time, even worse when some queries are complex queries.
Am I correct on this?
In this case, will it be better to instantiate the view objects using the view object definition at runtime instead of adding all of them to the application module at design time?

No, that's not the default behaviour.
Assuming you're talking JDev 11, the AM on it's General tab as a Tuning option where you can set the loading of the VOs to Lazy or Non-Lazy, Lazy is the default. In turn each VO on their General tab also has a Tuning option of similar nature.
Online documentation says:
Lazy LoadingSelect to choose lazy loading. In this case, the application module instance is created without any of its components. Your view object and nested application module instances will not load until the first time they are used. For example, when lazy loading is enabled, a view object is instantiated only when the application accesses it. This will make start-up time faster.
Non-lazy Loading
Select to choose non-lazy loading. Your view object and nested application module instances will load when the application starts up. For example, suppose the application module you are editing defines three view objects and two nested application modules (which appear in the Application Module Instance section of the Data Model page over the application module overview editor). When lazy loading is disabled, the application module instance is created together with all three view objects and both nested application modules.>
So in essence as you describe for each session, if we're using the Lazy setting, even though you have 325 VOs within an AM, if the user within the session only visits 35 queries, only 35 queries should fire.
Does this help?
CM.

Parameters in the Data Model not working

I have about a bunch of Data Models that all have about 20 datasets in them. I have coded them all to take a date parameter in the SQL. So each dataset has a parameter called
<parameter name="reportingdate" dataType="date" defaultValue="2010-10-01"/>
I now want to use the parameters that are available in the data model to finalize all of my data models. But no matter what type of variable I use I get the following error:
java.io.IOException: execute query failed[nQSError: 17001] Oracle Error code: 1722, message: ORA-01722: invalid number
at OCI call OCIStmtExecute: WITH
What type of gotchas are there with this parameter stuff. I have tried setting it as both date and string. I have tried the following formats (YYYY-MM-DD) and (MM-DD-YYYY) and I have tried 2010-07-01T00:00:00.000-04:00

Hi,
Use Java Date format i.e dd/MM/yyyy.
Thanks
Prasan

BI Publisher 10g - Limit to the size of the data model?

Similar Messages

Maybe you are looking for