Cardinality issue

Hello ,
I created a node emp and with attribute name in the component controller and gave the cardinality as 0..1 and selection 0:.1 .
and in the view i gave UI element Input_field for the attribute name.
But is giving dump when im executing with the follwoing message :
The following error text was processed in the system ARD : Adapter error in &VIEW_ELEMENT_TYPE& "IN" of view "YEXAMPLE.MAIN": Context binding of property VALUE cannot be resolved: Node MAIN.1.EMP does not contain any elements
Could you please say why im getting dump .
Also when im trying to give the cardinality as 0..n to also im gettting the dump.
Plesae give info about the same.
Edited by: meshack prasan appikatla on Jan 25, 2010 2:27 PM
Edited by: meshack prasan appikatla on Jan 25, 2010 2:30 PM

>
santosh.p wrote:
> hello thomas,
>
> But why is it required to have the Initial element . In the node there is only attribute name ?
>
> Can you please elaborate?
>
> Thanks
Without an element there is nothing for the UI element to bind to. It doesn't matter if you have one attribute or many - you still need an element for the binding to work. All data binding (even to the context root) technically must go through a context element.

Similar Messages

Cardinality Issue - WD Model (Form) Integration with BAPI

Hi -
We have an issue with our forms editable fields are getting disabled (read only, we can not enter data) even though we have proper properties set.
Our developers are looking into a possible cardinality issue i.e. our form fields are test field and have a cardinality of 0..1, where as our bapi structure is showing a cardinality of 0..n for the corresponding field in bapi.
We had internal table as an export parameter so we though may be because of that we are getting 0..n. However we have changed the internal table to a type of structure and recreated a model mapped all the controller and context nodes back to the new structure and still get 0..n cardinality.
We have already researched on SDN logs and did not find any relevant answers.
Any one have any idea please make our weekend happy Developers are really working hard on Friday to close on this before they go home.
Thanks
Shahid

Hi Shahid,
If the context node cardinality is 0...1 or 0...n then you need to first create or bind an element to the node to make the form fields editable to which those nodes are bound to. If it's a model node then you need to instantiate a new model node object and bind it to the node e.g.:
Bapi_xxx_Input input = new Bapi_xxx_Input();
wdContext.nodeBapi_xxx_Input().bind(input);
Or if it's a value node then you need to instantiate the node element as below:
wdContext.nodemyNode().addElement(wdContext.nodemyNode().createElement());
Hope this helps.
thanks,
Dipankar

Universe Cardinality Issues

Hi,
We have migrated BO 6.5 Oracle based universe to BO Xi R2 and noticed that there is different in count of divergences are not same between 6.5 and Xi R2. The underlying connection is exactly same.
Any thoughts this?
Please let me know how to fix this.
Thanks,
Sundar.

Hi ,
Please check if you are connected to the Same Database.
Regards
Prashant

Error in MDDataSetBW.GetCellData when Scheduling

Dear Experts,
We have a Web Intelligence report that refreshes in the Rich Client without a problem. If we try to schedule this report, we receive the following error message.
A database error occurred. The database error text is: Error in MDDataSetBW.GetCellData. FUNCTION_NOT_FOUND. (WIS 10901)
I've read the related SAP Note that says this is due to large data volumes, but it refreshes in the Rich Client fine. We've also restricted the WebI queries as much as we can and the underlying BEx query is also heavily restricted.
We're running BOE 3.1 SP2.
Any help to solve this problem will be massively appreciated,
Andrew

Hi Andrew,
Think is not million of records if cells if you have 10 dimensions and 100.000 records you will have this problem, because is million of cells.
How many dimension do you have in the query panel?
Other issue that I had with similar error number was related to LOV, and I solved this procedure:
1. check your Web Intelligence Processing Servers are enabled and running?
2. Does the user have the appropriate rights to the universe and connection underlying the report?
3. Do an integrity check on the Universe and resolve all cardinality issues from the migration.
Once all the integrity issues were resolved and the LOV's recreated u2013try to re-export the Universe, which will resolve the WIS errors.
4. check you have the Universes existing in the correct universe folders.
5. And also check the disk space.
Best regards,
praveen

Error MDDataSetBW.GetCellData (WIS 10901)

Hi all,
Iu2019m working with Business Objects series XI 3.1 and SAP BI. It give me the following error when I try to refresh a query in WebI after add on an additional characteristics. If remove that any characteristic, it works fine.
"...MDDataSetBW.GetCellData. See RFC trace file or SAP system log for more details. (WIS 10901)"
Please help me on this.
Regards,
Hizam

Hi Davis and Hizam,
Think is not million of records if cells if you have 10 dimensions and 100.000 records you will have this problem, because is million of cells.
How many dimension do you have in the query panel?
Other issue that I had with similar error number was related to LOV, and I solved this procedure:
1. check your Web Intelligence Processing Servers are enabled and running?
2. Does the user have the appropriate rights to the universe and connection underlying the report?
3. Do an integrity check on the Universe and resolve all cardinality issues from the migration.
Once all the integrity issues were resolved and the LOV's recreated u2013try to re-export the Universe, which will resolve the WIS errors.
4. check you have the Universes existing in the correct universe folders.
5. And also check the disk space.
Best regards,

How to Implement the OVS in a table

Hai
I want to implement a table with one column with OVS. But if I want to enable OVS, I can not create a table because of the cardinality of the node-element of the context.
My table Node cardinality is 0..n because we have many rows in a table.
i have introduced EVS in one column.it works fine.
Because We can not set our own inputfield or button in EVS Pop Up.
If we select the cardinality "1..1" the OVS works but the table only can have one row. If we select the cardinality "0..n" the table can have "n" rows but the OVS is disabled.
Did anybody implements a similar application? Please help
i got the following error
When i call WDValueServices.addOVSExtension with ovsStartupAttributes, do this error: MappedAttributeInfo ViewName): must not modify the datatype of a mapped attribute
Message was edited by:
        Dhinakaran Jeyachandran

