Solved Dimension

Hello All,
OWB 10gR2 talks about solved dimension to connect dimension at different level other than the lowest level.
Well in earlier versions of OWB when we needed to connect fact to a dimension other than lowest level, created a view to that level and used the view to connect to the desired level.
For E.g: Time Dimension Pay Fact
Year Level Monthly Salary
Month Level
Day Level
Now Pay Fact data is monthly data. We can create a "view" month_time_dimension which is grouped by month_id and this view has month_id at lowest level and we can join the Pay Fact to it.
Some people talk about creating different time dimension for each level but if we use views we have only one physical Time Dimension with different views. Which might me right ?? My guess..
Information about solved dimension: Page 20
http://www.oracle.com/technology/products/warehouse/pdf/OWB10gR2%20and%20Data%20Modeling.pdf
How do the "solved" dimension handle the problem of connecting fact at different level?? How they handle SCD2?? How they are implemented??
How is drill down/drill up etc handled in both the cases??
Any inputs are of great value. Thanks in advance.
Regards,
Suraj.

Similar Messages

Preaggregation across value based hierarchy dimension in 11g

Hi All,
I have created a cube with 6 dimensions in olap 11g. One of those six dimensions has only one hierarchy which is value based hierarchy. I have chosen level based aggregation as I know at what levels exactly users are going to query. When I was going through the dimensions to choose levels to preaggregate I noticed there were no options available for my value based hierarchy dimension ( I could see "all" option for the same case in 10g) then I tried to look for definitions of underlying objects just to make sure it will preaggregate data across my value based hierarchy dimension.
I found value set corresponding to my value based hierarchy dimension in <CUBE NAME>SOLVEAGGMAP object , which AWM uses to decide which dimension values to preaggregate but if I do rpr on that value set (rp r<CUBE NAME>SOLVE<DIMENSION NAME>_PVSET) it shows NA so my question is can I pre aggregate across value based hierarchy dimension in olap 11g?
Olap Version: 11.2.0.1
AWM version: 11.2.0.1
Thanks

