11g Physical Table Properties: "Parallel" misses "no selection"

Hi,
in 4.0.0.833 the generated SQL for a table has no "NOPARALLEL" clause, if you select "NO" in the 11g Physical Table Properties.
I think it should be empty/yes/no (like e.g. "logging") and generated the clauses accordingly.
See parallel_clause in the docs.
Best regards,
Blama

Hi Blama,
The NOPARALLEL clause is not normally generated as it is the default.
If you set the "Include default settings in DDL" option in the Data Modeler/DDL Preferences, the NOPARALLEL clause will be generated.
LOGGING is treated differently as it does not have such a well-defined default. If the LOGGING or NOLOGGING clause is not specified for a Table, it defaults to the Logging specified for the relevant Tablespace.
The "empty" option here indicates use the default for the Tablespace.
Regards,
David

Similar Messages

Table Type Stored Procedure in OBIEE Physical table properties

Hi,
Any one has ever used the Stored Procedure in OBIEE Physical table properties??
I've a procedure & a table i want to plopulate the tabel using the Procedure from OBIEE physical layer.

It would be nice if we know more details about 'Populating table'...
Using connection pool->connection pool scripts tab you may go for inserting/updating (Populating table) records into table.
It would be nice if you use dedicated connection pool for init blocks...
Ex: I want to insert user login time some xyz table my query would be like
insert into xyz values ('valueof(NQ_SESSION.USER)',sysdate)
without knowing your requirements its hard to tell anything apart from what is said.
If helps pls mark
Edited by: Srini VEERAVALLI on Jan 16, 2013 10:37 PM

DW CS3 Table properties partly missing

The bottom of my table properties window is cut off just
below the top of set bg image field. resizing does not help......
A bug maybe...
windows version

In the bottom-right corner of the properties window is a
triangle used
to expand and contract the size of that window.
HTH,
Randy
> The bottom of my table properties window is cut off just
below the top of set bg image field.

Using case when statement in the select query to create physical table

Hello,
I have a requirement where in I have to execute a case when statement with a session variable while creating a physical table using a select query. let me explain with an example.
I have a physical table based on a select table with one column.
SELECT 'VALUEOF(NQ_SESSION.NAME_PARAMETER)' AS NAME_PARAMETER FROM DUAL. Let me call this table as the NAME_PARAMETER table.
I also have a customer table.
In my dashboard that has two pages, Page 1 contains a table with the customer table with column navigation to my second dashboard page.
In my second dashboard page I created a dashboard report based on NAME_PARAMETER table and a prompt based on customer table that sets the NAME_ PARAMETER request variable.
EXECUTION
When i click on a particular customer, the prompt sets the variable NAME_PARAMETER and the NAME_PARAMETER table shows the appropriate customer.
everything works as expected. YE!!
Now i created another table called NAME_PARAMETER1 with a little modification to the earlier table. the query is as follows.
SELECT CASE WHEN 'VALUEOF(NQ_SESSION.NAME_PARAMETER)'='Customer 1' THEN 'TEST_MART1' ELSE TEST_MART2' END AS NAME_PARAMETER
FROM DUAL
Now I pull in this table into the second dashboard page along with the NAME_PARAMETER table report.
surprisingly, NAME_PARAMETER table report executes as is, but the other report based on the NAME_PARAMETER1 table fails with the following error.
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 16001] ODBC error state: S1000 code: 1756 message: [Oracle][ODBC][Ora]ORA-01756: quoted string not properly terminated. [nQSError: 16014] SQL statement preparation failed. (HY000)
SQL Issued: SET VARIABLE NAME_PARAMETER='Novartis';SELECT NAME_PARAMETER.NAME_PARAMETER saw_0 FROM POC_ONE_DOT_TWO ORDER BY saw_0
If anyone has any explanation to this error and how we can achieve the same, please help.
Thanks.