Hi,
If you think it's cardinality issue thenchange it to 1:n.
Otherwise do like this.
Create a custom controller first say OVSCustomController
and do following things for a column:-
Add this controller in your view.
IPublicOVSCustomController.IContextNode ovsContext = wdThis.wdGetOVSCustomControllerController().wdGetContext();
Create input and output nodes for ovs.
IWDNodeInfo ovsInputNodeInfo = ovsNodeInfo.addChild(columnName+"Input",null,true, CMICardinality.ONE,CMICardinality.ONE_TO_MANY, true, null);
IWDNodeInfo ovsOutputNodeInfo = ovsNodeInfo.addChild(columnName+"OutPut",null,true, CMICardinality.ONE_TO_MANY,CMICardinality.ONE_TO_MANY, true, null);
Create Attributes for this field in the input and output nodes.
IWDAttributeInfo attrInputInfo = ovsInputNodeInfo.addAttribute(field,datatype of field);
IWDAttributeInfo attrOutputInfo = ovsOutputNodeInfo.addAttribute((relatedfield,datatype of field);
set the attribute Info array:-
IWDAttributeInfo[] attrInfoArray = new IWDAttributeInfo[1];
          attrInfoArray[0] = attribute info of the column
Now call the ovs service :-
WDValueServices.addOVSExtension("",attrInfoArray,ovsInputNode,ovsOutputNode,listener);
Your ivs window will be opened by this.
Feel free for any queries regarding this.
Regards,
Praveen
Message was edited by:
        Praveen Kumar Pandey
Message was edited by:
        Praveen Kumar Pandey

Making a webdynpro through Web Service| VERY URGENT

Hi ,
 I am having a problem in the scenario when I am trying to make a webdynpro application using a WSDL file . When I deploy the application in my first view which is a search view the field appears disabled and I am not able to input the values for the same .I have done the following ...
1) In my action search following is the code
public void onActionSearch(com.sap.tc.webdynpro.progmodel.api.IWDCustomEvent wdEvent )
 //@@begin onActionSearch(ServerEvent)
 wdThis.wdFirePlugToOutputView();
 wdThis.wdGetContactTestAgainController().executeSearch();
 //@@end
2) in the wdDoInit method of the component controller following is the code
public void wdDoInit()
 //@@begin wdDoInit()
 Request_Default_siebelContactQueryByExample input =
 new Request_Default_siebelContactQueryByExample();
 wdContext.nodeRequest_ByExample().bind(input);
 //@@end
3) In the execute search method following is the code
public void executeSearch( )
 //@@begin executeSearch()
 try
 wdContext.currentRequest_ByExampleElement().modelObject().execute();
 catch(Exception ex)
 wdContext.nodeResponse().invalidate();
 wdContext.nodeResult().invalidate();
 //@@end
The scenario is somewhat like this . There is a proxy class being generated while importing the model by the name "Request_Default_siebelContactQueryByExample" . This class has a list inside . The relevant code for this inside the above mentioned class is as follows
private java.util.List _listOfContactInterface;
public void setListOfContactInterface (java.util.List arg)
 this._listOfContactInterface = arg;
public java.util.List getListOfContactInterface ()
 return _listOfContactInterface;
public void setListOfContactInterface (com.test.last.proxies.types.Contact[] args)
 if(_listOfContactInterface == null) _listOfContactInterface = new java.util.ArrayList();
 if (args == null ) return ;
 for(int i=0;i<args.length;i++)
 com.test.last.ComplexType_Contact wrapper = new com.test.last.ComplexType_Contact ();
 wrapper.setOriginalBean(args);
 _listOfContactInterface.add(wrapper);
public com.test.last.proxies.types.Contact[] getListOfContactInterfaceAsArray ()
 if(_listOfContactInterface == null) return new com.test.last.proxies.types.Contact[]{};
 com.test.last.proxies.types.Contact[] ListOfContactInterfaceAsArray = new com.test.last.proxies.types.Contact[_listOfContactInterface.size()];
 for(int i=0;i<_listOfContactInterface.size();i++)
 com.test.last.ComplexType_Contact item = (com.test.last.ComplexType_Contact)_listOfContactInterface.get(i);
 ListOfContactInterfaceAsArray = item.getOriginalBean();
 return ListOfContactInterfaceAsArray ;
I think I have to do something to set the values for the input the parameters . There is a field "id" that I am taking as my input but I am not sure how to set this value from the list .May be this is the reason for the whole problem .
Also if there is a cardinality issue then I have checked the context for views and the controller for the same . The cardinality appears to be 0..n for the input model node and 0..1 for the output model node that I have created and in both the cases it appears to be non editable .
This is a very urgent issue and will highly appreciate a prompt reply .
Regards
Deepak Singh

Hi Deepak,
I was facing the same problem with my webservice, the problem is when u create a model for a webservice, u need to create a webservice through UDDI server. When u create model u will get three option :
1) Local Server
2) Local Server URL
3) UDDI Server URL
U need to select the 3rd option and importing of webservice should be
Import webservice (deprecated) if u are using NWDS version 13.
And also refer this document, and hope your question will answered ..
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/696f9c90-0201-0010-0abd-86c6c7454052
All the best
Regards,
Sameer Ali Khan

Tablespace with too many extents are evil for performance

I think the tablespace with too many extents are not bad for performance after introduction of LMT tablespace?? May be true with DMT tablespace(earlier versions). This is just observation after reading the LMT vs DMT tablespaces.
Experts - Please comment on your thoughts.