Even if you know exactly which levels your users will query, percent based precompute (e.g. 30%) may still be faster in practice because queries are returned using 'sparse looping' instead of 'dense looping'. This was the single biggest performance advantage of 11g over 10g.
But if you still want to use level based precompute, then you should look at the XML template for the cube (as saved by AWM, for example). In it you should find something called PrecomputeCondition. This defines the set of members that are precomputed. Here is an example I just created using the GLOBAL schema
<PrecomputeCondition>
<![CDATA[
"TIME" LEVELS ("TIME"."MONTH", "TIME".CALENDAR_QUARTER, "TIME".CALENDAR_YEAR),
CHANNEL LEVELS (CHANNEL.TOTAL_CHANNEL, CHANNEL.CHANNEL),
CUSTOMER LEVELS (CUSTOMER.MARKET_SEGMENT, CUSTOMER.REGION, CUSTOMER.SHIP_TO),
PRODUCT LEVELS (PRODUCT.CLASS, PRODUCT.FAMILY, PRODUCT.ITEM)]]>
</PrecomputeCondition>The PrecomputeCondition is also visible through the USER_CUBES view.
SELECT PRECOMPUTE_CONDITION
FROM USER_CUBES
WHERE CUBE_NAME = 'MY_CUBE';You can hand modify this condition in the XML to specify an alternative 'non level based' precompute condition for any dimension. For example, if you define an attribute named 'SHOULD_PRECOMPUTE' on your PRODUCT dimension that is 1 for members to be precomputed and 0 for all others, then you can change the condition as follows.
<PrecomputeCondition>
<![CDATA[
"TIME" LEVELS ("TIME"."MONTH", "TIME".CALENDAR_QUARTER, "TIME".CALENDAR_YEAR),
CHANNEL LEVELS (CHANNEL.TOTAL_CHANNEL, CHANNEL.CHANNEL),
CUSTOMER LEVELS (CUSTOMER.MARKET_SEGMENT, CUSTOMER.REGION, CUSTOMER.SHIP_TO),
PRODUCT WHERE PRODUCT.SHOULD_PRECOMPUTE = 1]]>
</PrecomputeCondition>If you recreate the cube from the XML with this condition, then the PVSET valueset you discovered should contain all dimension members for which the attribute value is 1.   This gives you complete control over what is precomputed.   Note that AWM doesn't support this form of condition, so it won't show up if you go to the Precompute tab, but it is valid for the server. The PL/SQL below will modify the PrecomputeCondition (for the cube named MYCUBE) without going through AWM.
begin
dbms_cube.import_xml(q'!
<Metadata
Version="1.3"
MinimumDatabaseVersion="11.2.0.2">
<Cube Name="MY_CUBE">
    <Organization>
      <AWCubeOrganization>
        <PrecomputeCondition>
          <![CDATA[
           "TIME" LEVELS ("TIME"."MONTH","TIME".CALENDAR_QUARTER, "TIME".CALENDAR_YEAR),
           CHANNEL LEVELS (CHANNEL.TOTAL_CHANNEL,CHANNEL.CHANNEL),
           CUSTOMER LEVELS (CUSTOMER.MARKET_SEGMENT,CUSTOMER.REGION,CUSTOMER.SHIP_TO),
           PRODUCT WHERE PRODUCT.SHOULD_PRECOMPUTE = 1]]>
        </PrecomputeCondition>
      </AWCubeOrganization>
    </Organization>
</Cube>
</Metadata>
end;
/

Convert relational table to Dimension

Hi,
Suppose I have a Employee table includes columns:
+ emp_id (primary key)
+ emp_parent_key (a foreign key to emp_id)
+ emp_name
+ emp_birth
Could anyone tell me how to create the hierachies and attributes for dimension Employee?
Thanks,
Truong

Hi Truong,
that is a great question!
Essentially, you are asking how to convert an Oracle Extension (CONNECT BY which is a pseudo-4NF for what is really a 5NF structure) into a proper 1NF dimension table. This applies to organizations, products, employees, and all sorts of other dimensions where the issue is the dimensional hierachy structure rather than the levels (or members).
Wow! This is a really hard one.
!. The dimensional structuire in a dimensional star based RDBMS must be de-raggedised and fully balanced. This is a pre-requisite. I do this via custom code. I know of no other way to do it. Only you know whether your application generates ragged and/or unbalanced hierarchies. There is nothing in OWB that will do this for you, that I have used in the past.
(FYI, I write a recursive SQL tree-walker and package it.)
2. You have now clean hierarchies. You are now faced with the issue of basic versus solved dimensions. You are also faced with the issue (today) of the Paris inadequacies with regard to SCD 2 processing, and the issues around value-based hierarchies. Gee, but this is 'bleeding-edge' stuff!
Well, guess what? This whole thing landed on my desk today. We need Paris 10gR2 solved dimensions. They are the key to MV query rewrite, because of the huge semantic problem with regard to shrunken, collapsed, and lost dimensions, which I believe to be insoluble for the foreseeable future.
3. Refer to my paper on the Paris issues. Link is on this forum. But that will not tell you how to fix them. This, I am working on. I do not have a solution at this time. It will be on my website when I do.
To cut to the chase, you build as many levels as exist in your organization. You unpack the Parent-Child stuff. You clean it. You load it. You can use 9i techniques for mapping old/new and generating an SCD2 basic dimension table.
That will give you a first cut. What it won't give you is a method of updating it in Paris.
Stay tuned . . .
Cheers,
Donna
http://www.donnapkelly.pwp.blueyonder.co.uk

Dimension with SOLVED LEVEL-BASED hierarchy (10.2)

I'm trying to make a dimension with SOLVED LEVEL-BASED hierarchy (Oracle 10.2.0.1).
Hierarchy is folowing:
TOP
|_OWNER
|_OBJECT_TYPE
|_OBJECT_NAME
Script
DROP TABLE SOLVED_DIM;
CREATE TABLE SOLVED_DIM
GID NUMBER,
ETKEY VARCHAR2(100),
PARENT_GID NUMBER,
PARENT_ETKEY VARCHAR2(100),
SHORT_DESCRIPTION VARCHAR2(100),
LONG_DESCRIPTION VARCHAR2(100),
TOP                    VARCHAR2(100),
OWNER VARCHAR2(100),
OBJECT_TYPE VARCHAR2(100),
OBJECT_NAME VARCHAR2(100) ,
TOP_ID NUMBER,
OWNER_ID NUMBER,
OBJECT_TYPE_ID NUMBER,
OBJECT_NAME_ID NUMBER,
ID NUMBER
--Test dataset №1
INSERT INTO SOLVED_DIM VALUES (7, 'TOP', NULL, NULL, 'TOP', 'TOP', 'TOP', NULL, NULL, NULL, 1, NULL, NULL, NULL, 100001);
INSERT INTO SOLVED_DIM VALUES (3, 'SH', 7, 'TOP', 'SH', 'SH', 'TOP', 'SH', NULL, NULL, 1, 11, NULL, NULL, 100002);
INSERT INTO SOLVED_DIM VALUES (3, 'OLAP_USR', 7, 'TOP', 'OLAP_USR', 'OLAP_USR', 'TOP', 'OLAP_USR', NULL, NULL, 1, 12, NULL, NULL, 100003);
INSERT INTO SOLVED_DIM VALUES (1, 'SDIMENSION', 3, 'SH', 'SDIMENSION', 'SDIMENSION', 'TOP', 'SH', 'SDIMENSION', NULL, 1, 11, 111, NULL, 100004);
INSERT INTO SOLVED_DIM VALUES (1, 'ODIMENSION', 3, 'OLAP_USR', 'ODIMENSION', 'ODIMENSION', 'TOP', 'OLAP_USR', 'ODIMENSION', NULL, 1, 12, 121, NULL, 100005);
INSERT INTO SOLVED_DIM VALUES (0, 'OUD1', 1, 'ODIMENSION', 'OUD1', 'OUD1', 'TOP', 'OLAP_USR', 'ODIMENSION', 'OUD1', 1, 12, 121, 1211, 100006);
INSERT INTO SOLVED_DIM VALUES (0, 'OUD2', 1, 'SDIMENSION', 'OUD2', 'OUD2', 'TOP', 'SH', 'SDIMENSION', 'OUD2', 1, 11, 111, 1111, 100007);
commit;
--Test dataset №2
INSERT INTO SOLVED_DIM VALUES (7, 'TOP', NULL, NULL, 'TOP', 'TOP', 'TOP', NULL, NULL, NULL, 1, NULL, NULL, NULL, 100001);
INSERT INTO SOLVED_DIM VALUES (3, 'SH', 7, 'TOP', 'SH', 'SH', 'TOP', 'SH', NULL, NULL, 1, 11, NULL, NULL, 100002);
INSERT INTO SOLVED_DIM VALUES (3, 'OLAP_USR', 7, 'TOP', 'OLAP_USR', 'OLAP_USR', 'TOP', 'OLAP_USR', NULL, NULL, 1, 12, NULL, NULL, 100003);
INSERT INTO SOLVED_DIM VALUES (1, 'DIMENSION', 3, 'SH', 'DIMENSION', 'DIMENSION', 'TOP', 'SH', 'DIMENSION', NULL, 1, 11, 111, NULL, 100004);
INSERT INTO SOLVED_DIM VALUES (1, 'DIMENSION', 3, 'OLAP_USR', 'DIMENSION', 'DIMENSION', 'TOP', 'OLAP_USR', 'DIMENSION', NULL, 1, 12, 121, NULL, 100005);
INSERT INTO SOLVED_DIM VALUES (0, 'OUD1', 1, 'DIMENSION', 'OUD1', 'OUD1', 'TOP', 'OLAP_USR', 'DIMENSION', 'OUD1', 1, 12, 121, 1211, 100006);
INSERT INTO SOLVED_DIM VALUES (0, 'OUD2', 1, 'DIMENSION', 'OUD2', 'OUD2', 'TOP', 'SH', 'DIMENSION', 'OUD2', 1, 11, 111, 1111, 100007);
commit;
BEGIN
-- ---- Creating Dimension (CWM2_OLAP_DIMENSION) -------------------------
begin
cwm2_olap_dimension.drop_dimension(user, 'SOLVED_DIM');
exception when others then null;
end;
cwm2_olap_dimension.create_dimension(user, 'SOLVED_DIM', 'SOLVED_DIM disp', 'SOLVED_DIM pl', 'SOLVED_DIM short', 'SOLVED_DIM long');
-- ----- Completing Dimension Metadata (CWM2_OLAP_DIMENSION_ATTRIBUTE) ---
cwm2_olap_dimension_attribute.create_dimension_attribute(user, 'SOLVED_DIM', 'ID', 'ID', 'ID', 'ID');
cwm2_olap_dimension_attribute.create_dimension_attribute(user, 'SOLVED_DIM', 'ET key', 'ET key', 'ET key', 'ET key', true);
cwm2_olap_dimension_attribute.create_dimension_attribute(user, 'SOLVED_DIM', 'Parent ET key', 'Parent ET key', 'Parent ET key', 'Parent ET key', true);
cwm2_olap_dimension_attribute.create_dimension_attribute(user, 'SOLVED_DIM', 'Grouping ID', 'Grouping ID', 'Grouping ID', 'Grouping ID', true);
cwm2_olap_dimension_attribute.create_dimension_attribute(user, 'SOLVED_DIM', 'Parent Grouping ID', 'Parent Grouping ID', 'Parent Grouping ID', 'Parent Grouping ID', true);
cwm2_olap_dimension_attribute.create_dimension_attribute(user, 'SOLVED_DIM', 'Long Description', 'Long Description', 'Long Description', 'Long Description', true);
cwm2_olap_dimension_attribute.create_dimension_attribute(user, 'SOLVED_DIM', 'Short Description', 'Short Description', 'Short Description', 'Short Description', true);
-- ----- Completing Dimension Metadata (CWM2_OLAP_HIERARCHEY) ------------
cwm2_olap_hierarchy.create_hierarchy(user, 'SOLVED_DIM', 'SOLVED_DIM_HI', 'SOLVED_DIM_HI disp', 'SOLVED_DIM_HI short', 'SOLVED_DIM_HI long', 'SOLVED LEVEL-BASED');
cwm2_olap_dimension.set_default_display_hierarchy(user, 'SOLVED_DIM', 'SOLVED_DIM_HI');
-- ----- Completing Dimension Metadata (CWM2_OLAP_LEVEL) -----------------
cwm2_olap_level.create_level(user, 'SOLVED_DIM', 'OBJECT_NAME', 'OBJECT_NAME disp', 'OBJECT_NAME pl', 'OBJECT_NAME short', 'OBJECT_NAME long');
cwm2_olap_level.create_level(user, 'SOLVED_DIM', 'OBJECT_TYPE', 'OBJECT_TYPE disp', 'OBJECT_TYPE pl', 'OBJECT_TYPE short', 'OBJECT_TYPE long');
cwm2_olap_level.create_level(user, 'SOLVED_DIM', 'OWNER' ,'OWNER disp',      'OWNER pl', 'OWNER short', 'OWNER long');
cwm2_olap_level.create_level(user, 'SOLVED_DIM', 'TOP', 'TOP disp',           'TOP pl', 'TOP short', 'TOP long');
-- ----- Completing Dimension Metadata (CWM2_OLAP_LEVEL_ATTRIBUTE) -------
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'ID', 'OBJECT_NAME', 'ID', 'OBJECT_NAME_ID', 'OBJECT_NAME ID', 'ID');
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'ID', 'OBJECT_TYPE', 'ID', 'OBJECT_TYPE_ID', 'OBJECT_TYPE ID', 'ID');
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'ID', 'OWNER',      'ID', 'OWNER_ID', 'OWNER ID', 'ID');
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'ID', 'TOP', 'ID', 'TOP_ID', 'TOP ID', 'ID');
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'ET key', 'OBJECT_NAME', 'ET key', 'OBJECT_NAME_ET', 'OBJECT_NAME ET key', 'ET key', true);
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'Parent ET key', 'OBJECT_NAME', 'Parent ET key', 'OBJECT_NAME PARENT', 'OBJECT_NAME Parent ET key', 'Parent ET key', true);
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'Grouping ID', 'OBJECT_NAME', 'Grouping ID', 'OBJECT_NAME GID','OBJECT_NAME GID', 'Grouping ID', true);
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'Parent Grouping ID', 'OBJECT_NAME', 'Parent Grouping ID', 'OBJECT_NAME PGID', 'OBJECT_NAME Parent Grouping ID', 'Parent Grouping ID', true);
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'Long Description', 'OBJECT_NAME', 'Long Description', 'OBJECT_NAME LongDesc', 'OBJECT_NAME Long Desc', 'Long Description', true);
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'Short Description', 'OBJECT_NAME', 'Short Description', 'OBJECT_NAME ShortDesc', 'OBJECT_NAME Short Desc', 'Short Description', true);
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'ET key', 'OBJECT_TYPE', 'ET key', 'OBJECT_TYPE_ET', 'OBJECT_TYPE ET key', 'ET key', true);
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'Parent ET key', 'OBJECT_TYPE', 'Parent ET key', 'OBJECT_TYPE PARENT', 'OBJECT_TYPE Parent ET key', 'Parent ET key', true);
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'Grouping ID', 'OBJECT_TYPE', 'Grouping ID', 'OBJECT_TYPE GID','OBJECT_TYPE GID', 'Grouping ID', true);
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'Parent Grouping ID', 'OBJECT_TYPE', 'Parent Grouping ID', 'OBJECT_TYPE PGID', 'OBJECT_TYPE Parent Grouping ID', 'Parent Grouping ID', true);
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'Long Description', 'OBJECT_TYPE', 'Long Description', 'OBJECT_TYPE LongDesc', 'OBJECT_TYPE Long Desc', 'Long Description', true);
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'Short Description', 'OBJECT_TYPE', 'Short Description', 'OBJECT_TYPE ShortDesc', 'OBJECT_TYPE Short Desc', 'Short Description', true);
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'ET key', 'OWNER', 'ET key', 'OWNER_ET', 'OWNER ET key', 'ET key', true);
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'Parent ET key', 'OWNER', 'Parent ET key', 'OWNER PARENT', 'OWNER Parent ET key', 'Parent ET key', true);
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'Grouping ID', 'OWNER', 'Grouping ID', 'OWNER GID','OWNER GID', 'Grouping ID', true);
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'Parent Grouping ID', 'OWNER', 'Parent Grouping ID', 'OWNER PGID', 'OWNER Parent Grouping ID', 'Parent Grouping ID', true);
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'Long Description', 'OWNER', 'Long Description', 'OWNER LongDesc', 'OWNER Long Desc', 'Long Description', true);
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'Short Description', 'OWNER', 'Short Description', 'OWNER ShortDesc', 'OWNER Short Desc', 'Short Description', true);
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'ET key', 'TOP', 'ET key', 'TOP_ET', 'TOP ET key', 'ET key', true);
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'Parent ET key', 'TOP', 'Parent ET key', 'TOP PARENT', 'TOP Parent ET key', 'Parent ET key', true);
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'Grouping ID', 'TOP', 'Grouping ID', 'TOP GID','TOP GID', 'Grouping ID', true);
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'Parent Grouping ID', 'TOP', 'Parent Grouping ID', 'TOP PGID', 'TOP Parent Grouping ID', 'Parent Grouping ID', true);
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'Long Description', 'TOP', 'Long Description', 'TOP LongDesc', 'TOP Long Desc', 'Long Description', true);
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'Short Description', 'TOP', 'Short Description', 'TOP ShortDesc', 'TOP Short Desc', 'Short Description', true);
cwm2_olap_level.add_level_to_hierarchy(user, 'SOLVED_DIM', 'SOLVED_DIM_HI', 'OBJECT_NAME', 'OBJECT_TYPE');
cwm2_olap_level.add_level_to_hierarchy(user, 'SOLVED_DIM', 'SOLVED_DIM_HI', 'OBJECT_TYPE', 'OWNER');
cwm2_olap_level.add_level_to_hierarchy(user, 'SOLVED_DIM', 'SOLVED_DIM_HI', 'OWNER',          'TOP');
cwm2_olap_level.add_level_to_hierarchy(user, 'SOLVED_DIM', 'SOLVED_DIM_HI', 'TOP');
-- + Mapping Dimensions +
cwm2_olap_table_map.map_dimtbl_hierlevel(user, 'SOLVED_DIM', 'SOLVED_DIM_HI', 'OBJECT_NAME', user, 'SOLVED_DIM', 'OBJECT_NAME', 'OBJECT_TYPE');
cwm2_olap_table_map.map_dimtbl_hierlevel(user, 'SOLVED_DIM', 'SOLVED_DIM_HI', 'OBJECT_TYPE', user, 'SOLVED_DIM', 'OBJECT_TYPE', 'OWNER');
cwm2_olap_table_map.map_dimtbl_hierlevel(user, 'SOLVED_DIM', 'SOLVED_DIM_HI', 'OWNER',           user, 'SOLVED_DIM', 'OWNER',     'TOP');
cwm2_olap_table_map.map_dimtbl_hierlevel(user, 'SOLVED_DIM', 'SOLVED_DIM_HI', 'TOP',           user, 'SOLVED_DIM', 'TOP');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'ID', 'SOLVED_DIM_HI', 'OBJECT_NAME', 'ID', user, 'SOLVED_DIM', 'OBJECT_NAME_ID');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'ET key', 'SOLVED_DIM_HI', 'OBJECT_NAME', 'ET key', user, 'SOLVED_DIM', 'ETKEY');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'Parent ET key', 'SOLVED_DIM_HI', 'OBJECT_NAME', 'Parent ET key', user, 'SOLVED_DIM', 'PARENT_ETKEY');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'Grouping ID', 'SOLVED_DIM_HI', 'OBJECT_NAME', 'Grouping ID', user, 'SOLVED_DIM', 'GID');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'Parent Grouping ID', 'SOLVED_DIM_HI', 'OBJECT_NAME', 'Parent Grouping ID', user, 'SOLVED_DIM', 'PARENT_GID');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'Long Description', 'SOLVED_DIM_HI', 'OBJECT_NAME', 'Long Description', user, 'SOLVED_DIM', 'LONG_DESCRIPTION');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'Short Description', 'SOLVED_DIM_HI', 'OBJECT_NAME', 'Short Description', user, 'SOLVED_DIM', 'SHORT_DESCRIPTION');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'ID', 'SOLVED_DIM_HI', 'OBJECT_TYPE', 'ID', user, 'SOLVED_DIM', 'OBJECT_TYPE_ID');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'ET key', 'SOLVED_DIM_HI', 'OBJECT_TYPE', 'ET key', user, 'SOLVED_DIM', 'ETKEY');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'Parent ET key', 'SOLVED_DIM_HI', 'OBJECT_TYPE', 'Parent ET key', user, 'SOLVED_DIM', 'PARENT_ETKEY');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'Grouping ID', 'SOLVED_DIM_HI', 'OBJECT_TYPE', 'Grouping ID', user, 'SOLVED_DIM', 'GID');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'Parent Grouping ID', 'SOLVED_DIM_HI', 'OBJECT_TYPE', 'Parent Grouping ID', user, 'SOLVED_DIM', 'PARENT_GID');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'Long Description', 'SOLVED_DIM_HI', 'OBJECT_TYPE', 'Long Description', user, 'SOLVED_DIM', 'LONG_DESCRIPTION');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'Short Description', 'SOLVED_DIM_HI', 'OBJECT_TYPE', 'Short Description', user, 'SOLVED_DIM', 'SHORT_DESCRIPTION');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'ID', 'SOLVED_DIM_HI', 'OWNER', 'ID', user, 'SOLVED_DIM', 'OWNER_ID');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'ET key', 'SOLVED_DIM_HI', 'OWNER', 'ET key', user, 'SOLVED_DIM', 'ETKEY');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'Parent ET key', 'SOLVED_DIM_HI', 'OWNER', 'Parent ET key', user, 'SOLVED_DIM', 'PARENT_ETKEY');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'Grouping ID', 'SOLVED_DIM_HI', 'OWNER', 'Grouping ID', user, 'SOLVED_DIM', 'GID');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'Parent Grouping ID', 'SOLVED_DIM_HI', 'OWNER', 'Parent Grouping ID', user, 'SOLVED_DIM', 'PARENT_GID');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'Long Description', 'SOLVED_DIM_HI', 'OWNER', 'Long Description', user, 'SOLVED_DIM', 'LONG_DESCRIPTION');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'Short Description', 'SOLVED_DIM_HI', 'OWNER', 'Short Description', user, 'SOLVED_DIM', 'SHORT_DESCRIPTION');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'ID', 'SOLVED_DIM_HI', 'TOP', 'ID', user, 'SOLVED_DIM', 'TOP_ID');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'ET key', 'SOLVED_DIM_HI', 'TOP', 'ET key', user, 'SOLVED_DIM', 'ETKEY');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'Parent ET key', 'SOLVED_DIM_HI', 'TOP', 'Parent ET key', user, 'SOLVED_DIM', 'PARENT_ETKEY');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'Grouping ID', 'SOLVED_DIM_HI', 'TOP', 'Grouping ID', user, 'SOLVED_DIM', 'GID');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'Parent Grouping ID', 'SOLVED_DIM_HI', 'TOP', 'Parent Grouping ID', user, 'SOLVED_DIM', 'PARENT_GID');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'Long Description', 'SOLVED_DIM_HI', 'TOP', 'Long Description', user, 'SOLVED_DIM', 'LONG_DESCRIPTION');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'Short Description', 'SOLVED_DIM_HI', 'TOP', 'Short Description', user, 'SOLVED_DIM', 'SHORT_DESCRIPTION');
-- + Validate and Refresh +
cwm2_olap_validate.validate_dimension(user, 'SOLVED_DIM');
cwm2_olap_metadata_refresh.mr_refresh;
END;
The first dataset works perfectly. But not the second one... There are some intersections at OBJECT_TYPE level.
TOP->OLAP_USR->DIMENSION->OUD1
and
TOP->SH->DIMENSION->OUD2.
When I'm watching TOP->OLAP_USR->DIMENSION->OUD1, I not only open OUD1, but OUD2 under SH (even skipping OBJECT_TYPE level). It's simple to do it for USOLVED LEVEL-BASED by assigning different Id for the same OBJECT_TYPES from different owners. But it looks like my ids are ignored for Solved hierarchy.
Does anybody knows how to handle such situation?