Hello,
Updates :) sorry.. the error was a stupid one.. I resolved and I got stuck at my next step.
I am creating a physical table using a select query. But I am trying to obtain the name of the table dynamically.
Here is what I am trying to do. the select query of the physical table is as follows.
SELECT CUSTOMER_ID AS CUSTOMER_ID, CUSTOMER_NAME AS CUSTOMER_NAME FROM 'VALUEOF(NQ_SESSION.SCHEMA_NAME)'.CUSTOMER.
The idea behind this is to obtain the data from the same table from different schemas dynamically based on what a session variable. Please let me know if there is a way to achieve this, if not please let me know if this can be achieved in any other method in OBIEE.
Thanks.

"Select" Physical table as LTS for a Fact table

Hi,
I am very new to OBIEE, still in the learning phase.
Scenario 1:
I have a "Select" Physical table which is joined (inner join) to a Fact table in the Physical layer. I have other dimensions joined to this fact table.
In BMM, I created a logical table for the fact table with 2 Logical Table Sources (the fact table & the select physical table). No errors in the consistency check.
When I create an analysis with columns from the fact table and the select table, I don't see any data for the select table column.
Scenario 2:
In this scenario, I created an inner join between "Select" physical table and a Dimension table instead of the Fact table.
In BMM, I created a logical table for the dimension table with 2 Logical Table Sources (the dimension table & the select physical table). No errors in the consistency check.
When I create an analysis with columns from the dimension table and the select table, I see data for all the columns.
What am I missing here? Why is it not working in first scenario?
Any help is greatly appreciated.
Thanks,
SP

Hi,
If I understand your description correctly, then your materialized view skips some dimensions (infrequent ones). However, when you reference these skipped dimensions in filters, the queries are hitting the materialized view and failing as these values do not exist. In this case, you could resolve it as follows
1. Create dimensional hierarchies for all dimensions.
2. In the fact table's logical sources set the content tabs properly. (Yes, I think this is it).
When you skipped some dimensions, the grain of the new fact source (the materialized view in this case) is changed. For example:
Say a fact is available with the keys for Product, Customer, Promotion dimensions. The grain for this is Product * Customer * Promotion
Say another fact is available with the keys for Product, Customer. The grain for this is Product * Customer (In fact, I would say it is Product * Customer * Promotion Total).
So in the second case, the grain of the table is changed. So setting appropriate content levels for these sources would automatically switch the sources.
So, I request you to try these settings and let me know if it works.
Thank you,
Dhar

Create physical table using select in repository

Hi Gurus,
Can we create Physical table in OBIEE 11.1.1.6 repository using stored procedure and select?
How is the right syntax?
Thank you so much
JOE

Hi,
Yes. physical layer just select and put it like below
for example,
select field1, field2, . field_n
from tables
UNION
select field1, field2, . field_n
from tables;
http://gerardnico.com/wiki/dat/obiee/opaque_view
http://www.clearpeaks.com/blog/oracle-bi-ee-11gusing-select_physical-in-obiee-11g
http://allaboutobiee.blogspot.com/2012/05/obiee-11g-deployundeploy-view-in.html
Thanks
Deva

OBIEE generated SQL differs if it's a Physical Table or Select Table...

Hi!
I have some tables defined in the Physical Layer, which some are Physical Tables and others are OBIEE "views" (tables created with a Select clause).
My problem is that the difference in the generated SQL for the same table, differs (as expected) whether it is a Physical Table or a "Select Table". And this difference originates problems in the returned data. When it a Physical Table, the final report returns the correct data, but when it is a Select Table it returns incorrect/incomplete data. The report joins this table with another table from a different Database (it is a join between Sybase IQ and SQL Server).
This is the generated SQL in the log:
-- Physical Table generated SQL
select T182880."sbl_cust_acct_row_id" as c1,
T182880."sbl_cust_acct_ext_key" as c2,
T182880."sbl_cust_source_sys" as c3
from
"SGC_X_KEY_ACCOUNT" T182880
order by c2, c3
-- "Select Table" generated SQL
select
     sbl_cust_acct_ext_key,
     ltrim(rtrim(sbl_cust_source_sys)) as sbl_cust_source_sys,
     sbl_cust_acct_row_id,
     sbl_cust_acct_camp_contact_row_id,
     ods_date,
     ods_batch_no,
     ods_timestamp
