Unable to do Physical Join in rpd

Hi
I tried to join table Ra_Customer_trx_all and OE_order_header_all but the join condition is to_char(OE_order_header_all .order_number) = Ra_Customer_trx_all .Attribute6
can i use this join condition in physical layer..Because in physical join we staraightway give the join condition but here we are changing the column type and then using the join.
I am using OBIEE 11g
thanks in advance for the help
Debo

Hi
Thanks for the solution in physical join but when i simply join the two tables in the business layer the logical join is not pulling any data..Do we need to do something else to do the logical join between those tables
Regards
Debo

Similar Messages

  • Unable to create logical joins

    Oracle BI version 10.1.3.3
    After transferring the tables from the physical layer to the business modeling layer, I am trying to create logical joins among the tables in the logical layer using the Logical Diagram. At the logical join dialog box, I am unable to select the table columns on either side and the join operator is grayed out. The join is created, but with an empty expression.
    I am, however, able to create foreign keys in this layer.
    What could be the reason for this, and how do I create logical joins? The documentation recommends to create logical joins rather than foreign keys.
    I have the same problem if I use the Join Manager.
    Thanks.

    Hi,
    What you´re doing is creating "Complex joins" at logical level, that´s why the boxes are grey, you can't insert a join operator in this type of joins. It is recommended that you use complex joins at logical level that follow's the physical joins at physical level.
    Regards.

  • Between Operator in physical join

    Hello,
    Can we use between operator in physical join. We did that, its successfully checking in, but when we re-open the join, its show in RED color.
    So, got doubt, can we use between?
    and we have another error
    "No fact table exists at the requested level of detail"; what does this error mean
    Waiting for reply...
    Regards
    Kiran

    Can we use between operator in physical join. We did that, its successfully checking in, but when we re-open the join, its show in RED color.
    So, got doubt, can we use between?When you checkout the rpd object in online mode it would display in red, this is not an error.
    "No fact table exists at the requested level of detail"; what does this error meanThis error usually happens if you have not mapped the content level correctly in the logical table source.
    Rgds,
    Dpka

  • Documenting Joins in RPD

    Hi All,
    I want to document all Physical Joins present in RPD. Is there any way to do it instead of going through each and every join and documenting manually.
    Thanks

    1.) Agreed.
    2.) Not really. This is a physcial FKey in UDML:
    DECLARE FOREIGN KEY "Writeback (MSSQL)".."PADISHA"."Writeback (Fact)"."Writeback (Fact)_FKey" AS "Writeback (Fact)_FKey" HAVING
                "Writeback (MSSQL)".."PADISHA"."Writeback (Fact)"."COMMENT_ID" ) REFERENCES  "Writeback (MSSQL)".."PADISHA"."Dim - Market (WRITEBACK_F)"."COMMENT_ID"
         PRIVILEGES ( READ);Join expression:
    "Writeback (MSSQL)".."PADISHA"."Writeback (Fact)"."COMMENT_ID" ) REFERENCES  "Writeback (MSSQL)".."PADISHA"."Dim - Market (WRITEBACK_F)"."COMMENT_ID"Tables:
    - "Writeback (MSSQL)".."PADISHA"."Writeback (Fact)"
    - "Writeback (MSSQL)".."PADISHA"."Dim - Market (WRITEBACK_F)"
    These tables are alias objects and point to the physical table.
    So UDML has all you need.

  • What is the different between Logical complex join and Physical join?

    hi,
    Do somebody know what is the function different between logical complex join in BMM layer and physical join in physical layer?
    Thanks.

    Thank you very much1
    I understand their differentiation:
    In the BMM Complex join (intelligent), means OBI picks the best way from possibly many different ways to join using physical join. FK join forces the same join always, which limits flexibility.

  • Unable to determine Physical Disk from the VM manager : 3.2.1

    Unable to determine Physical Disk from the VM manager :
    OVM manager : 3.2.1.516
    VM Server : Available disks on vm server
    # fdisk -l
    Disk /dev/sda: 500.1 GB, 500107862016 bytes
    255 heads, 63 sectors/track, 60801 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot Start End Blocks Id System
    /dev/sda1 1 13 104391 83 Linux
    /dev/sda2 14 405 3148740 83 Linux
    /dev/sda3 406 536 1052257+ 82 Linux swap / Solaris
    Disk /dev/sdb: 80.0 GB, 80000000000 bytes
    255 heads, 63 sectors/track, 9726 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot Start End Blocks Id System
    /dev/sdb1 * 1 13 104391 83 Linux
    /dev/sdb2 14 9328 74822737+ 83 Linux
    /dev/sdb3 9329 9459 1052257+ 82 Linux swap / Solaris
    Disk /dev/dm-0: 80.0 GB, 80000000000 bytes
    255 heads, 63 sectors/track, 9726 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot Start End Blocks Id System
    /dev/dm-0p1 * 1 13 104391 83 Linux
    /dev/dm-0p2 14 9328 74822737+ 83 Linux
    /dev/dm-0p3 9329 9459 1052257+ 82 Linux swap / Solaris
    Disk /dev/dm-1: 106 MB, 106896384 bytes
    255 heads, 63 sectors/track, 12 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot Start End Blocks Id System
    Disk /dev/dm-2: 76.6 GB, 76618483200 bytes
    255 heads, 63 sectors/track, 9315 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk /dev/dm-2 doesn't contain a valid partition table
    Disk /dev/dm-3: 1077 MB, 1077511680 bytes
    255 heads, 63 sectors/track, 131 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk /dev/dm-3 doesn't contain a valid partition table
    #

    thanks for your prompt response.
    I am aware of that we can't use any free spaces where the VM is installed.Hence the additional storage added to the server.
    1. Install VM Server on 80GB HD ( /dev/sdb)
    2. Later, i added 500GB to the storage ( no installation - just the disk ) ( /dev/sda)
    Same configuration worked fine in 3.0, now i am not able to identified the additional disk which was added later with 3.2.1.

  • Filestream Creation Unable to Open Physical File Operating System Error 259

    Hey Everybody,
    I have run out of options supporting a customer that is having an error when creating a database with a file stream.  The error displayed is unable to open physical file operating system error 259 (No more data is available).  We're using a pretty
    standard creation SQL script that we aren't having issues with other customers:
    -- We are going to create our data paths for the filestreams.  
    DECLARE @data_path nvarchar(256);
    SET @data_path = (SELECT SUBSTRING(physical_name, 1, CHARINDEX(N'master.mdf', LOWER(physical_name)) - 1)
                      FROM master.sys.master_files
                      WHERE database_id = 1 AND file_id = 1);
    -- At this point, we should be able to create our database.  
    EXECUTE ('CREATE DATABASE AllTables
    ON PRIMARY
        NAME = AllTables_data
        ,FILENAME = ''' + @data_path + 'AllTables_data.mdf''
        ,SIZE = 10MB
        ,FILEGROWTH = 15%
    FILEGROUP FileStreamAll CONTAINS FILESTREAM DEFAULT
        NAME = FSAllTables
        ,FILENAME = ''' + @data_path + 'AllTablesFS''
    LOG ON
        NAME = AllTables_log
        ,FILENAME = ''' + @data_path + 'AllTables_log.ldf''
        ,SIZE = 5MB
        ,FILEGROWTH = 5MB
    GO
    We are using SQL Server 2014 Express.  File streams were enabled on the installation SQL Server.  The instance was created successfully and we are able to connect to the database through SSMS. The user is using an encrypted Sophos. 
    We have tried the following:
    1. Increasing the permissions of the SQL Server server to have full access to the folders.
    2. Attempted a restore of a blank database and it failed.
    There doesn't seem to be any knowledge base articles on this particular error and I am not sure what else I can do to resolve this.  Thanks in advance for any help!

    Hi Ryan,
    1)SQL Server(any version) can't be installed on encrypted drives. Please see a similar scenario in the following link
    https://ask.sqlservercentral.com/questions/115761/filestream-and-encrypted-drives.html
    2)I don't think there is any problem with permissions on the folder, if the user can create a database in the same folder. Am not too sure. Also see the article by
    Jacob on configuring the FILESTREAM for SQL Server that describes how to configure FILESTREAM access level & creating a FILESTREAM enabled database
    Hope this helps,
    Thanks
    Bhanu 

  • Physical Joins Difference Between 10G and 11G?

    Hi All, I have started using OBIEE 11G. Anybody please let me know is there any difference in applying physical joins in OBIEE 10G and 11G.
    I heard that we need to join Fact and Dim tables in reverse way in 11G.
    Thanks in Advance.

    # Fast-Start Failover for Maximum Performance Mode in a Data Guard Configuration
    # Compression of Redo Traffic (Only for Gap Resolution) Over the Network in a Data Guard Configuration
    # Real-Time Query Capability of Physical Standby Database
    # Fast Role Transitions in a Data Guard Configuration
    # Data Guard Integration, Simplification, and Performance
    # Dynamic Setting of Oracle Data Guard SQL Apply Parameters
    # Enhanced Data Guard Broker Based Management Framework
    # Histogram for Redo Transport Response Time in a Data Guard Configuration
    # Snapshot Standby
    # Strong Authentication for Data Guard Redo Transport
    # Enhanced DDL Handling in Oracle Data Guard SQL Apply
    # Enhanced Oracle RAC Switchover Support for Logical Standby Databases
    # Data Guard Logical Apply Completeness
    # Oracle Scheduler Support in Data Guard SQL Apply
    # Support Transparent Data Encryption (TDE) with Data Guard SQL Apply
    # Support XMLType Data Type (Only CLOB) in Data Guard SQL Apply
    # Virtual Private Database (VPD) Support in Data Guard SQL Apply
    See Also:
    Oracle Data Guard Concepts and Administration for details
    Ref. Oracle® Database New Features Guide
    11g Release 1 (11.1)
    Part Number B28279-01
    ~ Madrid

  • Physical Joins in OBIEE 11G

    Hi All,
    I just started 11g and am finding it very hard to understand why the physical join is created from Fact to Dimension and how does this qualify as 1:N.
    Can anyone explain if I am missing something.
    Thanks in advance.

    Hi,
    A foreign key repository join is used only to define a Primary Key-Foreign Key Relationships in the Physical Layer.
    It consist of a column or a set of columns and refers to the primary key column in another table.
    When you create it in the physical diagram, you have to point first the dimension and then the fact table.
    When you import keys in a physical schema, the primary key-foreign key joins are automatically defined.
    If you want to define other relationship, you have to use a complex join.
    And,
    In the business model, OBI recommends using complex logical joins instead of foreign key logical joins.
    When Complex joins are used in the business layer then they are really acting as placeholders. They allow the OBI Server to decide on which are the best joins define in the Physical Layer to satisfy the request.
    In a Dimension, you may have multiple Logical Table sources that all join to one fact table. The OBI Server will then decide the best joins to use to meet the requirements.
    Regards,
    MuRam

  • Logical joins vs Physical joins

    Hello,
    Can anyone tell me what is the difference between physical joins and logical joins. And how OBI Server treats the joins in relation to the Logical and Physical Layer.
    I'm a little confused also with the place to configure the joins, since there is more than one option.
    Thanks in advance,
    Sofiane

    Well actually no. The actual sql fired would depend on both the logical and physical joins. Logical join would be the entry point. Think of it this way. Business Model layer helps you designing a star schema(like a data warehouse) out of your source data. So logical joins are joins that you define on your star schema. But the star schema in itself derives its data from physical layer. So the Physical layer joins would be necessary as well. But if you have a star schema already in your physical layer the physical joins alone would suffice and logical joins are redundant but necessary.
    Thanks,
    Venkat
    http://oraclebizint.wordpress.com

  • Suse 10: Unable to release physical memory: Bad file descriptor

    When I'm trying to run jrockit it prints the message "Unable to release
    physical memory: Bad file descriptor":
    stef@linux:~> export JAVA_HOME=/home/stef/progs/jrockit-jdk1.5.0_03
    stef@linux:~> export PATH=/home/stef/progs/jrockit-jdk1.5.0_03/bin:$PATH
    stef@linux:~> java -version
    Unable to release physical memory: Bad file descriptor
    [~38 time the same message]
    Unable to release physical memory: Bad file descriptor
    java version "1.5.0_03"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_03-b07)
    BEA JRockit(R) (build dra-45238-20050523-2008-linux-ia32, R25.2.0-28)
    The vm does work and the speed seems to be okay but this messages pops
    up every time I try to run an application. (It's not specific to this
    user it also happens for root)
    What does it mean and what can I do about it?
    Yours,
    Stefan

    You can safely ignore the messages. It is a result of changes in the implementation of madvise in the 2.6.13 kernel (which, needless to say, isn't supported with JRockit). We'll change our usage in a future release so that these messages don't show up.
    Thanks for pointing it out,
    /Staffan

  • Joins in rpd

    Hi, I know that we create foreign key joins in the Physical Layer and complex joins in BMM layer. Can we create complex join in Physical Layer and foreign key joins in BMM layer? Under which circumstances should we do this? Is there any benefit/disadvantage in doing so?
    Thanks,
    D

    hi,
    Can we create complex join in Physical Layer
    Re: complex join at physical layer
    In BMM layer we can do only complex joins not physical joins
    thanks,
    saichand.v

  • Difference between physical join and logical join

    Hi Gurus,
    Can anyone tell me what is the difference between physical join and logical join
    Thanks,
    Chandra

    Hi,
    A physical join is at the physical layer and defines the join between two physical tables. Logical joins live at the BMM (logical) layer and define a join between two logical tables.
    The important differentiation is that at the BMM layer you do not tell the OBIEE server how to do the join, you just tell it that there is a relationship between these two logical entities. When the server comes to this logical join it will use the information in the physical joins and decides how the two logical tables are joined together.
    In BMM you use complex joins to establish which logical tables are joined which another, the OBI EE server will go to the physical level to search the physical join to make the query. You can also use physical joins in the BMM to override the join in the physical layer but only in very specific conditions.
    If you also set complex join in the physical layer OBI EE won't be able to construct the physical query.
    Hope this answers your question.
    Award points if helpful.
    Thanks,
    -Amith.

  • ABAP query- unable to delete the join between tables

    Im unable to delete the join between two tables. when i right clicked on the join then it gives two options:
    1. Display join condition
    2. Remove join condition
    both these options are grey in color so i cant select them. how can i remove join?

    goto SQ02 and enter infoset and goto change mode agagin select change mode and click the join then select and delete link...

  • Use of complex join in BMM and Physical Join in Physical layer ?

    Hi All ,
    Why we need to use complex join in BMM layer not the Physical Join ?
    Why we need to use Physical Join in Physical layer not Complex join ?
    thanks in advance

    Hi,
    A physical join is at the physical layer and defines the join between two physical tables.
    Logical joins live at the BMM (logical) layer and define a join between two logical tables.
    The important differentiation is that at the BMM layer you do not tell the OBIEE server how to do the join,
    you just tell it that there is a relationship between these two logical entities.
    when the server comes to this logical join it will use the information in the physical joins and decides how the two logical tables are joined together.
    thanks,
    pramod.

Maybe you are looking for