Indeed, I work in an environment where there is over 50 databases to be administered and so we have lots of DBAs interacting with each other.
I'm stunned by this myth of "reorganization". Most of the DBAs move tables + rebuild indexes regularly generating huge redo on a monthly basis. Also provoking indexes to do all the splits again generating even more redo. They claim "it helps performance a lot" however not one is able to quantify and quite justify it other than "less extents less I/O, good". Even when I bring up the existence of shrink they say "do not like it, prefer the classic move". People really have a way of holding on to their good ol' practices of Oracle 8i.
For full table scans (which should never be done on a OLTP scenario) this extent issue would be relevant IF data on the table is the victim of large deles and Oracle hasn't re-used that space yet. If your multiblock reads is a multiple of your extent size, than there won't be any overhead of I/O call, no matter the number of your extents. For OLTP this is not relevant because Oracle will access the table via ROWID.
I rarely have ever seen an index benefit from a rebuild significantly. In my experience what people often understand as "index fragmentation" is often just an unoptimized execution plan due to cardinality issues where oracle ends up fetching a large percentage of the table via single reads on that index.

Using Pipeline Table functions with other tables

I am on DB 11.2.0.2 and have sparingly used pipelined table functions but am considering it for a project that has some fairly big (lots of rows) sized tables. In my tests, selecting from just the pipelined table perform pretty well (whether it is directly from the pipleined table or the view I created on top of it). Where I start to see some degregation when I try to join the pipelined tabe view to other tables and add where conditions.
ie:
SELECT A.empno, A.empname, A.job, B.sal
FROM EMP_VIEW A, EMP B
WHERE A.empno = B.empno AND
      B.mgr = '7839'
I have seen some articles and blogs that mention this as a cardinality issue, and offer some undocumented methods to try and combat.
Can someone please give me some advice or tips on this. Thanks!
I have created a simple example using the emp table below to help illustrate what I am doing.
DROP TYPE EMP_TYPE;
DROP TYPE EMP_SEQ;
CREATE OR REPLACE TYPE EMP_SEQ AS OBJECT
       ( EMPNO                                         NUMBER(10),
         ENAME                                         VARCHAR2(100),
         JOB                                           VARCHAR2(100));
CREATE OR REPLACE TYPE EMP_TYPE AS TABLE OF EMP_SEQ;
CREATE OR REPLACE FUNCTION get_emp return EMP_TYPE PIPELINED AS
BEGIN
FOR cur IN (SELECT
                empno,
                ename,
                job
              FROM emp
         LOOP
           PIPE ROW(EMP_SEQ(cur.empno,
                            cur.ename,
                            cur.job));
         END LOOP;
         RETURN;
END get_emp;
create OR REPLACE view EMP_VIEW as select * from table(get_emp());
SELECT A.empno, A.empname, A.job, B.sal
FROM EMP_VIEW A, EMP B
WHERE A.empno = B.empno AND
      B.mgr = '7839'

I am on DB 11.2.0.2 and have sparingly used pipelined table functions but am considering it for a project that has some fairly big (lots of rows) sized tables
Which begs the question: WHY? What PROBLEM are you trying to solve and what makes you think using pipelined table functions is the best way to solve that problem?
The lack of information about cardinality is the likely root of the degradation you noticed as already mentioned.
But that should be a red flag about pipelined functions in general. PIPELINED functions hide virtually ALL KNOWLEDGE about the result set that is produced; cardinality is just the tip of the iceberg. Those functions pretty much say 'here is a result set' without ANY information about the number of rows (cardinality), distinct values for any columns, nullability of any columns, constraints that might apply to any columns (foreign key, primary key) and so on.
If you are going to hide all of that information from Oracle that would normally be used to help optimize queries and select the appropriate execution plan you need to have a VERY good reason.
The use of PIPELINED functions should be reserved for those use cases where ordinary SQL and PL/SQL cannot get the job done. That is they are a 'special case' solution.
The classic use case for those functions is for the transform stage of ETL where multiple pipelined functions are chained together: one function feeds its rows to the next function which feeds its rows to another and so on. Each of those 'chained' functions is roughly analogous to a full table scan of the data that often does not need to be joined to other data except perhaps low volumn lookup tables where the data may even be cached.
I suggest that any exploratory or prototyping work you do use standard relational tables until such point as you run into a problem whose solution might require PIPELINED functions to solve.

Urgent! 500 internal server error

Good afternoon,
When i run other interactive forms , it show successfully on the adobe forms however, when i run my project , it show :
500 Internal Server Error
Failed to process request. Please contact your system administrator.
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
The initial exception that caused the request to fail, was:
 com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentRuntimeException: Severe : PDFDocument is NULL. Exception : Bound data node Node(InvoiceSummary.InvoiceDetail) of InteractiveForm must not be empty!
 at com.sap.tc.webdynpro.clientserver.uielib.adobe.impl.InteractiveForm.afterHandleActionEvent(InteractiveForm.java:385)
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.afterApplicationModification(ClientApplication.java:1117)
 at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.afterApplicationModification(ClientComponent.java:887)
 at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doRespond(WindowPhaseModel.java:573)
 at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:152)
 ... 25 more
Currently using java webdynpro version 7.0.7, adobe live designer 7
Can any one help me? Thanks .... reward point will be awarded ...

Hi Lin,
The DataSource node,u have bound to the Interactive form is not initialized .Initialize the DataSource node in wdDoInit method.
e.g
InvoiceDetail detail = new InvoiceDetail();
wdContext.nodeInvoiceDetail().bind(detail);
Just check the above, if it works.
It could also be a Cardinality issue. If the above doesn't work make the cardinality as 1..n and also make sure that u need to give values in the pdf.
If you have bound the datasource property of the interactive form UI element to a node,make sure that it should not be null,you need to fill data in the fields and try to display the output.
Hope this helps.

Data Modelling in DW

Hi:
I have a Dim table - Dim_TblA with hierarchies setup as R->S->T (T being the lowest level of granularity)
I need to build an Aggregate table with some KPI's for reporting purpose (at a granularity level T)
Should I include R, S and T in the new table or can I include a Key (Foreign Key) to the Dim table Dim_TblA
Any pros / cons list will be very helpful.
Thanks