from dbo.SGC_X_KEY_ACCOUNT
As you may notice, the main difference is the use of Aliases (which I think that it has no influence in the report result) and the use of "Order By" (which I start to think that it its the main cause to return the correct data).
Don't forget that OBIEE server is joining the data from this table, with data from another table from a differente database. Therefore, the join is made in memory (OBIEE Engine). Maybe in the OBIEE Engine the Order by is essential to guarantee a correct join...but then again, I have some other tables in the Physical Layer that are defined as "Select" and the generated SQL uses the aliases and the Order by clause...
In order to solve my problem, I had to transform the "Select Table" into a "Physical Table". The reason it was defined as a "Select Table" was because it had a restriction in the Where Clause (which I eliminated already, althouth the performance wil be worse).
I'm confused. Help!
Thanks.
FPG

Hi FPG,
Not sure if this is a potential issue for you at all, but I know it caused me all kinds of headaches before I figured it out. Had to do with "Features" tab Values in the database object's settings in the Physical Layer:
Different SQL generated for physical table query vs. view object query?
Mine had to do with SQL from View objects not being submitted as I would expect, sounds like yours has more to do with "Order By"? I believe I remembered seeing some Order By and Group By settings in the "Features" list. You might make a copy of your RPD and experiement around with setting some of those if they aren't already selected and retesting your queries with the new DB settings.
Jeremy

Using variable in physical table of type "select"

Hello!
I have to use query as physical table (in Administration tool - http://file.qip.ru/file/120930377/8713693/1_online.html):
SELECT ID, CODE
FROM TABLE (pkg.output('1','2')) This code works well. I need to insert instead of parameters '1' and '2' session variables, which will be set from Dashboard.
How to put variable in this query? Variants like @{test} don't work.

Hi
I have a working example:
select * from table(get_emps('VALUEOF(NQ_SESSION.USER)'))
where
CREATE OR REPLACE FUNCTION GET_EMPS(P_USER VARCHAR2:='SUPPLIER2')
RETURN EMP_TYPE_LIST
IS
EMPS EMP_TYPE_LIST:=EMP_TYPE_LIST();
R EMP_TYPE:=EMP_TYPE(NULL,NULL,NULL,NULL,NULL);
i pls_integer:=0;
CURSOR C_EMP(C_USER EMPLOYEES.USER_ID%TYPE) IS
SELECT EMPLOYEE_ID,FIRST_NAME,LAST_NAME,SALARY ,USER_ID
FROM EMPLOYEES WHERE upper(USER_ID)=upper(C_USER);
BEGIN
OPEN C_EMP(P_USER);
LOOP
FETCH C_EMP INTO R.EMPLOYEE_ID,R.FIRST_NAME,R.LAST_NAME,R.SALARY,R.USER_ID;
EXIT WHEN C_EMP%NOTFOUND;
i:=i+1; emps.extend; EMPS(i):=R;
END LOOP;
RETURN EMPS;
END;
and
CREATE OR REPLACE TYPE EMP_TYPE AS OBJECT
EMPLOYEE_ID NUMBER(6),
FIRST_NAME VARCHAR2(20),
LAST_NAME VARCHAR2(25),
SALARY NUMBER(8,2),
USER_ID VARCHAR2(30));
and
CREATE OR REPLACE TYPE EMP_TYPE_LIST AS TABLE OF EMP_TYPE;
My employees table contains an extra column, called user_id, which has different values: 'Administrator','SUPPLIER2' and so on
Best regards
Laszlo

Creating Physical table as select in the .rpd

When creating a physical table as a select we can write the SQL statement like SELECT A,B,C... FROM xxx etc.
Trouble is that we then have to go the tab COLUMNS and define each column... This is kind of very error prone and lots of work...
Pls. is there a way to somehow leverage the columns alreaday defined in the PHYSICAL TABLE ?
Txs. for any help.
Antonio

Hi Antonio,
You didnt catch me..
1)Open actual rpd and create a view using select query, do not add any columns.
2) Create view in dev db.
3) Create a new rpd file import the view into the physical layer.
4) Select columns from step3 and copy
5) paste in the actual rpd on selecting the 'select query' object
you are good to go.
This wold help you with all columns and their datatypes.
Hope this helps.
Cheers,
SVee

Physical tables - table type 'select' query