I'm trying to make a dimension with SOLVED LEVEL-BASED hierarchy (Oracle 10.2.0.1).
Hierarchy is folowing:
TOP
|_OWNER
|_OBJECT_TYPE
|_OBJECT_NAME
Script
DROP TABLE SOLVED_DIM;
CREATE TABLE SOLVED_DIM
GID NUMBER,
ETKEY VARCHAR2(100),
PARENT_GID NUMBER,
PARENT_ETKEY VARCHAR2(100),
SHORT_DESCRIPTION VARCHAR2(100),
LONG_DESCRIPTION VARCHAR2(100),
TOP                    VARCHAR2(100),
OWNER VARCHAR2(100),
OBJECT_TYPE VARCHAR2(100),
OBJECT_NAME VARCHAR2(100) ,
TOP_ID NUMBER,
OWNER_ID NUMBER,
OBJECT_TYPE_ID NUMBER,
OBJECT_NAME_ID NUMBER,
ID NUMBER
--Test dataset №1
INSERT INTO SOLVED_DIM VALUES (7, 'TOP', NULL, NULL, 'TOP', 'TOP', 'TOP', NULL, NULL, NULL, 1, NULL, NULL, NULL, 100001);
INSERT INTO SOLVED_DIM VALUES (3, 'SH', 7, 'TOP', 'SH', 'SH', 'TOP', 'SH', NULL, NULL, 1, 11, NULL, NULL, 100002);
INSERT INTO SOLVED_DIM VALUES (3, 'OLAP_USR', 7, 'TOP', 'OLAP_USR', 'OLAP_USR', 'TOP', 'OLAP_USR', NULL, NULL, 1, 12, NULL, NULL, 100003);
INSERT INTO SOLVED_DIM VALUES (1, 'SDIMENSION', 3, 'SH', 'SDIMENSION', 'SDIMENSION', 'TOP', 'SH', 'SDIMENSION', NULL, 1, 11, 111, NULL, 100004);
INSERT INTO SOLVED_DIM VALUES (1, 'ODIMENSION', 3, 'OLAP_USR', 'ODIMENSION', 'ODIMENSION', 'TOP', 'OLAP_USR', 'ODIMENSION', NULL, 1, 12, 121, NULL, 100005);
INSERT INTO SOLVED_DIM VALUES (0, 'OUD1', 1, 'ODIMENSION', 'OUD1', 'OUD1', 'TOP', 'OLAP_USR', 'ODIMENSION', 'OUD1', 1, 12, 121, 1211, 100006);
INSERT INTO SOLVED_DIM VALUES (0, 'OUD2', 1, 'SDIMENSION', 'OUD2', 'OUD2', 'TOP', 'SH', 'SDIMENSION', 'OUD2', 1, 11, 111, 1111, 100007);
commit;
--Test dataset №2
INSERT INTO SOLVED_DIM VALUES (7, 'TOP', NULL, NULL, 'TOP', 'TOP', 'TOP', NULL, NULL, NULL, 1, NULL, NULL, NULL, 100001);
INSERT INTO SOLVED_DIM VALUES (3, 'SH', 7, 'TOP', 'SH', 'SH', 'TOP', 'SH', NULL, NULL, 1, 11, NULL, NULL, 100002);
INSERT INTO SOLVED_DIM VALUES (3, 'OLAP_USR', 7, 'TOP', 'OLAP_USR', 'OLAP_USR', 'TOP', 'OLAP_USR', NULL, NULL, 1, 12, NULL, NULL, 100003);
INSERT INTO SOLVED_DIM VALUES (1, 'DIMENSION', 3, 'SH', 'DIMENSION', 'DIMENSION', 'TOP', 'SH', 'DIMENSION', NULL, 1, 11, 111, NULL, 100004);
INSERT INTO SOLVED_DIM VALUES (1, 'DIMENSION', 3, 'OLAP_USR', 'DIMENSION', 'DIMENSION', 'TOP', 'OLAP_USR', 'DIMENSION', NULL, 1, 12, 121, NULL, 100005);
INSERT INTO SOLVED_DIM VALUES (0, 'OUD1', 1, 'DIMENSION', 'OUD1', 'OUD1', 'TOP', 'OLAP_USR', 'DIMENSION', 'OUD1', 1, 12, 121, 1211, 100006);
INSERT INTO SOLVED_DIM VALUES (0, 'OUD2', 1, 'DIMENSION', 'OUD2', 'OUD2', 'TOP', 'SH', 'DIMENSION', 'OUD2', 1, 11, 111, 1111, 100007);
commit;
BEGIN
-- ---- Creating Dimension (CWM2_OLAP_DIMENSION) -------------------------
begin
cwm2_olap_dimension.drop_dimension(user, 'SOLVED_DIM');
exception when others then null;
end;
cwm2_olap_dimension.create_dimension(user, 'SOLVED_DIM', 'SOLVED_DIM disp', 'SOLVED_DIM pl', 'SOLVED_DIM short', 'SOLVED_DIM long');
-- ----- Completing Dimension Metadata (CWM2_OLAP_DIMENSION_ATTRIBUTE) ---
cwm2_olap_dimension_attribute.create_dimension_attribute(user, 'SOLVED_DIM', 'ID', 'ID', 'ID', 'ID');
cwm2_olap_dimension_attribute.create_dimension_attribute(user, 'SOLVED_DIM', 'ET key', 'ET key', 'ET key', 'ET key', true);
cwm2_olap_dimension_attribute.create_dimension_attribute(user, 'SOLVED_DIM', 'Parent ET key', 'Parent ET key', 'Parent ET key', 'Parent ET key', true);
cwm2_olap_dimension_attribute.create_dimension_attribute(user, 'SOLVED_DIM', 'Grouping ID', 'Grouping ID', 'Grouping ID', 'Grouping ID', true);
cwm2_olap_dimension_attribute.create_dimension_attribute(user, 'SOLVED_DIM', 'Parent Grouping ID', 'Parent Grouping ID', 'Parent Grouping ID', 'Parent Grouping ID', true);
cwm2_olap_dimension_attribute.create_dimension_attribute(user, 'SOLVED_DIM', 'Long Description', 'Long Description', 'Long Description', 'Long Description', true);
cwm2_olap_dimension_attribute.create_dimension_attribute(user, 'SOLVED_DIM', 'Short Description', 'Short Description', 'Short Description', 'Short Description', true);
-- ----- Completing Dimension Metadata (CWM2_OLAP_HIERARCHEY) ------------
cwm2_olap_hierarchy.create_hierarchy(user, 'SOLVED_DIM', 'SOLVED_DIM_HI', 'SOLVED_DIM_HI disp', 'SOLVED_DIM_HI short', 'SOLVED_DIM_HI long', 'SOLVED LEVEL-BASED');
cwm2_olap_dimension.set_default_display_hierarchy(user, 'SOLVED_DIM', 'SOLVED_DIM_HI');
-- ----- Completing Dimension Metadata (CWM2_OLAP_LEVEL) -----------------
cwm2_olap_level.create_level(user, 'SOLVED_DIM', 'OBJECT_NAME', 'OBJECT_NAME disp', 'OBJECT_NAME pl', 'OBJECT_NAME short', 'OBJECT_NAME long');
cwm2_olap_level.create_level(user, 'SOLVED_DIM', 'OBJECT_TYPE', 'OBJECT_TYPE disp', 'OBJECT_TYPE pl', 'OBJECT_TYPE short', 'OBJECT_TYPE long');
cwm2_olap_level.create_level(user, 'SOLVED_DIM', 'OWNER' ,'OWNER disp',      'OWNER pl', 'OWNER short', 'OWNER long');
cwm2_olap_level.create_level(user, 'SOLVED_DIM', 'TOP', 'TOP disp',           'TOP pl', 'TOP short', 'TOP long');
-- ----- Completing Dimension Metadata (CWM2_OLAP_LEVEL_ATTRIBUTE) -------
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'ID', 'OBJECT_NAME', 'ID', 'OBJECT_NAME_ID', 'OBJECT_NAME ID', 'ID');
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'ID', 'OBJECT_TYPE', 'ID', 'OBJECT_TYPE_ID', 'OBJECT_TYPE ID', 'ID');
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'ID', 'OWNER',      'ID', 'OWNER_ID', 'OWNER ID', 'ID');
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'ID', 'TOP', 'ID', 'TOP_ID', 'TOP ID', 'ID');
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'ET key', 'OBJECT_NAME', 'ET key', 'OBJECT_NAME_ET', 'OBJECT_NAME ET key', 'ET key', true);
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'Parent ET key', 'OBJECT_NAME', 'Parent ET key', 'OBJECT_NAME PARENT', 'OBJECT_NAME Parent ET key', 'Parent ET key', true);
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'Grouping ID', 'OBJECT_NAME', 'Grouping ID', 'OBJECT_NAME GID','OBJECT_NAME GID', 'Grouping ID', true);
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'Parent Grouping ID', 'OBJECT_NAME', 'Parent Grouping ID', 'OBJECT_NAME PGID', 'OBJECT_NAME Parent Grouping ID', 'Parent Grouping ID', true);
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'Long Description', 'OBJECT_NAME', 'Long Description', 'OBJECT_NAME LongDesc', 'OBJECT_NAME Long Desc', 'Long Description', true);
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'Short Description', 'OBJECT_NAME', 'Short Description', 'OBJECT_NAME ShortDesc', 'OBJECT_NAME Short Desc', 'Short Description', true);
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'ET key', 'OBJECT_TYPE', 'ET key', 'OBJECT_TYPE_ET', 'OBJECT_TYPE ET key', 'ET key', true);
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'Parent ET key', 'OBJECT_TYPE', 'Parent ET key', 'OBJECT_TYPE PARENT', 'OBJECT_TYPE Parent ET key', 'Parent ET key', true);
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'Grouping ID', 'OBJECT_TYPE', 'Grouping ID', 'OBJECT_TYPE GID','OBJECT_TYPE GID', 'Grouping ID', true);
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'Parent Grouping ID', 'OBJECT_TYPE', 'Parent Grouping ID', 'OBJECT_TYPE PGID', 'OBJECT_TYPE Parent Grouping ID', 'Parent Grouping ID', true);
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'Long Description', 'OBJECT_TYPE', 'Long Description', 'OBJECT_TYPE LongDesc', 'OBJECT_TYPE Long Desc', 'Long Description', true);
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'Short Description', 'OBJECT_TYPE', 'Short Description', 'OBJECT_TYPE ShortDesc', 'OBJECT_TYPE Short Desc', 'Short Description', true);
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'ET key', 'OWNER', 'ET key', 'OWNER_ET', 'OWNER ET key', 'ET key', true);
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'Parent ET key', 'OWNER', 'Parent ET key', 'OWNER PARENT', 'OWNER Parent ET key', 'Parent ET key', true);
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'Grouping ID', 'OWNER', 'Grouping ID', 'OWNER GID','OWNER GID', 'Grouping ID', true);
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'Parent Grouping ID', 'OWNER', 'Parent Grouping ID', 'OWNER PGID', 'OWNER Parent Grouping ID', 'Parent Grouping ID', true);
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'Long Description', 'OWNER', 'Long Description', 'OWNER LongDesc', 'OWNER Long Desc', 'Long Description', true);
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'Short Description', 'OWNER', 'Short Description', 'OWNER ShortDesc', 'OWNER Short Desc', 'Short Description', true);
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'ET key', 'TOP', 'ET key', 'TOP_ET', 'TOP ET key', 'ET key', true);
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'Parent ET key', 'TOP', 'Parent ET key', 'TOP PARENT', 'TOP Parent ET key', 'Parent ET key', true);
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'Grouping ID', 'TOP', 'Grouping ID', 'TOP GID','TOP GID', 'Grouping ID', true);
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'Parent Grouping ID', 'TOP', 'Parent Grouping ID', 'TOP PGID', 'TOP Parent Grouping ID', 'Parent Grouping ID', true);
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'Long Description', 'TOP', 'Long Description', 'TOP LongDesc', 'TOP Long Desc', 'Long Description', true);
cwm2_olap_level_attribute.create_level_attribute(user, 'SOLVED_DIM', 'Short Description', 'TOP', 'Short Description', 'TOP ShortDesc', 'TOP Short Desc', 'Short Description', true);
cwm2_olap_level.add_level_to_hierarchy(user, 'SOLVED_DIM', 'SOLVED_DIM_HI', 'OBJECT_NAME', 'OBJECT_TYPE');
cwm2_olap_level.add_level_to_hierarchy(user, 'SOLVED_DIM', 'SOLVED_DIM_HI', 'OBJECT_TYPE', 'OWNER');
cwm2_olap_level.add_level_to_hierarchy(user, 'SOLVED_DIM', 'SOLVED_DIM_HI', 'OWNER',          'TOP');
cwm2_olap_level.add_level_to_hierarchy(user, 'SOLVED_DIM', 'SOLVED_DIM_HI', 'TOP');
-- + Mapping Dimensions +
cwm2_olap_table_map.map_dimtbl_hierlevel(user, 'SOLVED_DIM', 'SOLVED_DIM_HI', 'OBJECT_NAME', user, 'SOLVED_DIM', 'OBJECT_NAME', 'OBJECT_TYPE');
cwm2_olap_table_map.map_dimtbl_hierlevel(user, 'SOLVED_DIM', 'SOLVED_DIM_HI', 'OBJECT_TYPE', user, 'SOLVED_DIM', 'OBJECT_TYPE', 'OWNER');
cwm2_olap_table_map.map_dimtbl_hierlevel(user, 'SOLVED_DIM', 'SOLVED_DIM_HI', 'OWNER',           user, 'SOLVED_DIM', 'OWNER',     'TOP');
cwm2_olap_table_map.map_dimtbl_hierlevel(user, 'SOLVED_DIM', 'SOLVED_DIM_HI', 'TOP',           user, 'SOLVED_DIM', 'TOP');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'ID', 'SOLVED_DIM_HI', 'OBJECT_NAME', 'ID', user, 'SOLVED_DIM', 'OBJECT_NAME_ID');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'ET key', 'SOLVED_DIM_HI', 'OBJECT_NAME', 'ET key', user, 'SOLVED_DIM', 'ETKEY');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'Parent ET key', 'SOLVED_DIM_HI', 'OBJECT_NAME', 'Parent ET key', user, 'SOLVED_DIM', 'PARENT_ETKEY');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'Grouping ID', 'SOLVED_DIM_HI', 'OBJECT_NAME', 'Grouping ID', user, 'SOLVED_DIM', 'GID');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'Parent Grouping ID', 'SOLVED_DIM_HI', 'OBJECT_NAME', 'Parent Grouping ID', user, 'SOLVED_DIM', 'PARENT_GID');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'Long Description', 'SOLVED_DIM_HI', 'OBJECT_NAME', 'Long Description', user, 'SOLVED_DIM', 'LONG_DESCRIPTION');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'Short Description', 'SOLVED_DIM_HI', 'OBJECT_NAME', 'Short Description', user, 'SOLVED_DIM', 'SHORT_DESCRIPTION');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'ID', 'SOLVED_DIM_HI', 'OBJECT_TYPE', 'ID', user, 'SOLVED_DIM', 'OBJECT_TYPE_ID');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'ET key', 'SOLVED_DIM_HI', 'OBJECT_TYPE', 'ET key', user, 'SOLVED_DIM', 'ETKEY');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'Parent ET key', 'SOLVED_DIM_HI', 'OBJECT_TYPE', 'Parent ET key', user, 'SOLVED_DIM', 'PARENT_ETKEY');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'Grouping ID', 'SOLVED_DIM_HI', 'OBJECT_TYPE', 'Grouping ID', user, 'SOLVED_DIM', 'GID');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'Parent Grouping ID', 'SOLVED_DIM_HI', 'OBJECT_TYPE', 'Parent Grouping ID', user, 'SOLVED_DIM', 'PARENT_GID');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'Long Description', 'SOLVED_DIM_HI', 'OBJECT_TYPE', 'Long Description', user, 'SOLVED_DIM', 'LONG_DESCRIPTION');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'Short Description', 'SOLVED_DIM_HI', 'OBJECT_TYPE', 'Short Description', user, 'SOLVED_DIM', 'SHORT_DESCRIPTION');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'ID', 'SOLVED_DIM_HI', 'OWNER', 'ID', user, 'SOLVED_DIM', 'OWNER_ID');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'ET key', 'SOLVED_DIM_HI', 'OWNER', 'ET key', user, 'SOLVED_DIM', 'ETKEY');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'Parent ET key', 'SOLVED_DIM_HI', 'OWNER', 'Parent ET key', user, 'SOLVED_DIM', 'PARENT_ETKEY');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'Grouping ID', 'SOLVED_DIM_HI', 'OWNER', 'Grouping ID', user, 'SOLVED_DIM', 'GID');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'Parent Grouping ID', 'SOLVED_DIM_HI', 'OWNER', 'Parent Grouping ID', user, 'SOLVED_DIM', 'PARENT_GID');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'Long Description', 'SOLVED_DIM_HI', 'OWNER', 'Long Description', user, 'SOLVED_DIM', 'LONG_DESCRIPTION');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'Short Description', 'SOLVED_DIM_HI', 'OWNER', 'Short Description', user, 'SOLVED_DIM', 'SHORT_DESCRIPTION');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'ID', 'SOLVED_DIM_HI', 'TOP', 'ID', user, 'SOLVED_DIM', 'TOP_ID');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'ET key', 'SOLVED_DIM_HI', 'TOP', 'ET key', user, 'SOLVED_DIM', 'ETKEY');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'Parent ET key', 'SOLVED_DIM_HI', 'TOP', 'Parent ET key', user, 'SOLVED_DIM', 'PARENT_ETKEY');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'Grouping ID', 'SOLVED_DIM_HI', 'TOP', 'Grouping ID', user, 'SOLVED_DIM', 'GID');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'Parent Grouping ID', 'SOLVED_DIM_HI', 'TOP', 'Parent Grouping ID', user, 'SOLVED_DIM', 'PARENT_GID');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'Long Description', 'SOLVED_DIM_HI', 'TOP', 'Long Description', user, 'SOLVED_DIM', 'LONG_DESCRIPTION');
cwm2_olap_table_map.map_dimtbl_hierlevelattr(user, 'SOLVED_DIM', 'Short Description', 'SOLVED_DIM_HI', 'TOP', 'Short Description', user, 'SOLVED_DIM', 'SHORT_DESCRIPTION');
-- + Validate and Refresh +
cwm2_olap_validate.validate_dimension(user, 'SOLVED_DIM');
cwm2_olap_metadata_refresh.mr_refresh;
END;
The first dataset works perfectly. But not the second one... There are some intersections at OBJECT_TYPE level.
TOP->OLAP_USR->DIMENSION->OUD1
and
TOP->SH->DIMENSION->OUD2.
When I'm watching TOP->OLAP_USR->DIMENSION->OUD1, I not only open OUD1, but OUD2 under SH (even skipping OBJECT_TYPE level). It's simple to do it for USOLVED LEVEL-BASED by assigning different Id for the same OBJECT_TYPES from different owners. But it looks like my ids are ignored for Solved hierarchy.
Does anybody knows how to handle such situation?

