Maximum No of Dimensions.

HI Experts,
Can any one tell me why the no. of dimensions is restricted to 16 only??..Is it possible to include more then 16 dimensions ??

The Maximum Number of Dimensions in a Cube are 16
3 are pre defined by SAP
Data packet , Time , Unit ( all these collectively called as PTU)
and apart from these 13 dimensions can be created by User ( these are called userdefined dimensions)
In typical SAP BW practice it is mandatory to have a minimum of 4 dimension to create a cube. i.e u should create at least one dimension other than PTU dimensions created by BW system.
as far as my knowledge goes no body in the Industry has created 16 dimension Cube till date. Only Microsoft has started to implement with 16 dimension cube.
hope this helps you.
please assign points if you feel the information is useful

Similar Messages

Is there any limitations to the maximum number of dimensions in MP?

hi all
Is there any limitations to the maximum number of dimensions can be created in Multi provider. If so how what is the maximum number of dimensions that can be created in a multi provider?
regds
haritha

Hi,
Maximum number of dimensions 16. Out of 16, 3 are system defined
1.Datapacket
2.Time
3.Unit
It is restricted to 16 because the maximum no of dimensions in any database is 16.
Reward points if helpful
Cheers
Raj

Maximum number of dimensions for an array

What is the maximum number of dimensions an array can accept:
a. 266
b. 255
c. 256
d. 250
which option is correct and why?

sabre150 wrote:
I don't know and I most definitely don't care since anything more than 2 is, in my opinion, just silly.It's also quite untractable from a memory standpoint. Say you have an 10 by 10 by 10 array. That's 10^3 elements. Now say you have 250 dimensions, that's 10^250 elements which is a huge number in the order of the number of atoms in the universe or so.
Say you instead have just 1 element in each dimension. Then you got a total of 1^250 elements, which is 1 element. That's okay but you don't need the array because 1 element is a variable. This means an array has at least 2 elements in each dimension. That's 2^250 elements which is like 10^75 which is also a huge number. You wouldn't get that kind of memory even if you added up all computers that ever existed.
So array dimensions in the order of 250 aren't just silly, there isn't enougth memory for them.

Maximum number of dimensions & databases allowed & recommended in Essbase?

Hi,
can anyone one give input on what are Oracle recommendations on maximum number dimensions & databases allowed & recommended in Essbase?

Hi John,
Thanks for your post, I also have the same query related to Dimensions and Databases of (ASO,BSO) application, as i donot found anything like this in
http://docs.oracle.com/cd/E17236_01/epm.1112/esb_dbag/limits.htmlwhat is the maximum number of dimension & databases we can use in essbase application. like we have limitation of dimensions and database in Planning application
Thanks,
Avneet

Maximum movie stage dimensions in Flash CS4?

Anyone know what is the maximum movie stage dimensions in Flash CS4? Thanks for any info.

I don't remember for MX but I know in CS3 and CS4 your movie clips can be much larger than the max stage size (if you need them to be). I guess I misunderstood your original question as the stage size not the movie clip dimensions.

Maximum amount of dimensions in dimension analysis FC 7.5

Hello, dear colleagues!
Our project team have met problem, using SAP Business Objects Financial consolidation 7.5 (service pack 13 installed). Problem ties with dimension analysis in category. When we try adjust u201Cbreakdown of dimension analysisu201D by 7 dimensions, category canu2019t be validated and we have to shut down Financial Consolidation through task manager (system doesnu2019t respond after starting validation process u2013 at least 5 hours was not enough when we tested it). If we try to adjust breakdown u201Cbreakdown of dimension analysisu201D only by 6 dimensions, system works correct, and category validate within 3-4 seconds. We havenu2019t find any information about maximum number of possible dimensions in breakdown, but itu2019s hard to believe, that itu2019s only 6. We use "post breakdown total to a higher level" options in breakdown.
If anyone has any ideas, please post an answer! Thanks!