Hi,
Key figures represent the Fact table and hence there is no dimension for them . They are just key figures.
One should not group them in such are way as to produce a very large cardinality of that dimension. Remember the old rule: if every customer buys every product, never put customer and product in the same dimension The SID for the dimension gets huge, degrading query performance.
Example:
1000 customers x 1000 products = 1,000,000 SIDs in the same dimension
1000 customers + 1000 products = 2,000 SIDs if put in different dimensions.
If there are no cardinality issues, group the custom characteristic where it makes logical sense:
For example: something relating to versioning along with other similar chars like 0VERSION, 0VTYPE.
Something relating to material along with material, and so on.
Query tuning is highly related to good cube design, and the old principles should not be compromised
Hope this helps.
Regards
Amol

Need help on curosr

Hi ALL,
 Am getting an error when using a ref cursor. Like I need to insert some
 values into a table from a one function to another function insert statment.
 In process_payer function the ref cursor named g_r_payer_flat is populating values thru the
 select query, from that i need 4 values (payer_id, destination, product_type,customer_id)
 to be inserted into the another function write_tax_info.
 When i tried the below way i encountering the below error.
 "PLS-00302: component 'V_PAYERID' must be declared" on the insert stament of the function write_tax_info.
 Please advice me where am doing wrong.
CREATE OR REPLACE PACKAGE BODY FUNCTIONAL
AS
 type g_r_payer_flat is REF CURSOR;
FUNCTION process_payer
 (p_bill_date IN VARCHAR2 )
 RETURN INTEGER
IS
i_period Number := 0;
v_return_val integer;
d_flatFee number(10,4);
v_endDate varchar2(8);
v_clientId tax_era_client.client_id %type;
v_flatFeePeriod price_schedule.price_period %type;
v_eracnt era_claims.era_count %TYPE;
v_description product_type.description %type;
v_customerId payer_schedule.customer_id %type;
v_payerId payer_master.payer_id %type;
v_destination payer_master.destination %type;
v_subsystemCode payer_master.SUBSYSTEM_CODE %type;
v_productType product_type.product_type %type;
v_lastBillDate varchar2(9);
i_flatFeePeriod number;
v_flatFeePeriodUnit varchar2(2);
l_scheduleId payer_schedule.schedule_id %type;
i_acctgCode pre_staging.acctg_code %type;
/* Set up the cursor for the payer schedule - flat fees. */
 CURSOR g_r_payer_flat
 IS
 SELECT ps.payer_id ,
 ps.destination ,
 NVL (ps.customer_id, '000000000')as customer_id,
 ps.schedule_id ,
 ps.product_type ,
 TO_CHAR (NVL (ps.last_bill_date, TO_DATE (TO_CHAR (ADD_MONTHS (SYSDATE, -1), 'YYYYMM'), 'YYYYMM') ), 'YYYYMM')
 AS last_bill_date,
 NVL (pt.description, ' ') description,
 NVL (pt.acctg_code, 4010) acctg_code,
 pr.price AS price,
 pr.price_period,
 pr.price_period_unit AS price_period_unit,
 pm.subsystem_code,
 NVL (TO_CHAR (ps.grace_period_end_date, 'YYYYMM'), '200808') AS grace_period_end_date
 FROM payer_schedule ps,
 product_type pt,
 price_schedule pr,
 payer_master pm
 WHERE ps.product_type = pt.product_type
 AND ps.schedule_id = pr.schedule_id
 AND ps.payer_id = pm.payer_id
 AND ps.destination = pm.destination
 AND ps.bill_code = 'A' ;
 --AND pr.price_type IN ('A', 'F', 'I', 'M'); commented since data needs to be setup
BEGIN
 var_line := 'PAYER_ID' || ',' ||
 'DESTINATION' || ',' ||
 'CUSTOMER_ID' || ',' ||
 'SCHEDULE_ID' || ',' ||
 'PRODUCT_TYPE' || ',' ||
 'LAST_BILL_DATE' || ',' ||
 'DESCRIPTION' || ',' ||
 'ACCTG_CODE' || ',' ||
 'PRICE' || ',' ||
 'PRICE_PERIOD' || ',' ||
 'PRICE_PERIOD_UNIT' || ',' ||
 'SUBSYSTEM_CODE' || ',' ||
 'GRACE_PERIOD_END_DATE';
 UTL_FILE.PUT_LINE(var_out_file_handler, var_line);
 FOR r_payer_flat_cur IN g_r_payer_flat LOOP
 FETCH g_r_payer_flat
 INTO
 v_payerId,
 v_destination,
 v_customerId,
 l_scheduleId,
 v_productType,
 v_lastBillDate,
 v_description,
 i_acctgCode,
 d_flatFee,
 i_flatFeePeriod,
 v_flatFeePeriodUnit,
 v_subsystemCode,
 v_endDate;
 i_period := i_flatFeePeriod;
 IF r_payer_flat_cur.grace_period_end_date <= p_bill_date THEN
 cbsutil.lg.stat ( 'Grace Period for payer '
 || r_payer_flat_cur.payer_id
 || ' dest '
 || r_payer_flat_cur.destination
 || ' product '
 || r_payer_flat_cur.product_type
 || ' until '
 || r_payer_flat_cur.grace_period_end_date);
 ELSIF r_payer_flat_cur.price_period_unit IN ('D', 'W') THEN
 cbsutil.lg.stat ( 'Period Unit of D/W for payer '
 || r_payer_flat_cur.payer_id
 || ' dest '
 || r_payer_flat_cur.destination
 || ' product '
 || r_payer_flat_cur.product_type
 || ' Skipping');
 ELSIF r_payer_flat_cur.price_period_unit = 'O'
 AND r_payer_flat_cur.last_bill_date = p_bill_date THEN
 cbsutil.lg.stat ( 'Period Unit of O but has NULL or CURRENT date '
 || r_payer_flat_cur.payer_id
 || ' dest '
 || r_payer_flat_cur.destination
 || ' product '
 || r_payer_flat_cur.product_type
 || ' Skipping');
 ELSIF r_payer_flat_cur.price_period_unit = 'Y'
 AND r_payer_flat_cur.last_bill_date <> p_bill_date THEN
 cbsutil.lg.stat ( 'Period Unit of O but has NULL or CURRENT date '
 || r_payer_flat_cur.payer_id
 || ' dest '
 || r_payer_flat_cur.destination
 || ' product '
 || r_payer_flat_cur.product_type
 || ' Skipping');
 ELSE
 NULL;
 END IF;
 v_return_val := write_invoice_item(r_payer_flat_cur.price, 1);
 DBMS_OUTPUT.PUT_LINE('v_return_val in process_payer write_invoice_item'||' '||v_return_val);
 IF v_return_val = 1
 THEN
 RETURN RET_ERR;
 END IF;
 v_return_val := write_tax_info(r_payer_flat_cur.price, 1, r_payer_flat_cur.price, 'P');
 DBMS_OUTPUT.PUT_LINE('v_return_val in process_payer write_tax_info'||' '||v_return_val);
 IF v_return_val = 1
 THEN
 RETURN RET_ERR;
 END IF;
 IF NOT update_last_bill_date (r_payer_flat_cur.customer_id, r_payer_flat_cur.schedule_id, r_payer_flat_cur.product_type)
 THEN
 var_line := 'Error updating last bill date for: '
 || r_payer_flat_cur.payer_id
 || ' dest '
 || r_payer_flat_cur.destination
 || ' product '
 || r_payer_flat_cur.product_type;
 END IF;
 UPDATE payer_schedule
 SET last_bill_date = last_day(to_date(p_bill_date, 'YYYYMM'))
 WHERE payer_id = v_payerId
 AND destination = v_destination
 AND product_type = v_productType;