How to use Solve Order in Dimension level formula

Hi All,
Can anyone explain me how to use "Solve order" in formulas defined in dimension?
Regards,
Kapil

Hi,
Let us consider the following:
There are 3 members in your account dimension, Amt, Rate, and Prod. The data looks like
               Jan     Feb     Mar     Apr     May
Amt        100     10       20       30       40
Rate       10       20       10       20       30
Prod       1000 200     200      600     1200
The above values of the Prod will be displayed if the measure in CV is set to periodic. However, if you change the measure in CV to YTD and change the time dimension to dec, then you should get the below result.
              Dec
Amt       200
Rate      90
Prod      3200
This value is nothing but the total of the entire year.
Hope this helps.

Error -23011 occurred at LabVIEW Analysis ODE Solver/inconsistency in dimensions of X(0), F and X!

Hi,
I have been trying to simulate ODE but getting following error:
Error -23011 occurred at LabVIEW Analysis ODE Solver/inconsistency in dimensions of X(0), F and X!.
The screenshot of the code is attached.
Please let me know if anyone knows the reason of having this error.
Thank you.
-HB
Solved!
Go to Solution.
Attachments:
Screen Shot 2014-12-02 at 09.58.08.png ‏60 KB

Hi,
I have added another code which includes the "simple chemical reaction" which I am trying to model using ODE in LabVIEW, but I am continously having the same problem.
Kindly see the attachment and try to help me out solving this issue. I couldn't found this kind of error listed on NI forum.
Thank you.
Regards
Hasan
Attachments:
test_hb.vi ‏22 KB