Hello Alexander
The link is to a published KB article on the SMP
For this to work, you need to be a registered user (i.e. have a valid S-number)
But, to summarize: BFC currently only supports up to 7 dimensions in a Dimensional Analysis.
Best regards,
Marc

Maximum texture size/dimensions?

Greetings -
I've read in various places that the max texture size for Stage3D is 2048x2048. Perhaps this is an obvious question, but does this mean that each dimension must be 2048 or less, or that the total size in pixels be less than 2048x2048=4194304? So, is a 4096x1024 texture OK, or not?
Thanks!

Hey
It means that each dimension must be 2048 or less.

Maximum number of dimensions

Hi! Sorry the stupid question, how many dimensions can you have in an Essbase cube? I have heard 21? Thanks

As many as you want. However when doing this you need to think about your user base, and how easy they will find it to understand. You also need to check the density or sparsityof your data, and see whether there is scope for condensing anything. You can also use Attribute dimensions (if you are on Essbase 6.5.6 or above - below they don't work 100% correctly) to analyse data in different ways.

Maximum number of Attribute dimensions Possible in BSO Cube

hi,
i have two simple queries :
1 - What are the maximum number of Attribute dimensions Possible in a BSO Cube.
2- How many attribute dimension can be associated with one base Dimension.
hope to get reply soon.
thanks in advance.
Regards
Anubhav

No Limits are defined as such:
How many Maximum number of Dimensions can create ?
Even in the Dbag, it says "many":
A base dimension member can have many attributes, but only one attribute from each attribute dimension.Cheers..
Rahul S.

Discoverer 4i - Max Dimensions Supported?

Is there any limitation on the maximum number of dimensions that can be supported in Discoverer 4i?
Thanks & Regards,
Deepti

I have not run into any problems with Discoverer while setup in a Star Schema.
Christopher

Aggregates for master data & Line item Dimension

Hi i have question
1 Can we create Aggregate for Master Data?
2 Can we create Aggregate with Navigational Attributes?
3 Can we create Aggregate with Line Item Dimension?
4 How many dimension we can add with how many characteristics in it if we create a new Aggregate

1 Can we create Aggregate for Master Data? - No
2 Can we create Aggregate with Navigational Attributes? - No
3 Can we create Aggregate with Line Item Dimension? - No
4 How many dimension we can add with how many characteristics in it if we create a new Aggregate - You can create a maximum of 13 dimensions in the cube.You can add as many characteristics for an aggregate,adding many characteristics in the aggregate is as good as having the query fetch data from the Cube instead of the aggregates.
Aggregates are subsets infocubes derived from the main InfoCube to increase the query performance.You can create as many aggregates you want in an InfoCube.
For each aggregate,internally dimensions are created based on the selected characteristics.
Take a look at this link for detail information...
http://help.sap.com/saphelp_nw04/helpdata/en/7d/eb683cc5e8ca68e10000000a114084/content.htm

Numbers of Applications and dimension in an Appset

Hi!
Are there any recommendations or restrictions on how many applications and dimensions that you can have in one Appset.

Hi Daniel,
The adminmanual that comes with the product indicates that there are some maximums, I have added them below.
Personally I never encounterd/crossed the maximum for the number of dimensions (65.000 is a lot ) or the number of cubes within an appset.
Alwin
document as MS Analysis Services).
MS Analysis Services provides the online analytical processing (OLAP) and data mining capability behind
BPC.
Item Specification BPC notes
Dimensions in a database 65,535 maximum, regardless
of the number of cubes or
whether dimensions are shared
or private
There is no limit to the number of
dimensions defined in an AppSet but
an application cannot have more
than 20 dimensions
Levels in a database 65,535 maximum
Cubes in a virtual cube 64 maximum No explicit support for virtual cubes
Measures in a cube 1,024 maximum BPC uses one input measure, and
uses calculated measures for
frequencies.
Useru2019s Guide: SAP BPC Administration
August 2007 Page 170 of 220
Item Specification BPC notes
Measures in a virtual cube 2,048 maximum Not applicable.
Dimensions in a cube 128 maximum, including the
Measures dimension
20 is the recommended maximum
number of dimensions for BPC
Levels in a cube 256 maximum
Levels in a dimension 64 maximum The number of levels you can have in
BPC is dependent on the number of
properties in the dimension.
Members in a virtual
dimension created in SQL
Server version 7.0 OLAP
Services
759 maximum No explicit support for virtual
dimension. Virtual dimensions can be
manually created and used in
applications.
Members in a parent 64,000 maximum 5,000 members per dimension
supported for version 2000
Calculated members (server
defined) in a cube
65,535 maximum
Calculated members in a
parent measure in session
context
31,743 maximum
Calculated members in a
parent measure in query
context
31,743 maximum
Calculated members in a
parent dimension member in
session context
759 maximum
Calculated members in a
parent dimension member in
query context
759 maximum
Aggregations per partition 65,535 maximum
Cells returned by a query 2^31-1 = 2,147,483,647 cells
maximum. Although cubes can
be larger than this limit, a
query that requests more than
2^31-1 cells from a cube will
fail
Record size for source
database table
8060 bytes maximum
Length of object name
(except dimension name)
50 characters maximum when
using Analysis Services
Manager. 24 characters
maximum when using
PivotTable® Service
Max. 50 characters for member
names, and 50 characters for
member descriptions
Length of dimension name 24 characters maximum Max. 20 characters for dimension
names, and 50 characters for
dimension descriptions.
Useru2019s Guide: SAP BPC Administration
August 2007 Page 171 of 220
Item Specification BPC notes
Length of aggregation prefix 50 characters maximum