Hello,
I've been playing around with the migrateEUL tool and have noticed that all Discoverer custom folders get translated into Physical Tables with a table type of 'select' as I would expect.
What I'm not sure about is the location in which it places these objects.
With a database data source called 'Video Store Tutorial' at the top level, a Physical Schema of VIDEO5 gets created. Inside this Physical Schema are the regular tables. The 'select' tables are placed as siblings to the Physical Select folder, and not as a child object like the rest of the tables.
Can someone please comment on what is the best practice regarding locating these 'select' tables (as children of the Physical Schema or children of the Database).
If I create a new table of table type 'select' I can only do so by right clicking the Physical Schema and choosing 'New Physical Table', thereby making this new object a child of the schema. I cannot make it a child of the database directly - although I can drag the object out from within the Physical Schema and drop it on the database name, to make it so.
Cheers,
John

Hi John,
There not really an absolut truth for this. Normaly you would make 'single schema' view siblings of there physical schema and 'multi schema' views direct siblings. It doesn't influence performances if they use the same connection pool. It's just a matter of taste.
regards
John
http://obiee101.blogspot.com/

SDDM 4.1 - Physical Storage Properties Not Appearing in DDL

I have only had this problem while using 4.1, not 4.0. In Tools > Preferences > Data Modeler > DDL if have the "Include Storage in DDL" box checked, and I have a Storage Template assigned to my table in my physical model. However, when I preview my table's DDL, I do not see any of the physical storage properties included. This has not always been the case in 4.1. The first time I noticed that the storage properties did not appear, I closed SDDM and reopened it. This fixed my problem temporarily, but now I cannot get the storage properties to appear at all. Is this a bug with SDDM 4.1? Or am I doing something wrong? I did not have this problem in 4.0.