[SOLVED]HD Screen very high resolution dimension - small [BUG]

I got a new laptop and of course the first thing I must put on it it's Arch Linux.
It's an Asus N551 and EXTREAMLY WEIRD but everything went fine, I mean everything worked without me doing anything to fix up stuff (yes I had to install bumblebee) but everything, sound, touchpad, graphics, networking, etc just required installing the driver and that's it.
Now the problem is with the display,
xdpyinfo | grep -B2 resolution
screen #0:
dimensions: 1920x1080 pixels (508x285 millimeters)
resolution: 96x96 dots per inch
The resolution is as you see but everything else it's really small and I think I will become blind if I don't fix this.
I'm currently using the intel graphic card.
I read 2-3 topics similar to mine but without any understandble resolution and beeing very old I thought it's better to open a new one.
Thanks.
SOLUTION:
1) Find out your Screen ID (It should show "connected" and "allot of available displays")
]$ xrandr
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
eDP1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 345mm x 194mm
1920x1080 60.02*+
1400x1050 59.98
1280x1024 60.02
1280x960 60.00
1024x768 60.00
800x600 60.32 56.25
640x480 59.94
DP1 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
So Mine is eDP1
2) Find your screen size in mm
In my case intel and xdpyinfo reported the wrong value, so the right one for me was 345x194 mm
3) Find out your right DPI settings
http://dpi.lv will do this for you.
4) Apply what you found:
cat /etc/X11/xorg.conf.d/90-monitor.conf
Section "Monitor"
Identifier "eDP1"
DisplaySize 345 194
Option "DPI" "141 x 141"
EndSection
stop your DE and startx again
Confirm the settings were applied:
$ xdpyinfo | grep -B1 dot
dimensions: 1920x1080 pixels (345x194 millimeters)
resolution: 141x141 dots per inch
5) Use a DE which will not overwrite your DPI settings (So far , Gnome, Cinnamon, does it).
LXDE won't
xfce4 gives you an option to set your desired DPI so it's also OK.
6) Configure the browsers / or heavy applications NOT to ignore the system DPI settings.
(this is also a looong trail to deal with)....
BUG: https://bugs.freedesktop.org/show_bug.cgi?id=89820
Last edited by r0b0t (2015-03-30 11:25:42)

1- Done
$ cat /etc/X11/xorg.conf.d/90-monitor.conf
Section "Monitor"
Identifier "eDP1"
DisplaySize 345 194
Option "DPI" "141 x 141"
EndSection
And confirmed by xdpyinfo
2)LXDE it is
xfce4 also work if I manually set the dpi to 141 (it supports it).
It's working now.
Will try configure "dpi-resistent" applications.
I will mark the thread as solved but should I open a bug for intel setting
1) Wrong dimension
2) Wrong DPI
This is what's happening: (vanilla configuration , no xorg.conf stuff, no xinitrc)
[ 818.088] (II) intel(0): Using Kernel Mode Setting driver: i915, version 1.6.0 20141121
[ 818.089] (WW) Falling back to old probe method for modesetting
[ 818.089] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[ 818.089] (--) intel(0): Integrated Graphics Chipset: Intel(R) HD Graphics 4600
------------------------ SETTING DPI WRONGLY---------------------------------------------
[ 818.089] (--) intel(0): Output eDP1 using initial mode 1920x1080 on pipe 0
[ 818.089] (==) intel(0): TearFree disabled
[ 818.089] (==) intel(0): DPI set to (96, 96)
[ 818.090] (II) intel(0): SNA initialized with Haswell (gen7.5, gt2) backend
[ 818.090] (==) intel(0): Backing store enabled
[ 818.090] (==) intel(0): Silken mouse enabled
[ 818.090] (II) intel(0): HW Cursor enabled
[ 818.090] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message. >>>>>>>>>> WHY SHOULD I IGNORE??<<<<<<<<
[ 818.090] (==) intel(0): DPMS enabled
[ 818.090] (==) intel(0): display hotplug detection enabled
[ 818.090] (II) intel(0): [DRI2] Setup complete
[ 818.090] (II) intel(0): [DRI2] DRI driver: i965
[ 818.090] (II) intel(0): [DRI2] VDPAU driver: i965
[ 818.090] (II) intel(0): direct rendering: DRI2 enabled
[ 818.090] (II) intel(0): hardware support for Present enabled
[ 818.090] (--) RandR disabled
[ 818.107] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 818.107] (II) AIGLX: enabled GLX_ARB_create_context
[ 818.107] (II) AIGLX: enabled GLX_ARB_create_context_profile
[ 818.107] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
[ 818.107] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 818.107] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
[ 818.107] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
[ 818.107] (II) AIGLX: enabled GLX_ARB_fbconfig_float
[ 818.107] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[ 818.107] (II) AIGLX: enabled GLX_ARB_create_context_robustness
[ 818.107] (II) AIGLX: Loaded and initialized i965
[ 818.107] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 818.109] (II) intel(0): switch to mode [email protected] on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none
[ 818.122] (II) intel(0): Setting screen physical size to 508 x 285 >>>>>>>>>>>>>>>>> WRONG IT'S 345x194mm<<<<<<<<<<<<<<<<<<<<

[solved] screen dimensions & xorg config

I've been trying (finally) to improve the appearance of fonts in my system. In the process of following the wiki font configuration guide, I checked out the dpi/screen dimensions identified by xorg. According to my calculations, xorg is getting the physical dimensions of my laptop's display wrong. It correctly identifies the native resolution as 1366x768 and then uses a dpi of 96 to calculate physical dimensions:
$ xdpyinfo | grep -B2 reso
screen #0:
dimensions: 1366x768 pixels (361x203 millimeters)
resolution: 96x96 dots per inch
However, my laptop screen is 11.6" which I think is about 256.8x144.4 mm with a dpi of 136x135. Er... ish.
Trying to follow the wiki instructions for configuring xorg at https://wiki.archlinux.org/index.php/Xo … ze_and_DPI, I created a /etc/X11/xorg.conf.d/20-monitors.conf:
Section "Monitor"
Identifier "LVDS1"
DisplaySize 256.8 144.4 # In millimeters
EndSection
However, this produces pretty ugly results. Fonts look all wrong - at least in some applications - and things just generally seem too big. So I removed the config file and rebooted and everything looks OK again (actually a bit better than before - probably because I'd got through part of the font config guide). I have no non-default config files under /etc/X11/xorg.conf.d/ - just default files for evdev, quirks and synaptics.
So now I'm confused about what dimensions I should be using.
I would have thought that with the autogenerated settings above, I should find things not fitting onto the screen because X believes that the physical screen is larger than it really is. But that's not what happens. Everything fits fine. Plus I'm not sure how to check but the resolution looks comparable to the resolution I get in the ttys.
I'm using the intel i915 driver with various power-saving options (which don't affect display so far as I can tell). It's one of the integrated graphics chips. There's no separate graphics card to complicate (or improve!) things.
Could somebody explain what might be going on? Or give me a reference? I don't understand how the physical dimensions X uses can be incorrect and yet everything fit and look better than when I force it to use accurate ones.
Last edited by cfr (2012-03-06 18:31:35)

High resolution in the TTY means that you have KMS activated, which is a good thing.
Of course anything bigger than 96x96 or 100x100 DPI is going to look awkward, it's an 11.6 inch screen! Or did you actually try to bring a ruler to the screen and measure a 136x136 pixel image? There's this little thing called dot (pixel) pitch: 0.39, 0.33, 0.28, 0.265 mm, etc.
http://en.wikipedia.org/wiki/Dots_per_i … _standards
Obviously Microsoft's sneaky little hack had very long-term consequences, when instead they should've just used a better rendering method. "However, larger graphical elements meant less screen space on which to draw" - which is what you experienced when everything looked like it was on steroids.
Another very interesting article: http://www.tested.com/news/why-pixel-de … ution/371/

Query time affected when using dimensions that are at a lower grain

Hi all,
I have a product dimension that has one hierarchy and 7 levels: All Product -> Category -> BU -> Class -> Department -> SubDept -> Item. The lowest level has about 8 million members. The Department level has about 1500 members
Some of my Cubes are actually mapped to fact tables where the grain is at Department level. So I've ensured that in the Cube Mappings Editor, the Department Id of the fact table is mapped to the Department level of the Product Dimension, and I can actually see in the Cube's Aggmap, it is using LOAD_STATUS to limit the Product dimension to the Department level members for the aggregation.
Querying the Cube using SQL brings back the correct result across different level combination, however the query constantly takes about 2 - 3 mins to complete.
As a test, I've built another dimension that goes down to the Department level only, and issue the same query against the Cube. The difference is significant as the query takes roughly less than 1 second to complete, and returns exactly the same result.
Any idea? I am using AWM 11.2.0.1.0A
Thanks

