Sql not supported in view in physical layer

hi, I wanna create a view (in physical layer)
table type = Select (under General tab in Phyiscal Table property)
I have checked the checkbox "Use database specific SQL".
and chosen "Oracle 9i" in Database tree.
the data structure in the table is in this thread methodology to get the result
the sql is
SELECT user,
MAX(decode(type,'A',value)) A,
MAX(decode(type,'B',value)) B,
MAX(decode(type,'C',value)) C
FROM tab
GROUP BY user
BUT when I click "View data" on the menu bar (right click the object in the phyiscal layer)
I get the error message.
Is max or decode not supported ? thanks

Could you please provide the error message that you are getting?
Cheers,
Prasad Bolla.

Similar Messages

What does your account type does not support the view account feature mean?

What does your account type does not support the view account feature mean?

In reference to what? Where are you seeing this message - iTunes? Do you use a credit card for purchases in iTunes or do you download only free content?

Creating views in Physical Layer of OBIEE Administration Tool

Hello,
I am doing a proof of concept of creating an OBIEE repository using the Administration Tool to make a model for an in house sandbox OLTP system. Because this POC isn't using a warehouse that is built nicely with everything I need, I am having to import the OLTP tables into the Physical Layer and then create a few extra views (by creating a new physical table object and selecting "Table Type: Select") to add some new columns I will need.
My problem is that once I have created two views 'ViewA' and 'ViewB', I want to then create a third view 'ViewC' that is the union of 'ViewA' and 'ViewB'. But when I create ViewC from these two views and try to then update row count or view data in newly created ViewC, I get an error message of the effect:
Message 208: Invalid object name 'DBO.ViewA'
Message 208: Invalid object name 'DBO.ViewB'
When I try and create ViewC with DBO.OriginalTableA and DBO.OriginalTableB, however, it works just fine. And I am also able to successfully update row count and view data in ViewA and ViewB independently. So it seems to me like a view initialization problem when trying to have ViewC be created from A and B.
Am I trying to do something that is not allowed in the Physical Layer of the BI Admin Tool? I would think that I should be able to work with views just like actual physical tables from my OLTP. Maybe not.
Any help or insight would be greatly appreciated. Many thanks.

Hi Hammett81 ,
I think, I have given configured connection pool correct. (following Oracle guidelines: 'In the Connection Pool dialog box, on the General tab, verify that the call interface is set to Default (OCI 10g) and change the data source name to the appropriate tnsnames.ora entry ( ORCL in this example). Please note that this is the TNS service name, not the ODBC DSN. ' )
I tried to give ODBC DSN (SH) as call interface, which resulted in an Error dialogue, implying, previous configuration was correct.
So, I reverted back.
Regards,
Deeba

Views in Physical Layer

When creating a view on the Physical Layer, we get some white space to write a select statement on the window, Do we have nay parameter to choose the length of the space assigned.
My query is a long one containing many unions and i am running out of the space there.
Any parameter or config file where i can control the length of the space available ?

Sid_BI wrote:
Hi,
If you create an opaque view ..the BI will Physical layer will have to complete all the joins at the BI Server level and then send it to the db..
while otherwise BI Joins will complete all the joins with the view and send it to the data base which would then replace it with the actual view query ...
so you leave less strain on BI server to start with
Secondly as a practice since view is a db object why not let it be in the db for the dba to maintain that in the repository where BI Admin has to maintain wrt future enhancements etc..There are various reasons to have opaque view and a view not as a database object atleast with high security level database. I cannot give out the reasons here though. But I am not able to accept your explanation of Joins. The joins happen in the database only and not on the BI server.

If i use view in physical layer will it causes to performence

hi all
if i create a view in the physical layer will it causes to performance issue
can any one suggest me on it,bez i have to create 3 views
thanks

Hi,
Using Aliases is a better way to increase performace. You can refer the Vanilla RPD. Aliases are extensively used ther.
Thanks,
Imtiaz.

PL/SQL not supported in 8i

