Rollup for cube

Hi experts,
I have a cube. And the rollup for this cube seems to take a very long time to run. There is a SIGMA under the Rollup Status column for the requests of 11/19, 11/20, 11/21. As today is 11/22, the rollup for the first request has been running for over 3 days.
Would you please let me know how I can check the status of the rollup progress or how I can stop it and restart it?
Thanks.
Regards,
Shawn

Hi,
U can monitor the roll process in aggregates overview screen..
Goto RSA1> Monitoring Tab> Select Aggr's ... here u can monitor the roll up process
Goto SM37 and Selct that job and Cancel
goto SE38 and run the prog.. SAP_AGGREGATES_ACTIVATE_FILL
Thanks

Similar Messages

Cannot rollup for cube

Hi experts,
I have a rollup action in my process chain. It shows green light after execution, however, rollup is not performed.
I got the message "Aggregation of infocube XXXXX terminated, as end request id 0000000000 not permitted".
When I manage the cube, the technical status is also in green light, however, no click in "compression status of aggregate" and rollup status", and "request for reporting available" is nothing.. I tried to click the tab "Rollup", it said that "no valid request available for rollup".
Does anyone know what's going on... and how to solve it? Thanks in advance.
Points will be awarded for useful answers.

Hi,
Check whether the aggregates and activated and showing green. If not reactive and fill them.
If they are green. Go in the manage tab and take the latest request ID from the llist and put it in the roll up tab and then try to rollup
Regds,
Shashank

ROLLUP AND CUBE OPERATORS IN ORACLE 8I