Maximum number of applications per application set

Hello,
I know maximum number of dimensions per application is 20 in OutlookSoft 4.2.
What about maximum number of applications per application set?
Regards,
Hiroshi Yaji

Hiroshi - I have not encountered a technical limit on the number of applications in an appset. As a practical reality, performance and system administration will dictate how many apps an appset may contain.
On a related note, you could theoretically have more than 20 dimensions in an app. However, I have only worked with one client who asked (needed?) an app with more than 12 dimensions. In that case, usability was an issue due to the complexity in submitting data to an app with that many dimensions.
Hope that helps,
Jeff

ORA-13000: dimension number is out of range when using SDO_GEOM.RELATE

Dear everyone
I am attempting to workout which polygons cover the same area in order to determine distinct polygons. This is so I can then have just one copy of a polygon to a new table and delete all the duplicate polygons in the current table.
I ran the following first to check something:
SELECT SDO_GEOM.RELATE
 (A.geographical_coordinates,
 'DETERMINE',
 B.geographical_coordinates,
 0.05) relationship
FROM MAP_INDEX A,
 MAP_INDEX B
where A.geographical_coordinates is not NULL
and B.geographical_coordinates is not NULL;but got the error message:
Error starting at line 1 in command:
SELECT DISTINCT A.mi_prinx,
SDO_GEOM.RELATE
 (A.geographical_coordinates,
 'EQUAL',
 B.geographical_coordinates,
 0.05)
FROM MAP_INDEX A,
 MAP_INDEX B
where A.geographical_coordinates is not NULL
and B.geographical_coordinates is not NULL
Error report:
SQL Error: ORA-13000: dimension number is out of range
ORA-06512: at "MDSYS.SDO_GEOM", line 70
ORA-06512: at "MDSYS.SDO_GEOM", line 2647
13000. 00000 - "dimension number is out of range"
*Cause: The specified dimension is either smaller than 1 or greater than
 the number of dimensions encoded in the HHCODE.
*Action: Make sure that the dimension number is between 1 and the maximum
 number of dimensions encoded in the HHCODE.I then tried the following:
SELECT DISTINCT A.mi_prinx,
SDO_GEOM.RELATE
 (A.geographical_coordinates,
 'EQUAL',
 B.geographical_coordinates,
 0.05)