Hi everyone,
My company have recently sent me on the Oracle 10g PL/SQL course. I am now back at work, and my only problem is that at the moment, we are currently using Oracle 8i (although hoping to upgrade in the very near future!) ;o)
I have been searching to see if I could find any documentation which lists the commands, etc. that are new as of 9i onwards and therefore will not be supported in 8i. I have found lots of posts in which people ask for the new features and are directed towards the Oracle documentation which simply lists things like: Database security, Availability, Manageability, etc.
This is not what I am looking for, I was hoping there would be something which listed each version and the new commands, e.g. Version <version number, e.g. 9i> - <command, e.g. CASE> - <description of command>
(I use this as an example as I know the actual CASE command is not supported in 8i, and that you must use EXECUTE IMMEDIATE or DECODE)
So, I was wondering if anyone knew of anything like this? I hope you understand what I mean.
Thanks in advance!

The 9i New Features ddoes include an overview of the new stuff but I agree it's not comprehensive. It doesn't mention the neat-o PIPELINED function capability.
Also the other thing is some stuff that is listed as a 9i New Feature was actually backported to 8.1.7.4 e.g. Row level Security. So I suggest you, erm, suck it and see.
Good luck, APC

Why does PL/SQL not support 0 length strings?

Why does Trim(' ') return null instead of an empty string?
Why does '' return null instead of an empty string?
Because of this, LENGTH(Trim(' ')) returns null. And I want zero.
I ask because I'm cutting up a string and in other languages (even ones that support Null) when these techniques are used, I get a valid empty string.
Am I wrong in feeling that an empty string is the equivilent to a 0 in a numeric field and that null in a string is equivilent to null in a numeric field?
Andy

For Oracle, by definition, a null string is a string of length 0 since at least Oracle 5.0 (i do not know the previous ones).
use NVL
Why does Trim(' ') return null instead of an empty string?
Why does '' return null instead of an empty string?
Because of this, LENGTH(Trim(' ')) returns null. And I want zero.
I ask because I'm cutting up a string and in other languages (even ones that support Null) when these techniques are used, I get a valid empty string.
Am I wrong in feeling that an empty string is the equivilent to a 0 in a numeric field and that null in a string is equivilent to null in a numeric field?
Andy

Different rows of a view in Physical Layer and Presentation Services

Hi all
From Administration tool you I have the view <View_Name> which has 3165 rows after Update Rows command.
The same number of rows is even when i make a simple select in TOAD:
Select count(*) from <View_Name>
The simple report has only three fields on Presentation Layer:
Asset Id-----Asset Number----------------Asset Description
This report displays 3101 rows.
I have done Reload Server Metadata, but no changes. Please help me to solve this issue.
Regards

Hi Sutirtha Roy
The problem seems in OWB because from here i can no see the rows in Presentation Service.
Or am I wrong??
Regards

View Camera Raw files fine in Browser, but image not supported in Viewer

Hi,
I have a Canon EOS 20D camera and shoot in RAW format nearly all of the time. When I import those photos into Aperture 2.0.1 they import fine and all appear in the Browser window no problem. However, when I want to see them in the Viewer, either by double clicking a photo in the browser, or by having my monitor display both the Browser and the Viewer at the same time, the photo cannot be seen in the Viewer. I get "Unsupported Image Format" on the screen. Meanwhile, even if the Browser is on screen at the same time, the photos appear fine there.
Any ideas?
thanks

Two things you could try:
A) Re-build your library (hold down Alt + Command while starting Aperture).
B) Re-generate your perviews (hold down Alt while clicking the menu "Images", select "Generate Previews for Project).
Karsten

How to add a stand alone table from Physical layer to Business Model

Hi,
I have tables from 2 different database sources in my Physical Layer.
My Business model currently uses only tables from one database. from my second database in teh physical layer I need only one table and that will be a stand alone table, to my Presentation layer.
1. Does it have to go through my Business layer or can it be directly added to the Presentation layer. What are the steps?
2. Can I restrict the permissions on that stand alone table only to the administrator?
Thank you.

1)create a view with single column using the sql (select 1 from dual) in physical layer and join it with the table using complex join in physical layer (1=1).
Move that to BMM, set the column as key in both physical and bmm layer.
2) You can restrict the access for the table presentation layer
Double click the presentation layer table -> Permission -> there you can restrict the access by user or group
Thanks,
Vino

Physical Layer Joins