제품 : PL/SQL
작성날짜 : 2000-06-29
========================================
ROLLUP AND CUBE OPERATORS IN ORACLE 8I
========================================
PURPOSE
ROLLUP 과 CUBE Operator에 대해 설명하고자 한다.
Explanation
ROLLUP operator는 SELECT문의 GROUP BY절에 사용된다.
SELECT절에 ROLLUP 을 사용함으로써 'regular rows'(보통의 select된 data)와
'super-aggregate rows'(총계)을 구할 수 있다. 기존에는 select ... union select
를 이용해 구사해야 했었던 것이다. 'super-aggregate rows'는 'sub-total'
(중간 Total, 즉 소계)을 포함한다.
CUBE operator는 Cross-tab에 대한 Summary를 추출하는데 사용된다. 모든 가능한
dimension에 대한 total을 나타낸다. 즉 ROLLUP에 의해 나타내어지는 item total값과
column total값을 나타낸다.
NULL값은 모든 값에 대한 super-aggregate 을 나타낸다. GROUPING() function은
모든 값에 대한 set을 나타내는 null값과 column의 null값과 구별하는데 쓰여진다.
GROUPING() function은 GROUP BY절에서 반드시 표현되어야 한다. GROUPING()은 모든
값의 set을 표현합에 있어서 null이면 1을 아니면 0을 return한다.
ROLLUP과 CUBE는 CREATE MATERIALIZED VIEW에서 사용되어 질수 있다.
Example
아래와 같이 테스트에 쓰여질 table과 data을 만든다.
create table test_roll
(YEAR NUMBER(4),
REGION CHAR(7),
DEPT CHAR(2),
PROFIT NUMBER );
insert into test_roll values (1995 ,'West' , 'A1' , 100);
insert into test_roll values (1995 ,'West' , 'A2' , 100);
insert into test_roll values (1996 ,'West' , 'A1' , 100);
insert into test_roll values (1996 ,'West' , 'A2' , 100);
insert into test_roll values (1995 ,'Central' ,'A1' , 100);
insert into test_roll values (1995 ,'East' , 'A1' , 100);
insert into test_roll values (1995 ,'East' , 'A2' , 100);
SQL> select * from test_roll;
YEAR REGION DE PROFIT
1995 West A1 100
1995 West A2 100
1996 West A1 100
1996 West A2 100
1995 Central A1 100
1995 East A1 100
1995 East A2 100
7 rows selected.
예제 1: ROLLUP
SQL> select year, region, sum(profit), count(*)
from test_roll
group by rollup(year, region);
YEAR REGION SUM(PROFIT) COUNT(*)
1995 Central 100 1
1995 East 200 2
1995 West 200 2
1995 500 5
1996 West 200 2
1996 200 2
700 7
7 rows selected.
위의 내용을 tabular로 나타내어 보면 쉽게 알 수 있다.
Year Central(A1+A2) East(A1+A2) West(A1+A2)
1995 (100+NULL) (100+100) (100+100) 500
1996 (NULL+NULL) (NULL+NULL) (100+100) 200
700
예제 2: ROLLUP and GROUPING()
SQL> select year, region, sum(profit),
grouping(year) "Y", grouping(region) "R"
from test_roll
group by rollup (year, region);
YEAR REGION SUM(PROFIT) Y R
1995 Central 100 0 0
1995 East 200 0 0
1995 West 200 0 0
1995 500 0 1
1996 West 200 0 0
1996 200 0 1
700 1 1
7 rows selected.
참고) null값이 모든 값의 set에 대한 표현으로 나타내어지면 GROUPING function은
super-aggregate row에 대해 1을 return한다.
예제 3: CUBE
SQL> select year, region, sum(profit), count(*)
from test_roll
group by cube(year, region);
YEAR REGION SUM(PROFIT) COUNT(*)
1995 Central 100 1
1995 East 200 2
1995 West 200 2
1995 500 5
1996 West 200 2
1996 200 2
Central 100 1
East 200 2
West 400 4
700 7
위의 내용을 tabular로 나타내어 보면 쉽게 알 수 있다.
Year Central(A1+A2) East(A1+A2) West(A1+A2)
1995 (100+NULL) (100+100) (100+100) 500
1996 (NULL+NULL) (NULL+NULL) (100+100) 200
100 200 400 700
예제 4: CUBE and GROUPING()
SQL> select year, region, sum(profit),
grouping(year) "Y", grouping(region) "R"
from test_roll
group by cube (year, region);
YEAR REGION SUM(PROFIT) Y R
1995 Central 100 0 0
1995 East 200 0 0
1995 West 200 0 0
1995 500 0 1
1996 West 200 0 0
1996 200 0 1
Central 100 1 0
East 200 1 0
West 400 1 0
700 1 1
10 rows selected.
===============================================
HOW TO USE ROLLUP AND CUBE OPERATORS IN PL/SQL
===============================================
Release 8.1.5 PL/SQL에서는 CUBE, ROLLUP 이 지원되지 않는다. 8i에서는 DBMS_SQL
package을 이용하여 dynamic SQL로 구현하는 방법이 workaround로 제시된다.
Ordacle8i에서는 PL/SQL block에 SQL절을 직접적으로 위치시키는 Native Dynamic SQL
(참고 bul#11721)을 지원한다.
Native Dynamic SQL을 사용하기 위해서는 COMPATIBLE 이 8.1.0 또는 그 보다 높아야
한다.
SVRMGR> show parameter compatible
NAME TYPE VALUE
compatible string 8.1.0
예제 1-1: ROLLUP -> 위의 예제 1과 비교한다.
SQL> create or replace procedure test_rollup as
my_year test_roll.year%type;
my_region test_roll.region%type;
my_sum int;
my_count int;
begin
select year, region, sum(profit), count(*)
into my_year, my_region, my_sum, my_count
from test_roll
group by rollup(year, region);
end;
Warning: Procedure created with compilation errors.
SQL> show errors
Errors for PROCEDURE TEST_ROLLUP:
LINE/COL ERROR
10/8 PL/SQL: SQL Statement ignored
13/18 PLS-00201: identifier 'ROLLUP' must be declared
SQL> create or replace procedure test_rollup as
type curTyp is ref cursor;
sql_stmt varchar2(200);
tab_cv curTyp;
my_year test_roll.year%type;
my_region test_roll.region%type;
my_sum int;
my_count int;
begin
sql_stmt := 'select year, region, sum(profit), count(*) ' ||
'from test_roll ' ||
'group by rollup(year, region)';
open tab_cv for sql_stmt;
loop
fetch tab_cv into my_year, my_region, my_sum, my_count;
exit when tab_cv%NOTFOUND;
dbms_output.put_line (my_year || ' '||
nvl(my_region,' ') ||
' ' || my_sum || ' ' || my_count);
end loop;
close tab_cv;
end;
SQL> set serveroutput on
SQL> exec test_rollup
1995 Central 100 1
1995 East 200 2
1995 West 200 2
1995 500 5
1996 West 200 2
1996 200 2
700 7
PL/SQL procedure successfully completed.
예제 2-1: ROLLUP and GROUPING() -> 위의 예제 2와 비교한다.
SQL> create or replace procedure test_rollupg as
my_year test_roll.year%type;
my_region test_roll.region%type;
my_sum int;
my_count int;
my_g_region int;
my_g_year int;
begin
select year, region, sum(profit),
grouping(year), grouping(region)
into my_year, my_region, my_sum, my_count,
my_g_year, my_g_region
from test_roll
group by rollup(year, region);
end;
Warning: Procedure created with compilation errors.
SQL> show error
Errors for PROCEDURE TEST_ROLLUPG:
LINE/COL ERROR
12/4 PL/SQL: SQL Statement ignored
17/13 PLS-00201: identifier 'ROLLUP' must be declared
SQL> create or replace procedure test_rollupg as
type curTyp is ref cursor;
sql_stmt varchar2(200);
tab_cv curTyp;
my_year test_roll.year%type;
my_region test_roll.region%type;
my_sum int;
my_count int;
my_g_region int;
my_g_year int;
begin
sql_stmt := 'select year, region, sum(profit), count(*), ' ||
'grouping(year), grouping(region) ' ||
'from test_roll ' ||
'group by rollup(year, region)';
open tab_cv for sql_stmt;
loop
fetch tab_cv into my_year, my_region, my_sum, my_count,
my_g_year, my_g_region;
exit when tab_cv%NOTFOUND;
dbms_output.put_line (my_year || ' '||my_region ||
' ' || my_sum || ' ' || my_count ||
' ' || my_g_year || ' ' || my_g_region);
end loop;
close tab_cv;
end;
Procedure created.
SQL> set serveroutput on
SQL> exec test_rollupg
1995 Central 100 1 0 0
1995 East 200 2 0 0
1995 West 200 2 0 0
1995 500 5 0 1
1996 West 200 2 0 0
1996 200 2 0 1
700 7 1 1
PL/SQL procedure successfully completed.
예제 3-1: CUBE -> 위의 예제 3과 비교한다.
SQL> create or replace procedure test_cube as
my_year test_roll.year%type;
my_region test_roll.region%type;
my_sum int;
my_count int;
begin
select year, region, sum(profit), count(*)
into my_year, my_region, my_sum, my_count
from test_roll
group by cube(year, region);
end;
Warning: Procedure created with compilation errors.
SQL> show error
Errors for PROCEDURE TEST_CUBE:
LINE/COL ERROR
10/4 PL/SQL: SQL Statement ignored
13/13 PLS-00201: identifier 'CUBE' must be declared
SQL> create or replace procedure test_cube as
type curTyp is ref cursor;
sql_stmt varchar2(200);
tab_cv curTyp;
my_year test_roll.year%type;
my_region test_roll.region%type;
my_sum int;
my_count int;
begin
sql_stmt := 'select year, region, sum(profit), count(*) ' ||
'from test_roll ' ||
'group by cube(year, region)';
open tab_cv for sql_stmt;
loop
fetch tab_cv into my_year, my_region, my_sum, my_count;
exit when tab_cv%NOTFOUND;
dbms_output.put_line (my_year || ' '||
nvl(my_region,' ') ||
' ' || my_sum || ' ' || my_count);
end loop;
close tab_cv;
end;
Procedure created.
SQL> set serveroutput on
SQL> exec test_cube
1995 Central 100 1
1995 East 200 2
1995 West 200 2
1995 500 5
1996 West 200 2
1996 200 2
Central 100 1
East 200 2
West 400 4
700 7
PL/SQL procedure successfully completed.
예제 4-1: CUBE and GROUPING() -> 위의 예제 4와 비교한다.
SQL> create or replace procedure test_cubeg as
my_year test_roll.year%type;
my_region test_roll.region%type;
my_sum int;
my_count int;
my_g_region int;
my_g_year int;
begin
select year, region, sum(profit),
grouping(year), grouping(region)
into my_year, my_region, my_sum, my_count,
my_g_year, my_g_region
from test_roll
group by cube(year, region);
end;
Warning: Procedure created with compilation errors.
SQL> show error
Errors for PROCEDURE TEST_CUBEG:
LINE/COL ERROR
12/4 PL/SQL: SQL Statement ignored
17/13 PLS-00201: identifier 'CUBE' must be declared
SQL> create or replace procedure test_cubeg as
type curTyp is ref cursor;
sql_stmt varchar2(200);
tab_cv curTyp;
my_year test_roll.year%type;
my_region test_roll.region%type;
my_sum int;
my_count int;
my_g_region int;
my_g_year int;
begin
sql_stmt := 'select year, region, sum(profit), count(*), ' ||
'grouping(year), grouping(region) ' ||
'from test_roll ' ||
'group by cube(year, region)';
open tab_cv for sql_stmt;
loop
fetch tab_cv into my_year, my_region, my_sum, my_count,
my_g_year, my_g_region;
exit when tab_cv%NOTFOUND;
dbms_output.put_line (my_year || ' '||my_region ||
' ' || my_sum || ' ' || my_count ||
' ' || my_g_year || ' ' || my_g_region);
end loop;
close tab_cv;
end;
Procedure created.
SQL> set serveroutput on
SQL> exec test_cubeg
1995 Central 100 1 0 0
1995 East 200 2 0 0
1995 West 200 2 0 0
1995 500 5 0 1
1996 West 200 2 0 0
1996 200 2 0 1
Central 100 1 1 0
East 200 2 1 0
West 400 4 1 0
700 7 1 1
PL/SQL procedure successfully completed.
Reference Ducumment
Note:67988.1

Hello,
As previously posted you should use export and import utilities.
To execute exp or imp statements you have just to open a command line interface, for instance,
a DOS box on Windows.
So you don't have to use SQL*Plus or TOAD.
About export/import you may care on the mode, to export a single or a list of Tables the Table mode
is enough.
Please, find here an example to begin:
http://wiki.oracle.com/page/Oracle+export+and+import+
Hope this help.
Best regards,
Jean-Valentin

BI beans does not use QUERY RERWITE for cube

Hello!
First of all I would like to say big thanks to Keith for help on dimension rollup. It works now.
I am creating a pilot environment with
Oracle 10.2.0.3
OWB 10.2.0.3
SS Add-in 10.1.2.2
and one cube ST_R and three dims
DIM_R_NOMA for products
DIM_R_CIDI for stores
DIM_R_TIME for time
Now I have deployed dimensions and cube to CWM2. Dimensions are working quite well. I would say even better than in MOLAP. About 1 second for rollup on 2000 members in level.
Now I am facing second problem. I can not force BI beans (which is used in SS Add-in and Disco and OWB browser) to use summaries prepared by DBMS_ODM package.
1/ I have prepared MV LOGS for dimension and fact tables
2/ I have prepared MV for dimensions using DBMS_ODM
3/ I've prepared materialized view for cube aggs. with
DBMS_ODM.CREATESTDFACTMV('WWHH','ST_R','ST_R.sql','C:\TEMP',true,'FULL');
CWM2_OLAP_CUBE.set_mv_summary_code('WWHH','ST_R','GROUPINGSET');
as described in OLAP REFERENCE on DBMS_ODM page.
I explained all my MVs - they seem to be OK. They support
REWRITE_GENERAL,
REWRITE_FULL_TEXT,
REWRITE_PART_TEXT
There are no support for PCT rewrite etc.
My user 'WWHH' has a privileges:
ANALYSE_ANY
QWERY_REWRITE
GLOBAL_QWERY_REWRITE
My database has setting
QUERY_REWRITE_ENABLED=true
Stale_tolerated=enforced
all MVs and tables are analyzed.
I do not use parallel settings on tables,MVs.
to do some further analisys I've enabled olapcontinuous_trace_file. It generates some useful SQL statements from BI BEANS in UDUMP. These statements DO NOT resolve in MAT VIEW in explain plan
Questions:
Are there any settings for BI BEANS to turn on/off?
Are there any other packages to create MVs?
How to explain WHY MVs are not used?
THanks everybody for cooperation.
Regards,
Kirill Boyko

Keith,
Thank you for response.
I refreshed metadata, but no result. Again, dimensions are OK, but not cube. I am attaching explanation why it did no rewrite. This explanation is coming from
dbms_mview.Explain_Rewrite
QSM-01150: query did not rewrite
QSM-01263: query rewrite not possible when query references a dictionary table or view
QSM-01284: materialized view MV1125 has an anchor table DIM_R_TIME_V not found in query
QSM-01102: materialized view, MV1125, requires join back to table, DIM_R_CIDI_V, on column, REGION_ID
QSM-01219: no suitable materialized view found to rewrite this query
QSM-01284: - is wrong. I have DIM_R_TIME_V in MView.
Here is my MVIEW script from database:
SELECT
FROM
WWHH.CAWHTB2 a,
WWHH.DIM_R_CIDI_V b,
WWHH.DIM_R_NOMA_V c,
WWHH.DIM_R_TIME_V d
WHERE
b.STORE_ID = a.CIIDCA AND
c.ARTICLE_ID = a.NMIDCA AND
d.DAY_ID = a.CLIDCA
GROUP BY GROUPING SETS ( ...)
Could you tell me where to check in metadata that MVIEW is correctly setup?

ENT-06954: Error while Displaying BIBean for Cube/Dimension Dataviewer.

Hi all,
I have defined a cube with three dimensions. All elements are deployed and the mappings is executed successfully. If I try to open the dataviewer either for the cube or for the dimensions I receive the following errors:
ENT-06954: Error while Displaying BIBean for Cube Dataviewer.
     at oracle.wh.ui.owbcommon.dataviewer.dimensional.CubeDataViewerMain.getDataviewObject(CubeDataViewerMain.java:391)
     at oracle.wh.ui.owbcommon.dataviewer.dimensional.CubeDataViewerEditor._init(CubeDataViewerEditor.java:66)
     at oracle.wh.ui.editor.Editor.init(Editor.java:1115)
     at oracle.wh.ui.editor.Editor.showEditor(Editor.java:1431)
     at oracle.wh.ui.owbcommon.IdeUtils._tryLaunchEditorByClass(IdeUtils.java:1431)
     at oracle.wh.ui.owbcommon.IdeUtils._doLaunchEditor(IdeUtils.java:1344)
     at oracle.wh.ui.owbcommon.IdeUtils._doLaunchEditor(IdeUtils.java:1362)
     at oracle.wh.ui.owbcommon.IdeUtils.showDataViewer(IdeUtils.java:864)
     at oracle.wh.ui.owbcommon.IdeUtils.showDataViewer(IdeUtils.java:851)
     at oracle.wh.ui.console.commands.DataViewerCmd.performAction(DataViewerCmd.java:19)
     at oracle.wh.ui.console.commands.TreeMenuHandler$1.run(TreeMenuHandler.java:188)
     at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:178)
     at java.awt.EventQueue.dispatchEvent(EventQueue.java:454)
     at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
     at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)