FROM MAP_INDEX A,
 MAP_INDEX B
where A.geographical_coordinates is not NULL
and B.geographical_coordinates is not NULLwhich produced the following error message:
Error starting at line 1 in command:
SELECT
SDO_GEOM.RELATE
(A.geographical_coordinates,
'EQUAL',
B.geographical_coordinates,
0.05) relationship
FROM MAP_INDEX A,
 MAP_INDEX B
Error report:
SQL Error: ORA-13050: unable to construct spatial object
ORA-06512: at "MDSYS.SDO_3GL", line 4
ORA-06512: at "MDSYS.MD2", line 771
ORA-06512: at "MDSYS.SDO_GEOM", line 2622
ORA-06512: at "MDSYS.SDO_GEOM", line 2649
13050. 00000 - "unable to construct spatial object"
*Cause: This is an internal error.
*Action: Contact Oracle Support Services.Does anyone have any idea as to what I might doing wrong? The original polygons were created in MapInfo Professional 8 and I am working in 10.2g
I believe Imust be doing something wrong. I looked into SDO_GEOM_VALIDATE but again that produce the same error message as the first one. I have previously created a spatial index and inserted the values into the USER_SDO_GEOM_METADATA view.
I have been able to get the following to work, I was testing out examples online just to see if I could produce a result on an sdo function:
SELECT NAME_OF_FEATURE, SDO_GEOM.SDO_AREA(GEOGRAPHICAL_COORDINATES,M.DIMINFO)
FROM MAP_INDEX, user_sdo_geom_metadata M
WHERE M.TABLE_NAME='MAP_INDEX' AND M.COLUMN_NAME='GEOGRAPHICAL_COORDINATES'
AND geographical_coordinates is not null;When I drew my polygons in MapInfo, they are likely to have gone partly outside of the boundary dimension values inserted in USER_SDO_GEOM_METADATA. Is that likely to be the cause of my problems or something else?
If it is the cause, is there away of setting up Oracle or MapInfo so that anything drawn outside of the dimension area is clipped.
Kind regards
Tim