The stats you posted are puzzling. Usually the sum of loop and fetch time is close to the total time, but there is a big missing chunk of time in your case. It is clearly related to the calculated measures, since removing them solves the problem.
The most common problem with calculated measures is that they can cause the cube to loop densely (i.e. all logical member combinations) instead of sparsely (i.e. only the member combinations that have data). But I don't think this is the problem in your case since the difference between rows_read and rows_returned is small
ROWS_READ 212ROWS_RETURNED 185
NULLTRACK_SUPPRESSED 27>
If dense looping has happened then the rows_read is often orders of magnitude greater than rows_returned. You can see the looping strategy by running
select value || ' : ' || details as loop from cube_operations_log where name = 'LOOP_OPTIMIZED'Here is an example of the output for a good (sparse) loop.
LOOP
ON : LOOP AGGMAP(PRICE_COST_CUBE_SOLVE_AGGMAP PRICE_COST_CUBE_PRT_TEMPLATE)Here is the output if I add a year to date calc to the cube.
LOOP
ON : LOOP UNION(AGGMAP(PRICE_COST_CUBE_SOLVE_AGGMAP PRICE_COST_CUBE_PRT_TEMPLATE
) AGGMAP(DENSE(TIME) PRICE_COST_CUBE_SOLVE_AGGMAP PRICE_COST_CUBE_PRT_TEMPLATE))Note that TIME is now looped densely, but the code is still trying to loop the other dimensions sparsely. Finally, here is the loop if I add a random olap dml calculation to the cube.
LOOP
DISABLED :There is now no optimized looping and the cube will be looped densely.
So it may be worth checking the loop descriptor for your fast and slow cases, but my best guess at the moment is that the performance gap has something to do with your specific calculations. If I were you I would add them back one at a time to see if you can find a particular measure, or type of measure, that is causing the slowdown.

Error while creating a new Dimension/Model in BPC 10.0 NW

Hello Experts,
I am using BPC 10.0 NW system.
When I try to create new Dimensions or Models I get the following Error Message.
"Error in Admin module or a component used by Admin module.
Failed to create SAP NetWeaver BI InfoObject for dimension."
I am assigned to all the needed task profiles to create Dimensions and Models.
Please assist me to resolve this issue.
Thanks & Regards,
Archana

Thanks Roberto.
The error was coming because while creating the user id "SAP_ALL" Profile was not assigned. So I was not able to create Dimensions and models.
Now the issue is solved.

[Solved]Synaptics Touchpad not working at all on Fujitsu Siemens UH552