Hi,
A few things to check:
1. The Physical Model that will be used in the DDL Preview is the one shown on the RDBMS Site property on the General tab of the Model Properties dialog for the Relational Model.
(Right click on the entry for the Relational Model in the Browser and select Properties.)
This gets updated whenever you do a full DDL Generation to refer to the Physical Model used in that DDL Generation. (It's initial default value for a new Relational Model is Oracle Database 11g.)
Make sure that this refers to the relevant Physical Model. Update it if necessary.
2. The relevant Physical Model must be open when you do the DDL Preview.
3. As well as the "Include Storage in DDL" option there are additional options for each individual storage clause.
These appear on the Data Modeler > DDL > DDL/Storage page of the Preferences. The relevant options here need to be checked as well.
If there still seems to be a problem, please let us know, together with any extra details you can provide.
Thanks,
David

Physical Table (Dynamic Name) x Physical Table x Alias

Hello,
We are customizing the standard OBI Applications .rpd. but this question is in reference to OBIEE, hence the post here.
I have no problems with Physical Tables and Alias in the Physical layer.
It just happens that the standard OBI Applications .rdp has some other 'physical tables' - the one for: Dim_W_PARTY_ORG_D_Customer that in its properties uses a Dynamic Name pointing to a variable that contains W_PARTY_ORG_D.
There are other similar cases in the vanilla .rpd
I fail to understand why sometimes (most of the time) the vanilla .rpd uses Alias and in these few cases use this strange Physical table. Pls. anyone would care to comment ?
As we expand W_PARTY_ORG_D with new columns... these new columns are NOT automatically part of the Dim_W_PARTY_ORG_D_Customer as it happens in an Alias definition.
Txs. for any comments.
Antonio

Hi Antonio,
From the 11g documentation (http://docs.oracle.com/cd/E14571_01/bi.1111/e10540/physicallayer.htm#i1005872) ;
Select this option to use a session variable to specify the physical table name, similar to catalog and schema objects. This option is available for non-multidimensional data source tables when you select a table type of Physical Table.
You might want to choose this option if you have a multi-tenancy implementation and you want to define a separate physical table name for each customer. Another example would be to select between primary and shadow tables that are valid at different times in your ETL cycle. In both cases, you can assign session variables to dynamically select the appropriate table.
Hope this helps.
Daan Bakboord
http://obibb.wordpress.com

Oracle 11g - External Table Issue?

Oracle 11g - External Table Issue?
=====================
I hope this is the right forum for this issue, if not let me, where to go.
We are using Oracle 11g (11.2.0.1.0) on (Platform : solaris[tm] oe (64-bit)), Sql Developer 3.0.04
We are trying to use oracle external table to load text files in .csv format. Here is our data look like.
======================
Date1,date2,Political party,Name, ROLE
20-Jan-66,22-Nov-69,Democratic,"John ", MMM
22-Nov-70,20-Jan-71,Democratic,"John Jr.",MMM
20-Jan-68,9-Aug-70,Republican,"Rick Ford Sr.", MMM
9-Aug-72,20-Jan-75,Republican,Henry,MMM
------ ALL NULL -- record
20-Jan-80,20-Jan-89,Democratic,"Donald Smith",MMM
======================
Our Expernal table structures is as follows
CREATE TABLE P_LOAD
DATE1 VARCHAR2(10),
DATE2 VARCHAR2(10),
POL_PRTY VARCHAR2(30),
P_NAME VARCHAR2(30),
P_ROLE VARCHAR2(5)
ORGANIZATION EXTERNAL
(TYPE ORACLE_LOADER
DEFAULT DIRECTORY P_EXT_TAB_D
ACCESS PARAMETERS (
RECORDS DELIMITED by NEWLINE
SKIP 1
FIELDS TERMINATED BY "," OPTIONALLY ENCLOSED BY '"' LDRTRIM
REJECT ROWS WITH ALL NULL FIELDS
MISSING FIELD VALUES ARE NULL
DATE1 CHAR (10) Terminated by "," ,
DATE2 CHAR (10) Terminated by "," ,
POL_PRTY CHAR (30) Terminated by "," ,
P_NAME CHAR (30) Terminated by "," OPTIONALLY ENCLOSED BY '"' ,
P_ROLE CHAR (5) Terminated by ","
LOCATION ('Input.dat')
REJECT LIMIT UNLIMITED;
It created successfully using SQL Developer
Here is the issue.
It is not loading the records, where fields are enclosed in '"' (Rec # 2,3,4,7)
It is loading all NULL value record (Rec # 6)
*** If we remove the '"' from input data, it loads all records including all NULL records
Log file has
KUP-04021: field formatting error for field P_NAME
KUP-04036: second enclosing delimiter not found
KUP-04101: record 2 rejected in file ....
Our questions
Why did "REJECT ROWS WITH ALL NULL FIELDS" not working?
Why did Terminated by "," OPTIONALLY ENCLOSED BY '"' not working?
Any idea?
Thanks in helping.
Edited by: qwe16235 on Jun 10, 2011 2:16 PM

The following worked for me:
drop table p_load;
CREATE TABLE P_LOAD
DATE1 VARCHAR2(10),
DATE2 VARCHAR2(10),
POL_PRTY VARCHAR2(30),
P_NAME VARCHAR2(30),
P_ROLE VARCHAR2(5)
ORGANIZATION EXTERNAL
(TYPE ORACLE_LOADER
DEFAULT DIRECTORY scott_def_dir1
ACCESS PARAMETERS (
RECORDS DELIMITED by NEWLINE
badfile scott_def_dir2:'p_load_%a_%p.bad'
logfile scott_def_dir2:'p_load_%a_%p.log'
SKIP 1
FIELDS TERMINATED BY "," OPTIONALLY ENCLOSED BY '"' LDRTRIM
MISSING FIELD VALUES ARE NULL
REJECT ROWS WITH ALL NULL FIELDS
DATE1 CHAR (10) Terminated by "," ,
DATE2 CHAR (10) Terminated by "," ,
POL_PRTY CHAR (30) Terminated by "," ,
P_NAME CHAR (30) Terminated by "," OPTIONALLY ENCLOSED BY '"' ,
P_ROLE CHAR (5) Terminated by ","
LOCATION ('Input.dat')
REJECT LIMIT UNLIMITED;
Note that I had to interchange the two lines:
MISSING FIELD VALUES ARE NULL
REJECT ROWS WITH ALL NULL FIELDS
Just to get the access parameters to parse correctly.
I added two empty lines, one in the middle and one at the end - both were rejected.
In the log file, you will see the rejectiions:
$ cat p_load_000_9219.log
LOG file opened at 07/08/11 19:47:23
Field Definitions for table P_LOAD
Record format DELIMITED BY NEWLINE
Data in file has same endianness as the platform
Reject rows with all null fields
Fields in Data Source:
DATE1 CHAR (10)
Terminated by ","
Enclosed by """ and """
Trim whitespace same as SQL Loader
DATE2 CHAR (10)
Terminated by ","
Enclosed by """ and """
Trim whitespace same as SQL Loader
POL_PRTY CHAR (30)
Terminated by ","
Enclosed by """ and """
Trim whitespace same as SQL Loader
P_NAME CHAR (30)
Terminated by ","
Enclosed by """ and """
Trim whitespace same as SQL Loader
P_ROLE CHAR (5)
Terminated by ","
Enclosed by """ and """
Trim whitespace same as SQL Loader
KUP-04073: record ignored because all referenced fields are null for a record
KUP-04073: record ignored because all referenced fields are null for a record
Input Data:
Date1,date2,Political party,Name, ROLE
20-Jan-66,22-Nov-69,Democratic,"John ", MMM
22-Nov-70,20-Jan-71,Democratic,"John Jr.",MMM
20-Jan-68,9-Aug-70,Republican,"Rick Ford Sr.", MMM
9-Aug-72,20-Jan-75,Republican,Henry,MMM
4-Aug-70,20-Jan-75,Independent
Result:
SQL> select * from p_load;
DATE1 DATE2 POL_PRTY P_NAME P_ROL
20-Jan-66 22-Nov-69 Democratic John MMM
22-Nov-70 20-Jan-71 Democratic John Jr. MMM
20-Jan-68 9-Aug-70 Republican Rick Ford Sr. MMM
9-Aug-72 20-Jan-75 Republican Henry MMM
Regards,
- Allen

OBIEE 10g repository - Business model - logical table to physical table, column mapping is empty

Hi, I am really new to OBIEE 10g.
I already set up a SQL Server 2005 database in Physical and import a view vw_Dim_retail_branch.
The view has 3 columns: branch_id, branch_code, branch_desc.
Now I want to set up the Business model to map this physical table (view).
I created a new Business model
Added new logical table Dim_retail_branch
In the sources, added the vw_Dim_retail_branch as source table.
But in the Logical table source window, column mapping tab, it's blank. I thought it should be able to identify all the columns from vw_Dim_retail_branch, but not. The show mapped columns is ticked.
What should I do here? Manually type each column?

HI,
Just you can drag and drop the columns from physical layer to BMM layer.
Select the 3 columns and drag and drop it to the created logical column in BMM layer.
for more reference : http:\\mkashu.blogspot.com
Regards,
VG

AS: setting table properties in ID CS3 invokes odd error message

I'm converting an InDesign CS2 script to CS3 and am having the strangest error. This code used to work in ID CS2 for the selected text frame:
>tell parent story of insertion point 1 of selection
>set theTable to make table with properties {width:gridColumnWidth, body row count:totalGridRows, header row count:0, footer row count:0, column count:totalGridColumns, height:gridRowHeight, left border stroke weight:gridBorderWeight, right border stroke weight:gridBorderWeight, top border stroke weight:gridBorderWeight, bottom border stroke weight:gridBorderWeight, left border stroke type:"Solid", right border stroke type:"Solid", top border stroke type:"Solid", bottom border stroke type:"Solid", space after:0, space before:0}
>end tell
But now it chokes and gives me this strange error:
>Adobe InDesign CS3 got an error: Invalid value for set property 'height'. Expected number or string, but received 21.80909090909093.
Huh? That obviously has to be a number or string, so what's going on? What's even weirder is if I delete all the table properties except for weight and height, the script doesn't give the error. I know I can do this with a table style, but I'd like to understand what the problem is before I take that step.

Shane:
I was completely distracted by another project and am just getting back to addressing this problem. Sorry about that.
Anyway, your suggestion was a sound one: I set the width and height in the first statement, added everything else in a second statement, and it worked perfectly. Thanks! Any idea why I needed to do so?

11g Physical Table Properties: "Parallel" misses "no selection"

Similar Messages

Maybe you are looking for