ENT-06972: Error while Displaying BIBean for Dimension Dataviewer.
     at oracle.wh.ui.owbcommon.dataviewer.dimensional.DimDataViewerMain.getDimensionListObject(DimDataViewerMain.java:479)
     at oracle.wh.ui.owbcommon.dataviewer.dimensional.DimDataViewerEditor._init(DimDataViewerEditor.java:89)
     at oracle.wh.ui.editor.Editor.init(Editor.java:1115)
     at oracle.wh.ui.editor.Editor.showEditor(Editor.java:1431)
     at oracle.wh.ui.owbcommon.IdeUtils._tryLaunchEditorByClass(IdeUtils.java:1431)
     at oracle.wh.ui.owbcommon.IdeUtils._doLaunchEditor(IdeUtils.java:1344)
     at oracle.wh.ui.owbcommon.IdeUtils._doLaunchEditor(IdeUtils.java:1362)
     at oracle.wh.ui.owbcommon.IdeUtils.showDataViewer(IdeUtils.java:864)
     at oracle.wh.ui.owbcommon.IdeUtils.showDataViewer(IdeUtils.java:851)
     at oracle.wh.ui.console.commands.DataViewerCmd.performAction(DataViewerCmd.java:19)
     at oracle.wh.ui.console.commands.TreeMenuHandler$1.run(TreeMenuHandler.java:188)
     at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:178)
     at java.awt.EventQueue.dispatchEvent(EventQueue.java:454)
     at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
     at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)