Hi Tim,
Since Oracle 8.1.6 Oracle has suggested the use of 4 digit SDO_GTYPE values, which encode the number of dimensions in the geometry. Examples of 4 digit SDO_GTYPES include 2001 for a 2D point, 3001 for a 3D point, 2002 for a 2D linestring, 3002 for a 3D linestring, 2003 for a 2D polygon and 3003 for a 3D polygon.. Contrast these with single digit values of 1 for a point, 2 for a linestring, and 3 for a polygon.
My guess is that at least some of your data is loaded using single digit SDO_GTYPE values, and in the function Oracle does not know the dimensionality of the data (is a vertex identified by 2, 3, or four numbers?). You can check this by doing a:
select distinct a.geographical_coordinates.sdo_gtype from MAP_INDEX A;
If any of the values returned are single digit values then you will know this is the problem.
You have a few options.
You can have Oracle automatically fix the data by migrating the data:
execute sdo_migrate.to_current('MAP_INDEX','GEOGRAPHICAL_COORDINATES');
This will not only set the SDO_GTYPE correctly but will also fix any ring rotation problems (ensures exterior rings are stored counter-clockwise, and interior rings are stored clockwise), it will fix ring ordering problems (ensuring an exterior ring is followed by its interior rings), and it will appropiately set values in the SDO_ELEM_INFO_ARRAY.
After you do this you should be good to go. However, if you are using a tool to update the data and it resets the information back, then the problem will continue to plague you. You should check with your vendor if that is the case.
Another option is to change the query to a different signature which uses the SDO_GEOM_METADATA to get the dimensionality of the data. Instead of writing the query as you have, you would change it to:
SELECT SDO_GEOM.RELATE
(A.geographical_coordinates,
C.DIMINFO,
'DETERMINE',
B.geographical_coordinates,
C.DIMINFO) relationship
FROM MAP_INDEX A,
MAP_INDEX B,
USER_SDO_GEOM_METADATA C
WHERE A.geographical_coordinates is not NULL
and B.geographical_coordinates is not NULL
and C.TABLE_NAME='MAP_INDEX'
and C.COLUMN_NAME='GEOGRAPHICAL_COORDINATES';
So either of those should fix the problem you are seeing, but neither of those are the best way to accomplish what you want to do.
If I were you I would follow first set of directions (migrate your data), make sure I have a spatial index on my table:
select index_name
from user_sdo_index_info
where table_name='MAP_INDEX';
If no rows are returned, create the index:
create index MAP_INDEX_SIDX on MAP_INDEX(GEOGRAPHICAL_COORDINATES)
indextype is mdsys.spatial_index;
You could use SDO_JOIN to perform a self-join:
http://download.oracle.com/docs/cd/B28359_01/appdev.111/b28400/sdo_operat.htm#BGEDJIBF
using the EQUAL mask. Note the section on optimizing self-joins.
If you don't have too much data, this might be a start to doing what you want:
create table dups_rowids as
select /*+ ordered */ a.rowid rowid1,b.rowid rowid2
from MAP_INDEX A,
MAP_INDEX B
where SDO_EQUALS (a.geographical_coordinates,b.geographical_coordinates)='TRUE'
and a.rowid <> b.rowid;
create table nodup_rowid (noduprid VARCHAR2(24));
create table dup_rowid (duprid VARCHAR2(24));
set serveroutput on;
declare
rowida varchar2(24);
rowidb varchar2(24);
rowidt varchar2(24);
type myCursor is ref cursor;
acursor myCursor;
cursor c1 is select rowid1,rowid2 from dups_rowids;
begin
for r in c1 loop
rowida := r.rowid1;
rowidb := r.rowid2;
rowidt := NULL;
open acursor for 'select duprid from dup_rowid where duprid = :rowida' using rowida;
fetch acursor into rowidt;
if rowidt is null
then
execute immediate 'insert into nodup_rowid values (:rowida)' using rowida;
execute immediate 'insert into dup_rowid values (:rowida)' using rowida;
execute immediate 'commit';
end if;
close acursor;
rowidt := NULL;
open acursor for 'select duprid from dup_rowid where duprid = :rowidb' using rowidb;
fetch acursor into rowidt;
if rowidt is null
then
execute immediate 'insert into dup_rowid values (:rowidb)' using rowidb;
execute immediate 'commit';
end if;
close acursor;
end loop;
end;
Then your final table would have the geometries from the original table that had no match:
create table MAP_INDEX_NODUPS
as select * from MAP_INDEX where rownum < 1;
insert into MAP_INDEX_NODUPS
(select *
from MAP_INDEX
where ROWID not in
(select ROWID1 from DUPS_ROWIDS));
plus only one of the geometries that were equal:
insert into MAP_INDEX_NODUPS
(select *
from MAP_INDEX
where ROWID in
(select ROWID1 from NODUP_ROWID);
Hope this helps.

Why each cube has 16 dimensions?

Hi friends,
why each cube is restricted to 16 dimensions? what is the technical reason behind it?
I have searched a lot and finally posting the question here.
Thanks & Regards
Swathi

HI
Q. why an infocube has maximum of 16 dimensions?
A. Because any Database will supports only 16 foreign keys in a database table.
     As the total charecterstics are 255, out of which 16 charecters are being allowed for foreign keys
     and 6 charecters are for sap default, for this sake we have only 16 dimention tables, of which
     3 are again sap default (unit, time. Datapacket): so finally we have only 13 user dimentions.
    Latest Answer : As the total charecterstics are 255, out of which 16 charecters are being allowed
    for foreign keys and 6 charecters are for sap default, for this sake we have only 16 dimention tables,
    of which 3 are again sap default (unit, time. Datapacket): so finally ...

Maximum No of Dimensions.

Similar Messages

Maybe you are looking for