I am creating a data model from a database that is in 3rd Normal Form. My understanding in the physical layer I should make the joins based on the relation between tables. I have a CUSTOMER & ADDRESS table and I understand that my join will be 1:M here since 1 Customer can have many addresses. However I would like to get all my facts from the CUSTOMER table so since this is going to be the fact table should the Many end of the join be at the CUSTOMER table. I have been given much misinformation about this and have 2 scenarios but do not know which is correct.
Scenario #1: Model the joins in the physical layer as 1:M e.g 1 Customer has many Addresses and then reverse the joins in the BMM to make the CUSTOMER table a fact table.
Scenario #2: Model the joins in the physical layer making the M (Many) side of the join on the Customer table therefore choosing it as a fact table in the physical layer.
Thanks in advance for any answer.

So if I understand correctly then the join in the physical layer will look like this: CUSTOMER------------->ADDRESSES. Is this because the CUSTOMER table is going to be the fact table. I thought the relationship between Customer and Addresses is a 1:M i.e. 1 Customer has many addresses. Why do we not model this in the Physical Layer.

Data account not supported

Cant get cell data on iPad, I started a data plan with AT&T but get "your account does not support the view acct feature h5006"
AT&T says I need to download newest iTunes to iPad, what gives?

can anyone tell me what could be the problem?TOAD
Cheers, APC

Can't see the update to the DB mapped in physical layer of the Admin tool

Hello everybody!
I have an Access DB that i'm using to create a temporary data model for OBIEE.
When i update rows (add or erase rows in the tables) i can see them in the physical layer; instead if i add o remove table i don't see any variation on the Physical layer.
I restarted the OBIserver services and checked the ODBC that point to the access. Everything's ok!
Should i remapped the DB everytime i make the a varition in the number of the table in the DATABASE?
Can you give some help please!
Regards.

1.If you drop or create new tables, you would not see them in the physical layer.
2. The RPD is just metadata and not database.
3.BI server has nothing to do with the physical layer modeling
4. yes you need to remap (in physical) the new tables you create and the ones you drop.
:-)

Complex join in physical layer

Hi Experts,
In which scenarios we will use complex join in physical layer i saw in many blogs that when we are using expressions and other than equality.
For better under standing can any one post few scenarios on this.
Regards,
Rafi

Hi,
Always use “Foreign Key” joins, not “Complex Joins” on the Physical Layer
Refer-http://obiee101.blogspot.com/2011/10/obiee11g-golden-rules-rpd-physical.html
If your join looks like D_DATE = TRUNC(S_DATETIME) try add a extra column S_DATE in your DWH. Any matching processing done by the BI-server costs time and you often loose the advantage of an index in your DWH.
For all others relationships other than a Primary Key-Foreign Key Relationships (expression other than equal to perform an equi join), you have to use a complex join otherwise you have to use a foreign key

SQL Server Reporting Services SharePoint Integrated mode - Power View is not supported

Hi there,
My environment is the following:
SharePoint Server 2013
SQL Server 2012 SP1 Enterprise edition
I am getting the following message when trying to open BISM item with PowerView icon:
"The feature: "Power View" is not supported in this edition of Reporting Services."
My problem is that the first time I installed SQL Server Reporting Services SharePoint integrated, I used the SQL Server 2012 Standard edition ISO. But then I learned that Power View is only available with Enterprise and BI editions. So I uninstalled Reporting
Services Add-in from Control Panel, Reporting Services from the installation media and deleted the three Reporting DBs in the SharePoint DB server.
Then I used SQL Server 2012 SP1 Enterprise media to install again Reporting Services but not sure why I am still getting the message:
"The feature: "Power View" is not supported in this edition of Reporting Services."
Anyone can advice me what could be the problem? Maybe I have not complete deleted the previous SQL Server Reporting Service Share Point integrated mode from the previous installation? What would be the proper way to uninstall Reporting Services?
Any help will be welcome.
Thanks and best regards,
Joss

Hi Joss,
I am in the same situation,
SQL Server was installed in the standard mode because of that the powerview option is not working.
I have changed teh edition using maintenance --> upgrade edition. the sql server components like DB engine, SSAS and integration services are now showing in enterprise edition. The reporting services are installed from the application end still showing
as the reporting services are standard.
we reinstalled the reporting services but still persists the issue.
suggest me is there any work around to fix the issue other than reinstalled the whole SQL Server.
Thanks
Ramu

Sql not supported in view in physical layer

Similar Messages

Maybe you are looking for