In another warehouse this function works properly. I am using OWB 10gR2 (10.2.0.1.31).
Any hints to fix this issue would be appreciated.
Thanks in Advance, C.

If you run OWB using the supplied shell script or batch file are there other errors on the console before the exception. OWB uses a component (OLAPI does some validation over and above any other) which dumps the errors on the the standard output which often illustrates some invalid metadata in the OLAP catalog.

Rollup and Cube

can anyone xplain rollup and cube function in Groupby clause

Google "rollup and cube in oracle" or
http://www.psoug.org/reference/rollup.html
HTH
Girish Sharma

How to know Whether Partition is done for Cube or not

Hi All,
I need information regarding Partition of a cube.
a)How do i know the Partition is done or not for Cube
b)On what basis we should make parttion of Cube.
Thanks and Regards,
C.V.

There are several threads on partitioning, so it would be a good start for this question (as with any question) to search the BI forums on "Partitioning" and review thsoe first.
Some basic considerations on partitioning -
- Your DB must support Range partitioning to permit partitioning your InfoCube. The option will be greyed out if it is not available.
- InfoCube must be empty to be partitioned.
- InfoCube can only be partitioned on 0FISCPER or 0CALMONTH. You can define it so that you have a partition for each month/fiscper, or so that each partition will hold a few or several months of data.
- Generally, you would not partition small cubes.
- Thru BW 3.5 Aggregates automatically get partitioned the sme way the InfoCube is partitioned as long as the partitioning characteristic is in the aggregate. In 2004s, I believe you have options as to whether an aggregate gets partitioned or not.
- Partitioning may be done for query performance reasons and data administration. If the queries on the InfoCube regularly run with restrictions/filters on the partitioning characteristic (FISCPER or CALMONTH), the database will "prune" any partitions that do not contain the FISCPER/CALMONTH value(s), so that it does not need to consider them , e.g. most of your users only run a sales query for the current and previous month, but your cube contains 3 years of data. By partitioning on CALMONTH (we'll assume 1 partition / month), the database will exclude all but the two partitions from consideration. This could help query performance a lot. or maybe only a little, depending on a variety of other factors.
Again - it is important that the queries restrict onthe partitioning characteristic to be of any value on query performance. So don't partition on FISCPER if all the queries use CALMONTH for restrictions.
The data adminsitration reason you might partition is to improve selective deletion or archiving time. These processes are capable of using a DB function to Drop the partition, which quickly removes the data from the cube, rather than having to run a resource intensive Delete query. This only happens if you deletion/archiving criteria is set to remove an entire partition of data.
Again - review the other threads on the BI forums on Partitioning. Most questions you have will already have been asked and answered before, and post again on SDN if there is something you still have a question about.

How to create infopackage for Cube to Cune to transaction

HI Experts
I have performed following steps for cube to cube load.
1. Created source cube and loaded the data from R3
2. Created Destination cube
3. Generated Export Data source for the source cube. Here I'm able to see my datasource Icon(8ZFIGL_C01). When I double click on that it is give details.
4. Defined the update rules for Destiination cube by assiging the infosource (8ZFIGL_C01) which is created in step3.
5.Now I'm searching for the infosurce (8ZFIGL_C01) in data modelling -> infosource. its not showing up any name with 8ZFIGL_C01.
Kindly let me know how to create infopackage for this to laod the data from cube to cube.
Additional information:
I have set the optopn Display Generated Object in Settings.
Thanks in advance for your help.
Regards
NLN

Hi,
Right Click on "Infosource" (TA RSA12 Top at the Right side Panel) and choose Insert lost nodes and refresh the screen and now search for your infosource and you will find it.
See solution from SAT:
Problems with Infosource Data Marts
Best regards,
Frank

Help!Create Aggregates For Cube 0C_C03 Ocurs Eror

When I create a aggregate for cube 0ic_c03, and fixed value to characteristic '0PLANT', Error occurs as following: ,how can I do?
'acna': InfoCube '0IC_C03 contains non-cumulatives: Ref. char. 0PLANT not summarized
Message no. RSDD430
Diagnosis
InfoCube 0IC_C03 contains key figures that display non-cumulative values. The non-cumulative values, however, can only be correctly calculated, if the aggregate contains all characteristic values of the reference characteristics (the characteristics for the time slice).
System response
The aggregation level was set to 'not aggregated' for the reference characteristics.

Hi Shangfu,
Info cube 0IC_C03 consists of non-cumulative key figures which means breifly the values are aggregated in run-time based on Time characteristics.
Include time characteristics "0CALDAY" as part of the aggregate in addition to "0PLANT" object to avoid this problem.
There are many OSS Notes explaining the purpose and usage of Non-cumulative key figures.
Cheers
Bala Koppuravuri

Help! oracle report out of order after update Rollup for windows 2000 sp4

hello once again
i haven't received any solution of my problem, so i am again uploading it.
----PROBLEM IS GIVEN BELOW-----
i am having a problem in oracle report printing (2000,6i). I have installed patch "update Rollup for windows 2000 sp4" on windows 2000. now when i send report(132 column) for printing to the printer, the report fails to expand to 132 columns and data is printed in unformatted fashion. in order to print the report correctly i have to remove the patch from the windows.i have set all parameters and
defining page size in files like wide180.PRT in printers folder in oracle directory.
Is there anyway to print the report without uninstalling windows patch?
thanks

I don't have any idea about this issue. Maybe someone else on this forum can help. Meanwhile, there are couple of places you can search for this issue:
Search google for printing issues with this patch
Search Microsoft forums for Windows 2000
And if you have metalink account, search metalink forum, document/note or open a SR for this.

Enterprise Hotfix Rollup for Win7 and Server 2008 R2 via WSUS

I stumbled across the fact that Microsoft released a hotfix rollup for Win7 and Server 2008 R2 that contains 90 hotfixes
http://support.microsoft.com/kb/2775511/en-us
The articled I linked above talks about after installing 2775511 (the big hotfix rollup containing 90 hotfixes) it is also necessary to install three more hotfixes:
After this update is installed, you must install update 2732673 to fix a regression issue in the Rdbss.sys file
After this update is installed, you must install update 2728738 to fix a regression issue in the Profsvc.dll file
After this update is installed, you must install update 2878378 re-released on November 11, 2013 to fix a regression issue in the Advapi32.dll file
I have imported all four of these hotfixes into my WSUS server. Do I need to install 277551 first and then install the other three or can all four be approved and go out at once? I guess I am hung up on the language of "After this update is installed
.... ". I want to put all 4 of these on our Win7 machines as well as my 40+ WinServer 2008 R2 machines

I read somewhere that over half of the updates included in Win7 SP1 and WinServer 2008 R2 SP1 were originally released as hotfixes. This means Microsoft made the decision that a large number of hotfixes would benefit every user of these two OSs
I think your conclusion is flawed. The only thing that you can draw from the presented statistic, is that Microsoft determined that a significant percentage of updates originally released as hotfixes warranted the additional investment in regression testing
to subsequently release those hotfixes as updates.
The fact that they bundled these 90 hotfixes together leads me to the same conclusion.
In fact, exactly the opposite conclusion applies: What you have in this package is all the rest of the stuff that didn't make that cut. What you have in this package are still NOT-regression tested hotfixes, they've just been bundled up for easy deployment
(and note that three of them got further broken in the process of bundling), causing yet three more hotfixes to have to be released.
In fact I read the MS Team Blog about this big hotfix release and they say the same thing, all users of these OSs would benefit from the installation of this hotfix rollup, not just a subset of users.
I suspect there are a notable number of patch administrators and systems administrators who would disagree with that self-serving promotion. If, in fact, it's true that "all users" would benefit, then the product team should have invested the effort in properly
regression testing those hotfixes, and releasing them as REAL updates. They did not; ergo the *actual* value is less than claimed.
Of course the bugaboo here is the fact that three other individual hotfixes need to be installed after the big hotfix rollup is installed.
Exactly! (And those are just the attempted fixes that broke something. Who knows how many other "fixes" may still result in newly discovered "broken stuff" that was never broken in the first place.)
The second part of this question should revolve around an itemized review of the hotfixes contained in this rollup with one simple question asked for each:
Have we actually *experienced* the issue addressed by this hotfix.
Where hotfixes are concerned one very simple but important rule applies:
If it ain't broken, don't try to fix it!
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

Rollup and Cubes

Hi
I am new to use Rollup and Cubes.
I have one query with the correct syntax as per the tutorial, but i am getting the error.
Can anyone let me know where and what is the error in this ?
select cont,ctry,stat, sum(pop) ,
grouping(cont) as Continent,
grouping(ctry) as Country,
grouping(stat) as State
from dim1
group by rollup(cont,ctry,stat)
having (Continent = 1 and Country=1 and State=1)
or (Country=1 and State=1)
or (Continent=1 and State=1)
SQL> /
or (Continent=1 and State=1)
ERROR at line 9:
ORA-00904: "STATE": invalid identifier
Thanks
JC

That syntax is wrong:
SQL> create table dim1
2 as
3 select 'Europe' cont, 'Netherlands' ctry, 'Utrecht' stat, 1000000 pop from dual
4 /
Tabel is aangemaakt.
SQL> select cont,ctry,stat, sum(pop) ,
2 grouping(cont) as Continent,
3 grouping(ctry) as Country,
4 grouping(stat) as State
5 from dim1
6 group by rollup(cont,ctry,stat)
7 having (Continent = 1 and Country=1 and State=1)
8 or (Country=1 and State=1)
9 or (Continent=1 and State=1)
10 /
or (Continent=1 and State=1)
FOUT in regel 9:
.ORA-00904: "STATE": invalid identifierThe error is in the having clause. If we remove it, the SQL becomes valid again:
SQL> select cont,ctry,stat, sum(pop) ,
2 grouping(cont) as Continent,
3 grouping(ctry) as Country,
4 grouping(stat) as State
5 from dim1
6 group by rollup(cont,ctry,stat)
7 /
CONT   CTRY        STAT    SUM(POP) CONTINENT COUNTRY    STATE
Europe Netherlands Utrecht 1000000         0        0        0
Europe Netherlands          1000000         0        0        1
Europe                      1000000         0        1        1
                            1000000         1        1        1
4 rijen zijn geselecteerd.If you want the having clause, you have to refer to the grouping functions, not the aliases:
SQL> select cont,ctry,stat, sum(pop) ,
2         grouping(cont) as Continent,
3         grouping(ctry) as Country,
4         grouping(stat) as State
5    from dim1
6   group by rollup(cont,ctry,stat)
7 having (grouping(cont) = 1 and grouping(ctry)=1 and grouping(stat)=1)
8      or (grouping(ctry)=1 and grouping(stat)=1)
9      or (grouping(cont)=1 and grouping(stat)=1)
10 /
CONT   CTRY        STAT    SUM(POP) CONTINENT COUNTRY    STATE
Europe                      1000000         0        1        1
                            1000000         1        1        1
2 rijen zijn geselecteerd.Regards,
Rob.

No records for cube in production!

Hi,
we have a strange ituation where in i am finding records for a cube in dev but not in production!
i had transported right from infoobjects ( which i had added in dev for cube enhancements ) to update rules to production but still i did not find any records in production!
can u pls tell me what could be the problem? or i had missed something in transportaion?
Thanks,
Ravi

Hi,
I don't understand.... Do you expect to see the same records in your cube in your prod sys than in your deve sys just by transporting the change?
No: you have to load your cube with data in prod!
or do you think that when adding a new IObj in a cube and transport the changes then the new IObj will be populated?
No either, you'll have to reload your data.
please describe in detail your issue
hope this helps...
Olivier.

Best Practice For Cube Design

All,
First post here and was wondering if anyone out there has a best practice for cube design or optimisation. Currently have 7 Cubes that have been populated for the last 6 months and am now looking at ways of speeding up their population.
Are there any hard and fast rules about dimensions?
Should they be kept to a percentage of the fact table?
When should line item dimensions be used?
Regards
Gary Boyle

Hi Gary,
Ideally the DIM tables should be 20% of the fact table and preferably less. You can check the size ratios in RSRV using the Database tables test > Database info about InfoProvider tables. Line items dimensions should be employed where the char has a large number of unique values (like 0MATERIAL, or 0CUSTOMER), so that anothe DIM ID is not created, but the SID values are used directly in the Fact Table.
See these for more:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/media/uuid/10b589ad-0701-0010-0299-e5c282b7aaad
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/08f1b622-0c01-0010-618c-cb41e12c72be
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/6ce7b0a4-0b01-0010-52ac-a6e813c35a84
Hope this helps...

Bi 7.0 for cube and master data steps

hi friends,
can u give me step by step comparision between bi 7.0 and bi 3.0 for cube ods and master data, ple explaing me what are the steps difference for those in bi 7.0 .
and reporting is same or any difference in bi 7.0 .
other than sap.help.com material, if u have any other or any screen shots. ple send me.
Thanking u
suneel.

what abt master data, in master data we are using only transfer rules, here also we are using transformation and dtp again.
Yes we would be using transformations and DTP's on the masterdata too. but the system would prompt to make IO a infoprovider in order to use the new functionality. There is another work around for it, but we can discuss it later, orelse search the forum for that option, i have replied to couple of questions regarding that.
what abt reporting any things other than calculated kf restricted kf, filters rows columns, free chaststics, variables, any chnages in screen.
The basic functionality of all the above mentioned objects havent changes, and the query designer itself, there are hell a lot of changes in the appearance and it will take a while to get used to it and find your way with all the functionalities.
i have doubt bps menas businees planning simulation what is this, bec i have idea we can use transactional cube and transactional ods for write accress for planninmg also
BPS is something I have no clue abt... (you dont see me answering in Business planning forum)

Rollup for cube

Similar Messages

Maybe you are looking for