END LOOP;
CLOSE g_r_payer_flat;
/* Open the cursor payer */
 FOR r_payer IN c_payer LOOP
 -- IF process_payer_items(p_bill_date,v_eracnt) > 0 THEN
 NULL;
 -- END IF;
 END LOOP;
--CLOSE r_payer;
return RET_OK;
 UTL_FILE.PUT_LINE(var_out_file_handler, var_line);
 UTL_FILE.FCLOSE(var_out_file_handler); -- final file close
EXCEPTION
 WHEN NO_DATA_FOUND THEN
 RAISE_APPLICATION_ERROR(-20003, 'A NO DATA FOUND ERROR HAS OCCURED : '|| SQLCODE || ' ' || SQLERRM );
END process_payer; /* End process_payer function */
FUNCTION write_tax_info (
 P_UNITPRICE IN NUMBER,
 P_UNITCNT IN NUMBER,
 P_TOTAL_AMT IN NUMBER,
 P_TYPE IN VARCHAR
 RETURN INTEGER
IS
 d_totalamt NUMBER;
 d_workunitprice NUMBER;
 v_payerId payer_master.payer_id %type;
 v_destination payer_master.destination %type;
 v_preacctgcustid pre_staging.acctg_cust_id %type;
 v_productType product_type.product_type %type;
 v_clientId tax_era_client.client_id %type;
BEGIN
 D_WORKUNITPRICE := P_TOTAL_AMT / P_UNITCNT;
 IF P_TYPE = 'P' THEN
 INSERT INTO TAX_PAYER
 (payer_id, destination, product_type,
 customer_id, billed_amount, billed_count, billed_rate
 ) <<-- hear i want to insert the values from the cursor g_r_payer_flat(the REF CURSOR)
 VALUES (v_payerid, v_destination, v_producttype,
 v_preacctgcustid, d_totalamt, p_unitcnt, d_workunitprice
 ELSIF P_TYPE = 'C' THEN
 INSERT INTO TAX_ERA_CLIENT
 (client_id, product_type, customer_id,
 billed_amount, billed_count, billed_rate
 VALUES (v_clientid, v_producttype, v_preacctgcustid,
 d_totalamt, p_unitcnt, d_workunitprice
 END IF;
RETURN RET_OK;
EXCEPTION
 WHEN OTHERS THEN
 CBSUTIL.LG.STAT ('when others error with insert into tax on function write_tax_info'|| SQLCODE || ' ' || SQLERRM);
 RETURN RET_ERR;
END WRITE_TAX_INFO; /* End write_tax_info procedure. */thanks in advance

What I mean is
CREATE VIEW vw_payer_flat
AS
SELECT ps.payer_id ,
 ps.destination ,
 NVL (ps.customer_id, '000000000')as customer_id,
 ps.schedule_id ,
 ps.product_type ,
 TO_CHAR (NVL (ps.last_bill_date, TO_DATE (TO_CHAR (ADD_MONTHS (SYSDATE, -1), 'YYYYMM'), 'YYYYMM') ), 'YYYYMM')
 AS last_bill_date,
 NVL (pt.description, ' ') description,
 NVL (pt.acctg_code, 4010) acctg_code,
 pr.price AS price,
 pr.price_period,
 pr.price_period_unit AS price_period_unit,
 pm.subsystem_code,
 NVL (TO_CHAR (ps.grace_period_end_date, 'YYYYMM'), '200808') AS grace_period_end_date
 FROM payer_schedule ps,
 product_type pt,
 price_schedule pr,
 payer_master pm
 WHERE ps.product_type = pt.product_type
 AND ps.schedule_id = pr.schedule_id
 AND ps.payer_id = pm.payer_id
 AND ps.destination = pm.destination
 AND ps.bill_code = 'A' ; And then your insert becomes
INSERT INTO TAX_PAYER
 (payer_id, destination, product_type,
 customer_id, billed_amount, billed_count, billed_rate
SELECT payer_id, destination, product_type, customer_id,
 d_totalamt, p_unitcnt, d_workunitprice
 FROM vw_payer_flatOf course,
- The cursor as declared does not have a DESTINATION column. I suspect that is an oversight.
- d_totamamt is never getting assigned to anything. I suspect you don't need that local variable and want p_total_amt instead
- There seems to be a cardinality issue with the requirements you've posted thus far. Presumably, the view will return multiple rows, but it doesn't seem to make sense to do that given the input parameters.
As a general comment, posting hundreds of lines of code every time you have a question is probably not the most effective way to get help-- none of us are going to notice all the little nuances of the code. At best, we're going to skim the code looking for the most obvious issues. You really need to invest some time in building smaller test cases that illustrate whatever issue you're having.
Justin
Edited by: Justin Cave on Oct 7, 2008 11:43 AM

Incompatible data source error

I have one source table and one target table. In between I have several key lookups. The input into one of the key lookups (let call it K1) is supposed to consist from one source table field and one field that is derived from an other branch of data. This other branch of data stems from a field in the source table. This field is connected together with respective constants into two other key lookups (let call them K2 and K3). Outputs from K2 and K3 and the source field are joined. The output of the joiner is connected into an expression (CASE). The output form the expression is supposed to be the second input field for K1 key lookup. But when I try to connect it I get the following error: "API8003: Connection target attribute group is already connected to an incompatible data source.U se a Joiner or Set operator to join the upstream data first before connecting into this operator." I don't understand this message. The two streams are compatible in my mind since both emanate from the same source and are supposed to yield synchronized rows. I tried to do as advised by the error message, but it doesn't work neither.

Hi Samo,
Indeed, the error you get is a "cardinality issue". On your question on how OWB interprets a join, there is only one stream coming out of a join. So regardless whether this is a carthesion product, it will work and there is a guaranteed equal cardinality. We are not basing this on logical correctness of the join condition! The message implies that you can use a joiner to combine to streams of different cardinality into one single output.
What I meant with both is that you now feed one attribute into the K1 lookup, and transform the other one. Simply transform both through the expression, then feed them into the K1 lookup.
Hope that clarifies a bit,
Jean-Pierre

Query performance issues - Poor cardinality estimate?

Hi,
I have a query which is taking far longer than estimated by the explain plan (estimate 1min, query still running after several hours).
Plan hash value: 3287246760
| Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time |
| 0 | SELECT STATEMENT | | 1 | 195 | 3795 (1)| 00:00:46 |
| 1 | VIEW | | 1 | 195 | 3795 (1)| 00:00:46 |
| 2 | WINDOW SORT | | 1 | 151 | 3795 (1)| 00:00:46 |
| 3 | VIEW | | 1 | 151 | 3794 (1)| 00:00:46 |
| 4 | SORT UNIQUE | | 1 | 147 | 3794 (1)| 00:00:46 |
| 5 | WINDOW BUFFER | | 1 | 147 | 3794 (1)| 00:00:46 |
| 6 | SORT GROUP BY PIVOT | | 1 | 147 | 3794 (1)| 00:00:46 |
| 7 | NESTED LOOPS | | | | | |
| 8 | NESTED LOOPS | | 1 | 147 | 3793 (1)| 00:00:46 |
| 9 | NESTED LOOPS | | 3 | 297 | 1503 (1)| 00:00:19 |
|* 10 | HASH JOIN | | 238 | 15470 | 75 (7)| 00:00:01 |
| 11 | MAT_VIEW ACCESS FULL | VENTILATION | 17994 | 404K| 35 (0)| 00:00:01 |
| 12 | VIEW | | 17994 | 738K| 39 (11)| 00:00:01 |
| 13 | SORT UNIQUE | | 17994 | 702K| 39 (11)| 00:00:01 |
| 14 | WINDOW SORT | | 17994 | 702K| 39 (11)| 00:00:01 |
|* 15 | VIEW | | 17994 | 702K| 37 (6)| 00:00:01 |
| 16 | WINDOW SORT | | 17994 | 632K| 37 (6)| 00:00:01 |
| 17 | MAT_VIEW ACCESS FULL | VENTILATION | 17994 | 632K| 35 (0)| 00:00:01 |
| 18 | INLIST ITERATOR | | | | | |
|* 19 | TABLE ACCESS BY INDEX ROWID| LABEVENTS | 1 | 34 | 6 (0)| 00:00:01 |
|* 20 | INDEX RANGE SCAN | LABEVENTS_O5 | 5 | | 3 (0)| 00:00:01 |
|* 21 | INDEX RANGE SCAN | CHARTEVENTS_O5 | 4937 | | 12 (0)| 00:00:01 |
|* 22 | TABLE ACCESS BY INDEX ROWID | CHARTEVENTS | 1 | 48 | 763 (0)| 00:00:10 |
Predicate Information (identified by operation id):
10 - access("ICUS"."SUBJECT_ID"="FVGT48H"."SUBJECT_ID" AND
 SYS_EXTRACT_UTC("FVGT48H"."BEGIN_TIME")=SYS_EXTRACT_UTC("ICUS"."BEGIN_TIME"))
15 - filter((INTERNAL_FUNCTION("END_TIME")-INTERNAL_FUNCTION("BEGIN_TIME"))DAY(9) TO
 SECOND(9)>INTERVAL'+02 00:00:00' DAY(2) TO SECOND(0))
19 - filter(SYS_EXTRACT_UTC("LE"."CHARTTIME")>=SYS_EXTRACT_UTC("FVGT48H"."BEGIN_TIME") AND
 SYS_EXTRACT_UTC("LE"."CHARTTIME")<=SYS_EXTRACT_UTC("FVGT48H"."END_TIME"))
20 - access("ICUS"."ICUSTAY_ID"="LE"."ICUSTAY_ID" AND ("LE"."ITEMID"=50013 OR
 "LE"."ITEMID"=50019))
 filter("LE"."ICUSTAY_ID" IS NOT NULL)
21 - access("LE"."ICUSTAY_ID"="CE"."ICUSTAY_ID")I tried removing the nested loops using the NO_USE_NL hints, which give the following plan:
| Id | Operation | Name | Rows | Bytes |TempSpc| Cost (%CPU)| Time |
| 0 | SELECT STATEMENT | | 1 | 195 | | 22789 (1)| 00:04:34 |
| 1 | VIEW | | 1 | 195 | | 22789 (1)| 00:04:34 |
| 2 | WINDOW SORT | | 1 | 151 | | 22789 (1)| 00:04:34 |
| 3 | VIEW | | 1 | 151 | | 22788 (1)| 00:04:34 |
| 4 | SORT UNIQUE | | 1 | 147 | | 22788 (1)| 00:04:34 |
| 5 | WINDOW BUFFER | | 1 | 147 | | 22788 (1)| 00:04:34 |
| 6 | SORT GROUP BY PIVOT | | 1 | 147 | | 22788 (1)| 00:04:34 |
|* 7 | HASH JOIN | | 1 | 147 | | 22787 (1)| 00:04:34 |
| 8 | VIEW | | 17994 | 738K| | 39 (11)| 00:00:01 |
| 9 | SORT UNIQUE | | 17994 | 702K| | 39 (11)| 00:00:01 |
| 10 | WINDOW SORT | | 17994 | 702K| | 39 (11)| 00:00:01 |
|* 11 | VIEW | | 17994 | 702K| | 37 (6)| 00:00:01 |
| 12 | WINDOW SORT | | 17994 | 632K| | 37 (6)| 00:00:01 |
| 13 | MAT_VIEW ACCESS FULL | VENTILATION | 17994 | 632K| | 35 (0)| 00:00:01 |
|* 14 | HASH JOIN | | 11873 | 1217K| 5800K| 22747 (1)| 00:04:33 |
|* 15 | HASH JOIN | | 86060 | 4790K| | 16141 (2)| 00:03:14 |
| 16 | MAT_VIEW ACCESS FULL | VENTILATION | 17994 | 404K| | 35 (0)| 00:00:01 |
|* 17 | TABLE ACCESS FULL | LABEVENTS | 176K| 5869K| | 16105 (2)| 00:03:14 |
| 18 | INLIST ITERATOR | | | | | | |
| 19 | TABLE ACCESS BY INDEX ROWID| CHARTEVENTS | 104K| 4911K| | 6024 (1)| 00:01:13 |
|* 20 | INDEX RANGE SCAN | CHARTEVENTS_O4 | 104K| | | 220 (1)| 00:00:03 |
Predicate Information (identified by operation id):
 7 - access("ICUS"."SUBJECT_ID"="FVGT48H"."SUBJECT_ID" AND
 SYS_EXTRACT_UTC("FVGT48H"."BEGIN_TIME")=SYS_EXTRACT_UTC("ICUS"."BEGIN_TIME"))
 filter(SYS_EXTRACT_UTC("LE"."CHARTTIME")>=SYS_EXTRACT_UTC("FVGT48H"."BEGIN_TIME") AND
 SYS_EXTRACT_UTC("LE"."CHARTTIME")<=SYS_EXTRACT_UTC("FVGT48H"."END_TIME"))
11 - filter((INTERNAL_FUNCTION("END_TIME")-INTERNAL_FUNCTION("BEGIN_TIME"))DAY(9) TO
 SECOND(9)>INTERVAL'+02 00:00:00' DAY(2) TO SECOND(0))
14 - access("LE"."ICUSTAY_ID"="CE"."ICUSTAY_ID")
 filter(SYS_EXTRACT_UTC("CHARTTIME")<SYS_EXTRACT_UTC("LE"."CHARTTIME"))
15 - access("ICUS"."ICUSTAY_ID"="LE"."ICUSTAY_ID")
17 - filter("LE"."ICUSTAY_ID" IS NOT NULL AND ("LE"."ITEMID"=50013 OR "LE"."ITEMID"=50019))
20 - access("CE"."ITEMID"=185 OR "CE"."ITEMID"=186 OR "CE"."ITEMID"=190 OR "CE"."ITEMID"=3420)The cardinality estimate looks way off to me - I'm expecting several thousand rows. I have up-to-date statistics.
Can anyone help?
Thanks,
Dan

WITH chf_patients AS (
-- Exclude patients with CHF by ICD9 code
select subject_id,
 hadm_id
from mimic2v26.icd9
where code in ('398.91','402.01','402.91','428.0','428.0', '428.1', '404.13', '404.93', '428.9', '404.91')
, icustays AS (
 /* Our ICU Stay population */
SELECT *
FROM MIMIC2V26.ICUSTAY_DETAIL
WHERE ICUSTAY_AGE_GROUP = 'adult'
 AND SUBJECT_ID NOT IN (select subject_id from chf_patients)
-- AND SUBJECT_ID < 50
--select * from icustays;
-- Combine ventilation periods separated by < 48 hours.
, combine_ventilation as (
select subject_id,
 icustay_id,
 begin_time,
-- end_time as end_first_vent,
-- lead(begin_time,1) over (partition by icustay_id order by begin_time) as next_begin_time,
-- lead(begin_time,1) over (partition by icustay_id order by begin_time) - begin_time as time_to_next,
 case when (lead(begin_time,1) over (partition by icustay_id order by begin_time) - begin_time) < interval '2' day
 then lead(end_time,1) over (partition by icustay_id order by begin_time)
 else end_time end as end_time
from mimic2devel.ventilation
--select * from combine_ventilation;
--select * from combine_ventilation where end_of_ventilation != end_time;
-- Get the first ventilation period which is > 48 hours.
, first_vent_gt_48hrs as (
select distinct subject_id,
 first_value(begin_time) over (partition by subject_id order by begin_time) as begin_time,
 first_value(end_time) over (partition by subject_id order by begin_time) as end_time
from combine_ventilation where end_time - begin_time > interval '48' hour
--select * from first_vent_gt_48hrs;
-- Find the ICU stay when it occurred
, icustay_first_vent_gt_48hrs as (
select fvgt48h.subject_id,
 icus.icustay_id,
 fvgt48h.begin_time,
 fvgt48h.end_time
from first_vent_gt_48hrs fvgt48h
join mimic2devel.ventilation icus on icus.subject_id = fvgt48h.subject_id and fvgt48h.begin_time = icus.begin_time
--select /*+gather_plan_statistics*/ * from icustay_first_vent_gt_48hrs;
, pao2_fio2_during_ventilation as (
select /*+ NO_USE_NL(le ifvgt48h) */
 le.subject_id,
 le.hadm_id,
 le.icustay_id,
 charttime,
 case when itemid = 50019 then 'PAO2'
 when itemid = 50013 then 'FIO2'
 end as item_type,
 -- Some FIO2s are fractional instead of percentage
 case when itemid = 50013 and valuenum > 1 then round(valuenum / 100,2)
 else round(valuenum,2)
 end as valuenum
from mimic2v26.labevents le
join icustay_first_vent_gt_48hrs ifvgt48h on ifvgt48h.icustay_id = le.icustay_id and le.charttime between ifvgt48h.begin_time and ifvgt48h.end_time
where le.itemid = 50019 or le.itemid = 50013
--select * from pao2_fio2_during_ventilation;
-- Check that FIO2s have valid range
, vent_data_pivot as (
select * from (
 select subject_id, hadm_id, icustay_id, charttime, item_type, valuenum from pao2_fio2_during_ventilation)
 pivot ( max(valuenum) as valuenum for item_type in ('FIO2' as fio2, 'PAO2' as pao2) )
--select * from vent_data_pivot;
-- Fill in prior FIO2 from chartevents
, get_prior_fio2s as (
select /*+ NO_USE_NL(vdp ce) */
 distinct
 vdp.subject_id,
 vdp.hadm_id,
 vdp.icustay_id,
 vdp.charttime as pao2_charttime,
 vdp.fio2_valuenum,
 vdp.pao2_valuenum,
-- ce.itemid,
-- ce.charttime as chart_charttime,
-- ce.value1num,
 first_value(ce.value1num) over (partition by ce.icustay_id, vdp.charttime order by ce.charttime desc) as most_recent_fio2_raw,
 case when first_value(ce.value1num) over (partition by ce.icustay_id, vdp.charttime order by ce.charttime desc) > 1
 then round(first_value(ce.value1num) over (partition by ce.icustay_id, vdp.charttime order by ce.charttime desc) / 100,2)
 else round(first_value(ce.value1num) over (partition by ce.icustay_id, vdp.charttime order by ce.charttime desc),2)
 end as most_recent_fio2,
 first_value(ce.charttime) over (partition by ce.icustay_id, vdp.charttime order by ce.charttime desc) as most_recent_fio2_charttime,
 vdp.charttime - first_value(ce.charttime) over (partition by ce.icustay_id, vdp.charttime order by ce.charttime desc) as time_since_fio2,
-- first_value(ce.charttime) over (partition by ce.icustay_id, vdp.charttime order by ce.charttime desc) as most_recent_charttime
 case when first_value(ce.value1num) over (partition by ce.icustay_id, vdp.charttime order by ce.charttime desc) > 1
 then round(vdp.pao2_valuenum/(first_value(ce.value1num) over (partition by ce.icustay_id, vdp.charttime order by ce.charttime desc) / 100),2)
 else round(vdp.pao2_valuenum/(first_value(ce.value1num) over (partition by ce.icustay_id, vdp.charttime order by ce.charttime desc)),2)
 end as pf_ratio,
 case when first_value(ce.value1num) over (partition by ce.icustay_id, vdp.charttime order by ce.charttime desc) > 1
 then
 case when vdp.pao2_valuenum/(first_value(ce.value1num) over (partition by ce.icustay_id, vdp.charttime order by ce.charttime desc) / 100) < 200 then 1 else 0 end
 else
 case when vdp.pao2_valuenum/(first_value(ce.value1num) over (partition by ce.icustay_id, vdp.charttime order by ce.charttime desc)) < 200 then 1 else 0 end
 end as pf_ratio_below_thresh
from vent_data_pivot vdp
join mimic2v26.chartevents ce on vdp.icustay_id = ce.icustay_id and ce.charttime < vdp.charttime
where itemid in (190,3420,186,185)
--select * from get_prior_fio2s order by icustay_id, charttime;
, pf_data as (
select subject_id,
 hadm_id,
 icustay_id,
 pao2_charttime,
 lead(pao2_charttime) over (partition by icustay_id order by pao2_charttime) as next_pao2_charttime,
 fio2_valuenum,
 pao2_valuenum,
 lead(pao2_valuenum) over (partition by icustay_id order by pao2_charttime) as next_pao2_valuenum,
 most_recent_fio2_raw,
 most_recent_fio2,
 most_recent_fio2_charttime,
 time_since_fio2,
 pf_ratio,
 lead(pf_ratio) over (partition by icustay_id order by pao2_charttime) as next_pf_ratio,
 pf_ratio_below_thresh,
 lead(pf_ratio_below_thresh) over (partition by icustay_id order by pao2_charttime) as next_pf_ratio_below_thresh
from get_prior_fio2s
select * from pf_data;Table structure is available here:
http://mimic.physionet.org/schema/latest/
Can I still get a TKPROF if the query doesn't complete? I'll have a go and post the results shortly.
Thanks,
Dan

Issue: SOAMANGER enpoint invalid cardinality "AuthenticationMethod"

Hi:
I can't publishing a web service because have this error in SOAMANAGER:
" Error when building binding view: Configuration is invalid: Invalid cardinality "AuthenticationMethod" "
The endpoint configuration was the first problem, and now this... more endpoint ...
for testing WS, I need in WSDL the SOAP URI, and this it is not...
can you help me?
tks

The answer was FQDN activation.

Cardinality issue

Similar Messages

Maybe you are looking for