Hi,
I have just installed Arch on my Fujitsu Siemens UH552 laptop. Everything works except for the touchpad which seems to get loaded by Xorg, but when in X it doesn't work. I have tried both using /dev/input/event* and /dev/input/mouse0 as device paths, neither works.
xf86-input-evdev and xf86-input-synaptics are installed.
I have tried running both with the default 10-evdev.conf, with 10-synaptics.conf, with both, and without both.
TLDR SOLUTION: https://bbs.archlinux.org/viewtopic.php … 3#p1189603
My current 10-synaptics.conf:
Section "InputClass"
Identifier "Touchpad Catchall"
MatchIsTouchpad "on"
MatchDevicePath "/dev/input/event*"
Driver "synaptics"
Option "TapButton1" "1"
Option "TapButton2" "2"
Option "TapButton3" "3"
EndSection
Xorg.0.log
[ 2275.127]
X.Org X Server 1.12.4
Release Date: 2012-08-27
[ 2275.130] X Protocol Version 11, Revision 0
[ 2275.131] Build Operating System: Linux 3.4.8-1-ARCH x86_64
[ 2275.132] Current Operating System: Linux corvo 3.5.3-1-ARCH #1 SMP PREEMPT Sun Aug 26 09:14:51 CEST 2012 x86_64
[ 2275.132] Kernel command line: root=/dev/sda2 rootflags=subvol=__active ro initrd=/boot/initramfs-linux.img BOOT_IMAGE=/boot/vmlinuz-linux
[ 2275.134] Build Date: 27 August 2012 08:04:39AM
[ 2275.135]
[ 2275.136] Current version of pixman: 0.26.2
[ 2275.138] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 2275.138] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 2275.142] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Sep 1 13:16:01 2012
[ 2275.143] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 2275.144] (==) No Layout section. Using the first Screen section.
[ 2275.144] (==) No screen section available. Using defaults.
[ 2275.144] (**) |-->Screen "Default Screen Section" (0)
[ 2275.144] (**) | |-->Monitor "<default monitor>"
[ 2275.144] (==) No device specified for screen "Default Screen Section".
Using the first device section listed.
[ 2275.144] (**) | |-->Device "Intel Graphics"
[ 2275.144] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 2275.144] (==) Automatically adding devices
[ 2275.144] (==) Automatically enabling devices
[ 2275.144] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 2275.144] Entry deleted from font path.
[ 2275.144] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 2275.144] Entry deleted from font path.
[ 2275.144] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 2275.144] Entry deleted from font path.
[ 2275.144] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 2275.144] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 2275.144] Entry deleted from font path.
[ 2275.144] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 2275.144] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/
[ 2275.144] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 2275.144] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 2275.144] (II) Loader magic: 0x7c8b00
[ 2275.144] (II) Module ABI versions:
[ 2275.144] X.Org ANSI C Emulation: 0.4
[ 2275.144] X.Org Video Driver: 12.1
[ 2275.144] X.Org XInput driver : 16.0
[ 2275.144] X.Org Server Extension : 6.0
[ 2275.144] (--) PCI:*(0:0:2:0) 8086:0166:10cf:16c2 rev 9, Mem @ 0xf0000000/4194304, 0xe0000000/268435456, I/O @ 0x00002000/64
[ 2275.144] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 2275.144] (II) LoadModule: "extmod"
[ 2275.144] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
[ 2275.145] (II) Module extmod: vendor="X.Org Foundation"
[ 2275.145] compiled for 1.12.4, module version = 1.0.0
[ 2275.145] Module class: X.Org Server Extension
[ 2275.145] ABI class: X.Org Server Extension, version 6.0
[ 2275.145] (II) Loading extension MIT-SCREEN-SAVER
[ 2275.145] (II) Loading extension XFree86-VidModeExtension
[ 2275.145] (II) Loading extension XFree86-DGA
[ 2275.145] (II) Loading extension DPMS
[ 2275.145] (II) Loading extension XVideo
[ 2275.145] (II) Loading extension XVideo-MotionCompensation
[ 2275.145] (II) Loading extension X-Resource
[ 2275.145] (II) LoadModule: "dbe"
[ 2275.145] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
[ 2275.145] (II) Module dbe: vendor="X.Org Foundation"
[ 2275.145] compiled for 1.12.4, module version = 1.0.0
[ 2275.145] Module class: X.Org Server Extension
[ 2275.145] ABI class: X.Org Server Extension, version 6.0
[ 2275.145] (II) Loading extension DOUBLE-BUFFER
[ 2275.145] (II) LoadModule: "glx"
[ 2275.145] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 2275.145] (II) Module glx: vendor="X.Org Foundation"
[ 2275.145] compiled for 1.12.4, module version = 1.0.0
[ 2275.145] ABI class: X.Org Server Extension, version 6.0
[ 2275.145] (==) AIGLX enabled
[ 2275.145] (II) Loading extension GLX
[ 2275.145] (II) LoadModule: "record"
[ 2275.145] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
[ 2275.145] (II) Module record: vendor="X.Org Foundation"
[ 2275.145] compiled for 1.12.4, module version = 1.13.0
[ 2275.145] Module class: X.Org Server Extension
[ 2275.145] ABI class: X.Org Server Extension, version 6.0
[ 2275.145] (II) Loading extension RECORD
[ 2275.145] (II) LoadModule: "dri"
[ 2275.145] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[ 2275.145] (II) Module dri: vendor="X.Org Foundation"
[ 2275.145] compiled for 1.12.4, module version = 1.0.0
[ 2275.145] ABI class: X.Org Server Extension, version 6.0
[ 2275.145] (II) Loading extension XFree86-DRI
[ 2275.145] (II) LoadModule: "dri2"
[ 2275.145] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 2275.145] (II) Module dri2: vendor="X.Org Foundation"
[ 2275.145] compiled for 1.12.4, module version = 1.2.0
[ 2275.145] ABI class: X.Org Server Extension, version 6.0
[ 2275.145] (II) Loading extension DRI2
[ 2275.145] (II) LoadModule: "intel"
[ 2275.146] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[ 2275.146] (II) Module intel: vendor="X.Org Foundation"
[ 2275.146] compiled for 1.12.3.901, module version = 2.20.5
[ 2275.146] Module class: X.Org Video Driver
[ 2275.146] ABI class: X.Org Video Driver, version 12.1
[ 2275.146] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G,
E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
4 Series, G45/G43, Q45/Q43, G41, B43, B43, Clarkdale, Arrandale,
Sandybridge Desktop (GT1), Sandybridge Desktop (GT2),
Sandybridge Desktop (GT2+), Sandybridge Mobile (GT1),
Sandybridge Mobile (GT2), Sandybridge Mobile (GT2+),
Sandybridge Server, Ivybridge Mobile (GT1), Ivybridge Mobile (GT2),
Ivybridge Desktop (GT1), Ivybridge Desktop (GT2), Ivybridge Server,
Ivybridge Server (GT2), Haswell Desktop (GT1), Haswell Desktop (GT2),
Haswell Desktop (GT2+), Haswell Mobile (GT1), Haswell Mobile (GT2),
Haswell Mobile (GT2+), Haswell Server (GT1), Haswell Server (GT2),
Haswell Server (GT2+), Haswell SDV Desktop (GT1),
Haswell SDV Desktop (GT2), Haswell SDV Desktop (GT2+),
Haswell SDV Mobile (GT1), Haswell SDV Mobile (GT2),
Haswell SDV Mobile (GT2+), Haswell SDV Server (GT1),
Haswell SDV Server (GT2), Haswell SDV Server (GT2+),
Haswell ULT Desktop (GT1), Haswell ULT Desktop (GT2),
Haswell ULT Desktop (GT2+), Haswell ULT Mobile (GT1),
Haswell ULT Mobile (GT2), Haswell ULT Mobile (GT2+),
Haswell ULT Server (GT1), Haswell ULT Server (GT2),
Haswell ULT Server (GT2+), Haswell CRW Desktop (GT1),
Haswell CRW Desktop (GT2), Haswell CRW Desktop (GT2+),
Haswell CRW Mobile (GT1), Haswell CRW Mobile (GT2),
Haswell CRW Mobile (GT2+), Haswell CRW Server (GT1),
Haswell CRW Server (GT2), Haswell CRW Server (GT2+)
[ 2275.146] (--) using VT number 7
[ 2275.149] drmOpenDevice: node name is /dev/dri/card0
[ 2275.149] drmOpenDevice: open result is 7, (OK)
[ 2275.150] drmOpenByBusid: Searching for BusID pci:0000:00:02.0
[ 2275.150] drmOpenDevice: node name is /dev/dri/card0
[ 2275.150] drmOpenDevice: open result is 7, (OK)
[ 2275.150] drmOpenByBusid: drmOpenMinor returns 7
[ 2275.150] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
[ 2275.150] drmOpenDevice: node name is /dev/dri/card0
[ 2275.150] drmOpenDevice: open result is 8, (OK)
[ 2275.150] drmOpenByBusid: Searching for BusID pci:0000:00:02.0
[ 2275.150] drmOpenDevice: node name is /dev/dri/card0
[ 2275.150] drmOpenDevice: open result is 8, (OK)
[ 2275.150] drmOpenByBusid: drmOpenMinor returns 8
[ 2275.150] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
[ 2275.150] (II) intel(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 2275.150] (==) intel(0): Depth 24, (--) framebuffer bpp 32
[ 2275.150] (==) intel(0): RGB weight 888
[ 2275.150] (==) intel(0): Default visual is TrueColor
[ 2275.150] (**) intel(0): Option "AccelMethod" "sna"
[ 2275.150] (--) intel(0): Integrated Graphics Chipset: Intel(R) Ivybridge Mobile (GT2)
[ 2275.151] (**) intel(0): Framebuffer tiled
[ 2275.151] (**) intel(0): Pixmaps tiled
[ 2275.151] (**) intel(0): 3D buffers tiled
[ 2275.151] (**) intel(0): Throttling enabled
[ 2275.151] (**) intel(0): Delayed flush enabled
[ 2275.151] (**) intel(0): "Tear free" disabled
[ 2275.151] (**) intel(0): Forcing per-crtc-pixmaps? no
[ 2275.151] (II) intel(0): Output LVDS1 has no monitor section
[ 2275.152] (II) intel(0): found backlight control interface acpi_video0 (type 'firmware')
[ 2275.152] (II) intel(0): Output VGA1 has no monitor section
[ 2275.153] (II) intel(0): Output HDMI1 has no monitor section
[ 2275.193] (II) intel(0): Output DP1 has no monitor section
[ 2275.193] (II) intel(0): EDID for output LVDS1
[ 2275.193] (II) intel(0): Manufacturer: LGD Model: 371 Serial#: 0
[ 2275.193] (II) intel(0): Year: 2012 Week: 0
[ 2275.193] (II) intel(0): EDID Version: 1.3
[ 2275.193] (II) intel(0): Digital Display Input
[ 2275.193] (II) intel(0): Max Image Size [cm]: horiz.: 29 vert.: 16
[ 2275.193] (II) intel(0): Gamma: 2.20
[ 2275.193] (II) intel(0): No DPMS capabilities specified
[ 2275.193] (II) intel(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
[ 2275.193] (II) intel(0): First detailed timing is preferred mode
[ 2275.193] (II) intel(0): redX: 0.589 redY: 0.347 greenX: 0.343 greenY: 0.555
[ 2275.193] (II) intel(0): blueX: 0.160 blueY: 0.124 whiteX: 0.313 whiteY: 0.329
[ 2275.193] (II) intel(0): Manufacturer's mask: 0
[ 2275.193] (II) intel(0): Supported detailed timing:
[ 2275.193] (II) intel(0): clock: 70.0 MHz Image Size: 293 x 165 mm
[ 2275.193] (II) intel(0): h_active: 1366 h_sync: 1402 h_sync_end 1438 h_blank_end 1476 h_border: 0
[ 2275.193] (II) intel(0): v_active: 768 v_sync: 772 v_sync_end 780 v_blanking: 790 v_border: 0
[ 2275.193] (II) intel(0): LG Display
[ 2275.193] (II) intel(0): LP133WH2-TLF1
[ 2275.193] (II) intel(0): EDID (in hex):
[ 2275.193] (II) intel(0): 00ffffffffffff0030e4710300000000
[ 2275.193] (II) intel(0): 00160103801d10780afc359658578e29
[ 2275.193] (II) intel(0): 1f505400000001010101010101010101
[ 2275.193] (II) intel(0): 010101010101581b566e500016302424
[ 2275.194] (II) intel(0): 480025a5100000190000000000000000
[ 2275.194] (II) intel(0): 00000000000000000000000000fe004c
[ 2275.194] (II) intel(0): 4720446973706c61790a2020000000fe
[ 2275.194] (II) intel(0): 004c503133335748322d544c463100ce
[ 2275.194] (II) intel(0): EDID vendor "LGD", prod id 881
[ 2275.194] (II) intel(0): Printing DDC gathered Modelines:
[ 2275.194] (II) intel(0): Modeline "1366x768"x0.0 70.00 1366 1402 1438 1476 768 772 780 790 -hsync -vsync (47.4 kHz eP)
[ 2275.194] (II) intel(0): Not using default mode "320x240" (doublescan mode not supported)
[ 2275.194] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported)
[ 2275.194] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported)
[ 2275.194] (II) intel(0): Not using default mode "512x384" (doublescan mode not supported)
[ 2275.194] (II) intel(0): Not using default mode "640x480" (doublescan mode not supported)
[ 2275.194] (II) intel(0): Not using default mode "640x512" (doublescan mode not supported)
[ 2275.194] (II) intel(0): Not using default mode "800x600" (doublescan mode not supported)
[ 2275.194] (II) intel(0): Not using default mode "896x672" (doublescan mode not supported)
[ 2275.194] (II) intel(0): Not using default mode "928x696" (doublescan mode not supported)
[ 2275.194] (II) intel(0): Not using default mode "960x720" (doublescan mode not supported)
[ 2275.194] (II) intel(0): Not using default mode "700x525" (doublescan mode not supported)
[ 2275.194] (II) intel(0): Not using default mode "1024x768" (doublescan mode not supported)
[ 2275.194] (II) intel(0): Printing probed modes for output LVDS1
[ 2275.194] (II) intel(0): Modeline "1366x768"x60.0 70.00 1366 1402 1438 1476 768 772 780 790 -hsync -vsync (47.4 kHz eP)
[ 2275.194] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz d)
[ 2275.194] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz d)
[ 2275.194] (II) intel(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz d)
[ 2275.194] (II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz d)
[ 2275.194] (II) intel(0): EDID for output VGA1
[ 2275.195] (II) intel(0): EDID for output HDMI1
[ 2275.236] (II) intel(0): EDID for output DP1
[ 2275.236] (II) intel(0): Output LVDS1 connected
[ 2275.236] (II) intel(0): Output VGA1 disconnected
[ 2275.236] (II) intel(0): Output HDMI1 disconnected
[ 2275.236] (II) intel(0): Output DP1 disconnected
[ 2275.236] (II) intel(0): Using exact sizes for initial modes
[ 2275.236] (II) intel(0): Output LVDS1 using initial mode 1366x768
[ 2275.236] (II) intel(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 2275.236] (**) intel(0): Display dimensions: (290, 160) mm
[ 2275.236] (**) intel(0): DPI set to (119, 121)
[ 2275.236] (II) Loading sub module "dri2"
[ 2275.236] (II) LoadModule: "dri2"
[ 2275.237] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 2275.237] (II) Module dri2: vendor="X.Org Foundation"
[ 2275.237] compiled for 1.12.4, module version = 1.2.0
[ 2275.237] ABI class: X.Org Server Extension, version 6.0
[ 2275.237] (==) Depth 24 pixmap format is 32 bpp
[ 2275.237] (II) intel(0): SNA initialized with IvyBridge backend
[ 2275.237] (==) intel(0): Backing store disabled
[ 2275.237] (==) intel(0): Silken mouse enabled
[ 2275.237] (II) intel(0): HW Cursor enabled
[ 2275.237] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 2275.238] (==) intel(0): DPMS enabled
[ 2275.239] (II) intel(0): [DRI2] Setup complete
[ 2275.239] (II) intel(0): [DRI2] DRI driver: i965
[ 2275.239] (II) intel(0): direct rendering: DRI2 Enabled
[ 2275.239] (==) intel(0): hotplug detection: "enabled"
[ 2275.239] (--) RandR disabled
[ 2275.239] (II) Initializing built-in extension Generic Event Extension
[ 2275.239] (II) Initializing built-in extension SHAPE
[ 2275.239] (II) Initializing built-in extension MIT-SHM
[ 2275.239] (II) Initializing built-in extension XInputExtension
[ 2275.239] (II) Initializing built-in extension XTEST
[ 2275.239] (II) Initializing built-in extension BIG-REQUESTS
[ 2275.239] (II) Initializing built-in extension SYNC
[ 2275.239] (II) Initializing built-in extension XKEYBOARD
[ 2275.239] (II) Initializing built-in extension XC-MISC
[ 2275.239] (II) Initializing built-in extension SECURITY
[ 2275.239] (II) Initializing built-in extension XINERAMA
[ 2275.239] (II) Initializing built-in extension XFIXES
[ 2275.239] (II) Initializing built-in extension RENDER
[ 2275.239] (II) Initializing built-in extension RANDR
[ 2275.239] (II) Initializing built-in extension COMPOSITE
[ 2275.239] (II) Initializing built-in extension DAMAGE
[ 2275.250] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 2275.250] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 2275.250] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
[ 2275.250] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[ 2275.250] (II) AIGLX: Loaded and initialized i965
[ 2275.250] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 2275.251] (II) intel(0): switch to mode 1366x768 on crtc 3 (pipe 0)
[ 2275.276] (II) intel(0): Setting screen physical size to 361 x 203
[ 2275.319] (II) config/udev: Adding input device Power Button (/dev/input/event6)
[ 2275.319] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 2275.319] (II) LoadModule: "evdev"
[ 2275.319] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 2275.320] (II) Module evdev: vendor="X.Org Foundation"
[ 2275.320] compiled for 1.12.3.901, module version = 2.7.3
[ 2275.320] Module class: X.Org XInput Driver
[ 2275.320] ABI class: X.Org XInput driver, version 16.0
[ 2275.320] (II) Using input driver 'evdev' for 'Power Button'
[ 2275.320] (**) Power Button: always reports core events
[ 2275.320] (**) evdev: Power Button: Device: "/dev/input/event6"
[ 2275.320] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 2275.320] (--) evdev: Power Button: Found keys
[ 2275.320] (II) evdev: Power Button: Configuring as keyboard
[ 2275.320] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input6/event6"
[ 2275.320] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 2275.320] (**) Option "xkb_rules" "evdev"
[ 2275.320] (**) Option "xkb_model" "evdev"
[ 2275.320] (**) Option "xkb_layout" "se"
[ 2275.355] (II) config/udev: Adding input device Fujitsu FUJ02E3 (/dev/input/event3)
[ 2275.356] (**) Fujitsu FUJ02E3: Applying InputClass "evdev keyboard catchall"
[ 2275.356] (II) Using input driver 'evdev' for 'Fujitsu FUJ02E3'
[ 2275.356] (**) Fujitsu FUJ02E3: always reports core events
[ 2275.356] (**) evdev: Fujitsu FUJ02E3: Device: "/dev/input/event3"
[ 2275.356] (--) evdev: Fujitsu FUJ02E3: Vendor 0 Product 0x6
[ 2275.356] (--) evdev: Fujitsu FUJ02E3: Found keys
[ 2275.356] (II) evdev: Fujitsu FUJ02E3: Configuring as keyboard
[ 2275.356] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/FUJ02E3:00/input/input3/event3"
[ 2275.356] (II) XINPUT: Adding extended input device "Fujitsu FUJ02E3" (type: KEYBOARD, id 7)
[ 2275.356] (**) Option "xkb_rules" "evdev"
[ 2275.356] (**) Option "xkb_model" "evdev"
[ 2275.356] (**) Option "xkb_layout" "se"
[ 2275.357] (II) config/udev: Adding input device Video Bus (/dev/input/event9)
[ 2275.357] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 2275.357] (II) Using input driver 'evdev' for 'Video Bus'
[ 2275.357] (**) Video Bus: always reports core events
[ 2275.357] (**) evdev: Video Bus: Device: "/dev/input/event9"
[ 2275.357] (--) evdev: Video Bus: Vendor 0 Product 0x6
[ 2275.357] (--) evdev: Video Bus: Found keys
[ 2275.357] (II) evdev: Video Bus: Configuring as keyboard
[ 2275.357] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input9/event9"
[ 2275.357] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 8)
[ 2275.358] (**) Option "xkb_rules" "evdev"
[ 2275.358] (**) Option "xkb_model" "evdev"
[ 2275.358] (**) Option "xkb_layout" "se"
[ 2275.359] (II) config/udev: Adding input device Fujitsu FUJ02B1 (/dev/input/event2)
[ 2275.359] (**) Fujitsu FUJ02B1: Applying InputClass "evdev keyboard catchall"
[ 2275.359] (II) Using input driver 'evdev' for 'Fujitsu FUJ02B1'
[ 2275.359] (**) Fujitsu FUJ02B1: always reports core events
[ 2275.359] (**) evdev: Fujitsu FUJ02B1: Device: "/dev/input/event2"
[ 2275.359] (--) evdev: Fujitsu FUJ02B1: Vendor 0 Product 0x6
[ 2275.359] (--) evdev: Fujitsu FUJ02B1: Found keys
[ 2275.359] (II) evdev: Fujitsu FUJ02B1: Configuring as keyboard
[ 2275.359] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:02/FUJ02B1:00/input/input2/event2"
[ 2275.359] (II) XINPUT: Adding extended input device "Fujitsu FUJ02B1" (type: KEYBOARD, id 9)
[ 2275.359] (**) Option "xkb_rules" "evdev"
[ 2275.359] (**) Option "xkb_model" "evdev"
[ 2275.359] (**) Option "xkb_layout" "se"
[ 2275.360] (II) config/udev: Adding input device Power Button (/dev/input/event5)
[ 2275.360] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 2275.360] (II) Using input driver 'evdev' for 'Power Button'
[ 2275.360] (**) Power Button: always reports core events
[ 2275.360] (**) evdev: Power Button: Device: "/dev/input/event5"
[ 2275.360] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 2275.360] (--) evdev: Power Button: Found keys
[ 2275.360] (II) evdev: Power Button: Configuring as keyboard
[ 2275.361] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input5/event5"
[ 2275.361] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 10)
[ 2275.361] (**) Option "xkb_rules" "evdev"
[ 2275.361] (**) Option "xkb_model" "evdev"
[ 2275.361] (**) Option "xkb_layout" "se"
[ 2275.362] (II) config/udev: Adding input device Lid Switch (/dev/input/event4)
[ 2275.362] (II) No input driver specified, ignoring this device.
[ 2275.362] (II) This device may have been added with another device file.
[ 2275.362] (II) config/udev: Adding input device FJ Camera (/dev/input/event7)
[ 2275.362] (**) FJ Camera: Applying InputClass "evdev keyboard catchall"
[ 2275.362] (II) Using input driver 'evdev' for 'FJ Camera'
[ 2275.362] (**) FJ Camera: always reports core events
[ 2275.362] (**) evdev: FJ Camera: Device: "/dev/input/event7"
[ 2275.363] (--) evdev: FJ Camera: Vendor 0x10f1 Product 0x1a44
[ 2275.363] (--) evdev: FJ Camera: Found keys
[ 2275.363] (II) evdev: FJ Camera: Configuring as keyboard
[ 2275.363] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.3/3-1.3:1.0/input/input7/event7"
[ 2275.363] (II) XINPUT: Adding extended input device "FJ Camera" (type: KEYBOARD, id 11)
[ 2275.363] (**) Option "xkb_rules" "evdev"
[ 2275.363] (**) Option "xkb_model" "evdev"
[ 2275.363] (**) Option "xkb_layout" "se"
[ 2275.364] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event10)
[ 2275.364] (II) No input driver specified, ignoring this device.
[ 2275.364] (II) This device may have been added with another device file.
[ 2275.364] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=3 (/dev/input/event11)
[ 2275.364] (II) No input driver specified, ignoring this device.
[ 2275.364] (II) This device may have been added with another device file.
[ 2275.365] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event12)
[ 2275.365] (II) No input driver specified, ignoring this device.
[ 2275.365] (II) This device may have been added with another device file.
[ 2275.365] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 2275.365] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 2275.365] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[ 2275.366] (**) AT Translated Set 2 keyboard: always reports core events
[ 2275.366] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[ 2275.366] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[ 2275.366] (--) evdev: AT Translated Set 2 keyboard: Found keys
[ 2275.366] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[ 2275.366] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[ 2275.366] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 12)
[ 2275.366] (**) Option "xkb_rules" "evdev"
[ 2275.366] (**) Option "xkb_model" "evdev"
[ 2275.366] (**) Option "xkb_layout" "se"
[ 2275.366] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event8)
[ 2275.366] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Touchpad Catchall"
[ 2275.366] (II) LoadModule: "synaptics"
[ 2275.366] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[ 2275.367] (II) Module synaptics: vendor="X.Org Foundation"
[ 2275.367] compiled for 1.12.2, module version = 1.6.2
[ 2275.367] Module class: X.Org XInput Driver
[ 2275.367] ABI class: X.Org XInput driver, version 16.0
[ 2275.367] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
[ 2275.367] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 2275.367] (**) Option "Device" "/dev/input/event8"
[ 2275.367] (II) synaptics: SynPS/2 Synaptics TouchPad: found clickpad property
[ 2275.367] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5472
[ 2275.367] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4448
[ 2275.367] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
[ 2275.367] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
[ 2275.367] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left double triple
[ 2275.367] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
[ 2275.367] (**) Option "TapButton1" "1"
[ 2275.367] (**) Option "TapButton2" "2"
[ 2275.367] (**) Option "TapButton3" "3"
[ 2275.367] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 2275.367] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 2275.367] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input8/event8"
[ 2275.368] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 13)
[ 2275.368] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
[ 2275.368] (**) synaptics: SynPS/2 Synaptics TouchPad: MaxSpeed is now 1.75
[ 2275.368] (**) synaptics: SynPS/2 Synaptics TouchPad: AccelFactor is now 0.040
[ 2275.368] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
[ 2275.368] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
[ 2275.368] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
[ 2275.368] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
[ 2275.368] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 2275.368] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0)
[ 2275.368] (II) No input driver specified, ignoring this device.
[ 2275.368] (II) This device may have been added with another device file.
[ 2275.368] (II) config/udev: Adding input device PC Speaker (/dev/input/event1)
[ 2275.368] (II) No input driver specified, ignoring this device.
[ 2275.368] (II) This device may have been added with another device file.
xinput
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ SynPS/2 Synaptics TouchPad id=13 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Fujitsu FUJ02E3 id=7 [slave keyboard (3)]
↳ Video Bus id=8 [slave keyboard (3)]
↳ Fujitsu FUJ02B1 id=9 [slave keyboard (3)]
↳ Power Button id=10 [slave keyboard (3)]
↳ FJ Camera id=11 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=12 [slave keyboard (3)]
running
dmesg | grep -i synaptics
doesn't show anything. However running
dmesg | grep -i psmouse
returns a lot of
psmouse serio1: bad data from KBC - timeout
Last edited by flako (2012-11-08 09:44:59)

I have tried doing that with both linux mint, and now fedora live usb. Neither one loads the touchpad correctly. So yeah, our problems weren't really related
Anyway, I tried looking into the
psmouse serio1: bad data from KBC - timeout
messages, and tried running psmouse proto (defined in /etc/modprobe.conf/psmouse.conf) as both raw and imps as per https://answers.launchpad.net/ubuntu/+s … ion/206950 Unfortunately, that didn't solve anything. Using the raw setting meant that the touchpad wasn't loaded at all (as in not appearing in the Xorg.log at all).
The laptop is quite new, but at the same time what i figured from the touchpad vendor & product ID, the touchpad itself isn't. So it should technically work. Before installing arch i booted into windows to see if everything worked, and found no issues with the touchpad. So I have ruled out any hardware errors. Maybe its just the Fn-key that doesn't work yet in Linux? But that doesn't explain the "psmouse serio1: bad data from KBC - timeout" Any pointers to where I should look/ what commands I should run to delve deeper into this issue?
Last edited by flako (2012-09-09 12:10:51)

Error while activating Account Dimension in BPC 10

Hi All,
While trying to activate the Account Dimension, it is giving an error. Please see the screenshot below. Please let me know if someone has faced this issue before and has solved this.
Thanks in advance,
Best Regards,
Venkata

Hi Bhupi -
Go to SU53 T-code from the back end , you can find the authorization issues; It will clearly mention what authorizations are missing in Red.
Hope this helps!!!

Video card dell dimension 3000

Hey, everybody.
Im planning to buy a new video card for my ; dell dimension 3000, Intel(R) , Celeron(R) CPU 2.4GHz, 2.00 gb of ram, and I believe power supply is 250 W.
So here is the bunch of questions;
1. Seems like my computer uses a pci type memory cards, my question here is can I use these wide known pci e cards?
2. Second one is I seen that there are different sizes of video cards out there for sale, so how do I figure out which one I should use, I mean is there a maximum number of mb that my computer supports or I could use any size of video card?
..and I think so far I do not have more questions about my video memory card purchase.
*all help would be appreciated Thanks*

1. you will not be able to use a PCI-E card in the Dimension 3000.
2. Your choices are very limted on PCI videocards and the performance increase is not worth the money that a new card will cost you. You could go with a 512mb PCI card but with the slow celeron processor and and low end power supply. You still will not be able to play of the new games that are out right now.
It's time for a new computer.
**If you like my answer then click the little Star under my username.
**If my response answered your question then click the Solved button. Thanks

Showing Multiple dimension columns in same report

We need to show revenue data in one report (pivot table) with column headings as Month, Qtr and Year coming from the same dimension.
The Report should be like,
Jul Aug Sep Q3-2007 2007
Revenue
We are able to create separate views for month, year and quarter in the same report but we need all of them to show up in one line in the same view. If we create 3 separate views then they are not correctly aligned on the dashboard page. Can we create a single view using these columns.
Any suggestions on how to solve this?
Thanks.

use min(month), min(month)+1 , max(month) , quarter, year at qurter level report

Multiple columns from the same dimension table as row labels performing slowly

(Working with SSAS tabular)
I'm trying to figure out what the approach should be for the following scenario:
Lets say we have a Customer table. The table has columns such as account number, department number, name, salesperson, account manager, number of customers, delivery route, etc
A user of the model could want to see any permutation of that information as the row labels. How should that be handled?
What we've been doing so far is that the user adds each column they want into the "ROWS" section in Excel. This works fine with smaller tables (for example, "Department" table with a "Department Code" and "Department Name",
but on large tables this quickly chokes. I understand why this is happening, I just haven't found a better way to accomplish the same thing.
I can add a calculated column to the model through VS, but obviously this is unsupportable and unscalable when each person needs their own permutations of the data. Can something similar be done in Excel?
This question seems to be what I need:
http://social.msdn.microsoft.com/Forums/en-US/97d1157a-1402-4227-b96a-79524401ddcd/mdx-query-performance-when-selecting-multiple-attributes-from-same-dimension?forum=sqlanalysisservices
However I can't find any information on how to add those properties (is it a multidimensional-only thing?)

Thanks for the help. Sorry but i'm a self-taught developer, and i may be missing some basics :)
Anyway i've done what you suggested but i get this error:
[nQSError: 15011]The dimension table source Dimension Services.DM_D_SERVIZI_SRV has an aggregate content specification that specifies the level Product. But the source mapping contains column COD_PRODUCT with a functional dependency association on a more detailed level .
where:
- DM_D_SERVIZI_SRV is the physical alias for the Service Dimension (and the name of the LTS too)
- COD_PRODUCT is the leaf of the hierarchy, the physical primary key, but it hasnt to be included in the hierarchy
Do i have to add another level with the primary key and hide it to the users?
I tried to solve this going to the logical tables source properties, on the tab contents, setting "logical level" to null for the hierarchy, but i don't know if this is correct.
Thanks

Solved Dimension

Similar Messages

Maybe you are looking for