Regading WHEN usage in CASE statement

Hi All,
I have a issue with WHEN in CASE statement.
The actual issue is i have one statement is program[REP1] as below:
DELETE S012.
Now i am using the REP1 in my new program by copying all the commands in REP1 into one Internaltable I_TAB.
In this I_TAB internal table i have a field COMMANDS which is filled as below for above code:
DELETE
S012
.
Now When i am using following code in REP2.
CASE I_TAB-COMMANDS.
WHEN 'DELETE'.
Some Updation Code
WHEN 'INSERT'.
Some Updation Code
WHEN 'UPDATE'.
Some Updation Code
WHEN 'X'.
Some Updation Code
WHEN OTHERS.
Some Updation Code
ENDCASE.
It is not going inside DELETE though it is there in I_TAB Internal table.
Same is the case with INSERT&UPDATE.
Can anybody tell me why it is not going inside of WHEN 'DELETE'
Can anybody solve this issue!
Thanks in advance.
Thanks,
Dep.

Put the Itab in a loop. so that every time loop passes the ITAB-COMMAND will have the value for that field related to that loop pass.
Inside loop , if you put your case stmt , it will execute the case for all the ITAB-COMMANDS.
like....
loop at itab.
CASE I_TAB-COMMANDS.
WHEN 'DELETE'.
Some Updation Code
WHEN 'INSERT'.
Some Updation Code
WHEN 'UPDATE'.
Some Updation Code
WHEN 'X'.
Some Updation Code
WHEN OTHERS.
Some Updation Code
ENDCASE.
endloop.

Similar Messages

DoGet method is called 2 times when a switch-case statement is used

Hello all,
I have a servlet that, when run from browser, runs the doGet method 2 times.
I have a switch case statement within the servlet and when I comment out this servlet, it runs 1 time as expected.
Here is the code:
public class RSSServlet extends HttpServlet {
 /** Processes requests for both HTTP <code>GET</code> and <code>POST</code> methods.
 * @param request servlet request
 * @param response servlet response
 protected void processRequest(HttpServletRequest request, HttpServletResponse response)
 throws ServletException, IOException {
 System.out.println("CALLED SERVLET");
 response.setContentType("text/xml;charset=UTF-8");
 PrintWriter out = response.getWriter();
 DBQueriesRSS queries = new DBQueriesRSS();
 String queryType = request.getParameter("queryType");
 String strCount = request.getParameter("count");
 int count = (strCount != null && !strCount.equalsIgnoreCase("null") && strCount.length() > 0) ?
 Integer.parseInt(strCount) : 25;
 if(queryType != null && !queryType.equalsIgnoreCase("null") && queryType.length() > 0) {
 System.out.println("IN IF STATEMENT");
 switch(Integer.parseInt(queryType)) {
 case 1 : out.println(queries.getDefault(count));System.out.println("1"); break;
 case 11: out.println(queries.getDefault(count));System.out.println("11"); break;
 case 21: out.println(queries.getTopDaily(count));System.out.println("21"); break;
 case 22: out.println(queries.getTopWeekly(count));System.out.println("22"); break;
 case 23: out.println(queries.getTopMonthly(count));System.out.println("23"); break;
 case 24: out.println(queries.getTopYearly(count));System.out.println("24"); break;
 case 31: out.println(queries.getTopNDailyBW(count));System.out.println("31"); break;
 case 32: out.println(queries.getTopNWeeklyBW(count));System.out.println("32"); break;
 case 33: out.println(queries.getTopNMonthlyBW(count));System.out.println("33"); break;
 case 34: out.println(queries.getTopNYearlyBW(count));System.out.println("34"); break;
 default: out.println(queries.getTopWeekly(25));System.out.println("default"); break;
 System.out.println("OUT OF SWITCH");
 System.out.println("OUT OF IF");
 out.close();
 // <editor-fold defaultstate="collapsed" desc="HttpServlet methods. Click on the + sign on the left to edit the code.">
 /** Handles the HTTP <code>GET</code> method.
 * @param request servlet request
 * @param response servlet response
 protected void doGet(HttpServletRequest request, HttpServletResponse response)
 throws ServletException, IOException {
 processRequest(request, response);
 /** Handles the HTTP <code>POST</code> method.
 * @param request servlet request
 * @param response servlet response
 protected void doPost(HttpServletRequest request, HttpServletResponse response)
 throws ServletException, IOException {
 processRequest(request, response);
 /** Returns a short description of the servlet.
 public String getServletInfo() {
 return "Short description";
 // </editor-fold>
} The results from running this servlet are:
http://localhost/proxy/RSSServlet??queryType=34&count=66
CALLED SERVLET
IN IF STATEMENT
34
OUT OF SWITCH
OUT OF IF
CALLED SERVLET
IN IF STATEMENT
34
OUT OF SWITCH
OUT OF IFAnyone see anything obvious?
TIA!

in your case you want 'count' to be a class attribute rather than a local variable. But yes, incrementing it each time that the method is called will serve your purpose.

How to use CASE statement in WDA

Hi All,
Can any one Please expain me ' How to use CASE statement in Web dynpro ABAP? '
Please give me an example also.
Thanks in Advance !

Hi,
The usage of case statement in webdynpro is same as used in general ABAP.
Data: l_id type string.
l_id = wdevent->get_string( 'ID' ).
case l_id.
when 'BTN1'.
when 'BTN2'.
when 'OTHERS'.
endcase.
Regards,
Radhika.

Sql query slow due to case statement on Joins

Hi
The sql query runs very slow for 30 min when the below case statement is added on the joins. Could you please let me know how to tune it. if the case statement is not there then it runs only for 1 min.
*( CASE*
WHEN PO_DIST_GL_CODE_COMB.SEGMENT2 <> '1000'
THEN PO_DIST_GL_CODE_COMB.SEGMENT1 || PO_DIST_GL_CODE_COMB.SEGMENT2 || '_' || NVL(PO_DIST_GL_CODE_COMB.SEGMENT6,'000')
WHEN DT_REQ_ALL.EMPMGMTCD IS NOT NULL AND
PO_DIST_GL_CODE_COMB.SEGMENT2 = '1000'
THEN DT_REQ_ALL.EMPMGMTCD
END =DB2.DB2_FDW_MGMT_V.MH_CHILD )
SELECT DISTINCT
D.DB2_FDW_MGMT_V.RC_PARENT,
DT_REQ_ALL.FULL_NAME,
DT_REQ_ALL.EMP_COMPANY_CODE,
DT_REQ_ALL.EMP_COST_CENTER,
PO.PO_VENDORS.VENDOR_NAME,
PO_PO_HEADERS_ALL2.SEGMENT1,
PO_PO_HEADERS_ALL2.CREATION_DATE,
PO_DIST_GL_CODE_COMB.SEGMENT1,
PO_DIST_GL_CODE_COMB.SEGMENT2,
PO_PO_HEADERS_ALL2.CURRENCY_CODE,
PO_INV_DIST_ALL.INVOICE_NUM,
PO_INV_DIST_ALL.INVOICE_DATE,
(PO_INV_DIST_ALL.INVOICE_AMOUNT* PO_Rates_GL_DR.CONVERSION_RATE),
(NVL(to_number(PO_DIST_ALL.AMOUNT_BILLED),0) * PO_Rates_GL_DR.CONVERSION_RATE),
PO_LINES_LOC.LINE_NUM,
GL.GL_SETS_OF_BOOKS.NAME,
CASE
 WHEN TRUNC(PO_PO_HEADERS_ALL2.CREATION_DATE) > PO_INV_DIST_ALL.INVOICE_DATE
 THEN 1
 ELSE 0
 END ,
PO.PO_REQUISITION_LINES_ALL.LINE_LOCATION_ID,
TRUNC(PO_PO_HEADERS_ALL2.CREATION_DATE,'WW') + 8 WEEK_Ending
FROM
DB2.DB2_FDW_MGMT_V,
 PO.PO_VENDORS,
PO.PO_HEADERS_ALL PO_PO_HEADERS_ALL2,
GL.GL_CODE_COMBINATIONS PO_DIST_GL_CODE_COMB,
AP.AP_INVOICES_ALL PO_INV_DIST_ALL,
 PO.PO_DISTRIBUTIONS_ALL PO_DIST_ALL,
PO.PO_LINES_ALL PO_LINES_LOC,
GL.GL_SETS_OF_BOOKS,
PO.PO_REQUISITION_LINES_ALL,
PO.PO_LINE_LOCATIONS_ALL,
AP.AP_INVOICE_DISTRIBUTIONS_ALL PO_DIST_INV_DIST_ALL,
APPS.HR_OPERATING_UNITS,
PO.PO_REQ_DISTRIBUTIONS_ALL,
 SELECT DISTINCT
 PO_RDA.DISTRIBUTION_ID,
 PO_RLA.requisition_line_id,
 PO_RHA.DESCRIPTION PO_Descr,
 PO_RHA.NOTE_TO_AUTHORIZER PO_Justification,
 Req_Emp.FULL_NAME,
 GL_CC.SEGMENT1 Req_Company_Code,
 GL_CC.SEGMENT2 Req_Cost_Center,
 Req_Emp_CC.SEGMENT1 Emp_Company_Code,
 Req_Emp_CC.SEGMENT2 Emp_Cost_Center,
 (Case
 When GL_CC.SEGMENT2 <> 8000
 Then TRUNC(GL_CC.SEGMENT1) || TRUNC(GL_CC.SEGMENT2) || '_' || NVL(GL_CC.SEGMENT6,'000')
 Else TRUNC(Req_Emp_CC.SEGMENT1) || TRUNC(Req_Emp_CC.SEGMENT2) || '_' || NVL(Req_Emp_CC.SEGMENT6,'000')
 End) EmpMgmtCD
 FROM
 PO.po_requisition_lines_all PO_rla,
 PO.po_requisition_headers_all PO_rha,
 PO.PO_REQ_DISTRIBUTIONS_ALL po_RDA,
 GL.GL_CODE_COMBINATIONS gl_cc,
 HR.PER_ALL_PEOPLE_F Req_Emp,
 HR.PER_ALL_ASSIGNMENTS_F Req_Emp_Assign,
 HR.hr_all_organization_units Req_Emp_Org,
 HR.pay_cost_allocation_keyflex Req_Emp_CC
 WHERE
 PO_RDA.CODE_COMBINATION_ID = GL_CC.CODE_COMBINATION_ID and
 PO_RLA.REQUISITION_LINE_ID = PO_RDA.REQUISITION_LINE_ID AND
 PO_RLA.to_person_id = Req_Emp.PERSON_ID AND
 PO_RLA.REQUISITION_HEADER_ID = PO_RHA.REQUISITION_HEADER_ID AND
 (trunc(PO_rla.CREATION_DATE) between Req_Emp.effective_start_date and Req_Emp.effective_end_date OR
 Req_Emp.effective_start_date IS NULL) AND
 Req_Emp.PERSON_ID = Req_Emp_Assign.PERSON_ID AND
 Req_Emp_Assign.organization_id = Req_Emp_Org.organization_id AND
 (trunc(PO_rla.CREATION_DATE) between Req_Emp_Assign.effective_start_date and Req_Emp_Assign.effective_end_date OR
 Req_Emp_Assign.effective_start_date IS NULL) AND
 Req_Emp_Assign.primary_flag = 'Y' AND
 Req_Emp_Assign.assignment_type = 'E' AND
 Req_Emp_Org.cost_allocation_keyflex_id = Req_Emp_CC.cost_allocation_keyflex_id
) DT_REQ_ALL,
SELECT
 FROM_CURRENCY,
 TO_CURRENCY,
 CONVERSION_DATE,
 CONVERSION_RATE
 FROM GL.GL_DAILY_RATES
 UNION
 SELECT Distinct
 'USD',
 'USD',
 CONVERSION_DATE,
 1
 FROM GL.GL_DAILY_RATES
) PO_Rates_GL_DR
WHERE
( PO_DIST_GL_CODE_COMB.CODE_COMBINATION_ID=PO_DIST_ALL.CODE_COMBINATION_ID )
AND ( PO_DIST_ALL.LINE_LOCATION_ID=PO.PO_LINE_LOCATIONS_ALL.LINE_LOCATION_ID )
AND ( PO_PO_HEADERS_ALL2.VENDOR_ID=PO.PO_VENDORS.VENDOR_ID )
AND ( PO_PO_HEADERS_ALL2.ORG_ID=APPS.HR_OPERATING_UNITS.ORGANIZATION_ID )
AND ( GL.GL_SETS_OF_BOOKS.SET_OF_BOOKS_ID=APPS.HR_OPERATING_UNITS.SET_OF_BOOKS_ID )
AND ( PO_PO_HEADERS_ALL2.CURRENCY_CODE=PO_Rates_GL_DR.FROM_CURRENCY )
AND ( trunc(PO_PO_HEADERS_ALL2.CREATION_DATE)=PO_Rates_GL_DR.CONVERSION_DATE )
AND ( PO_DIST_ALL.REQ_DISTRIBUTION_ID=PO.PO_REQ_DISTRIBUTIONS_ALL.DISTRIBUTION_ID(+) )
AND ( PO.PO_REQ_DISTRIBUTIONS_ALL.REQUISITION_LINE_ID=PO.PO_REQUISITION_LINES_ALL.REQUISITION_LINE_ID(+) )
AND ( PO_LINES_LOC.PO_HEADER_ID=PO_PO_HEADERS_ALL2.PO_HEADER_ID )
AND ( PO.PO_LINE_LOCATIONS_ALL.PO_LINE_ID=PO_LINES_LOC.PO_LINE_ID )
AND ( PO_DIST_ALL.REQ_DISTRIBUTION_ID=DT_REQ_ALL.DISTRIBUTION_ID(+) )
AND ( PO_DIST_ALL.PO_DISTRIBUTION_ID=PO_DIST_INV_DIST_ALL.PO_DISTRIBUTION_ID(+) )
AND ( PO_INV_DIST_ALL.INVOICE_ID(+)=PO_DIST_INV_DIST_ALL.INVOICE_ID )
AND ( PO_INV_DIST_ALL.SOURCE(+) <> 'XML GATEWAY' )
AND
 ( NVL(PO_PO_HEADERS_ALL2.CANCEL_FLAG,'N') <> 'Y' )
 AND
 ( NVL(PO_PO_HEADERS_ALL2.CLOSED_CODE, 'OPEN') <> 'FINALLY CLOSED' )
 AND
 ( NVL(PO_PO_HEADERS_ALL2.AUTHORIZATION_STATUS,'IN PROCESS') <> 'REJECTED' )
 AND
 ( TRUNC(PO_PO_HEADERS_ALL2.CREATION_DATE) BETWEEN TO_DATE('01-jan-2011') AND TO_DATE('04-jan-2011') )
 AND
 PO_Rates_GL_DR.TO_CURRENCY = 'USD'
 AND
 DB2.DB2_FDW_MGMT_V.RC_PARENT In ( 'Unavailable','Corp','Commercial' )
 AND
( CASE
 WHEN PO_DIST_GL_CODE_COMB.SEGMENT2 <> '1000'
 THEN PO_DIST_GL_CODE_COMB.SEGMENT1 || PO_DIST_GL_CODE_COMB.SEGMENT2 || '_' || NVL(PO_DIST_GL_CODE_COMB.SEGMENT6,'000')
 WHEN DT_REQ_ALL.EMPMGMTCD IS NOT NULL AND
 PO_DIST_GL_CODE_COMB.SEGMENT2 = '1000'
 THEN DT_REQ_ALL.EMPMGMTCD
 END =DB2.DB2_FDW_MGMT_V.MH_CHILD )Explain plan. sorry can't get the explain plan from sql. this is from toad.
Plan
SELECT STATEMENT ALL_ROWSCost: 53,932 Bytes: 2,607 Cardinality: 1
 79 HASH UNIQUE Cost: 53,932 Bytes: 2,607 Cardinality: 1
 78 NESTED LOOPS OUTER Cost: 53,931 Bytes: 2,607 Cardinality: 1
 75 NESTED LOOPS OUTER Cost: 53,928 Bytes: 2,560 Cardinality: 1
 72 NESTED LOOPS Cost: 53,902 Bytes: 2,552 Cardinality: 1
 69 NESTED LOOPS OUTER Cost: 53,900 Bytes: 2,533 Cardinality: 1
 66 NESTED LOOPS OUTER Cost: 53,898 Bytes: 2,521 Cardinality: 1
 63 HASH JOIN OUTER Cost: 53,896 Bytes: 2,509 Cardinality: 1
 40 TABLE ACCESS BY INDEX ROWID TABLE PO.PO_DISTRIBUTIONS_ALL Cost: 3 Bytes: 26 Cardinality: 1
 39 NESTED LOOPS Cost: 17,076 Bytes: 2,400 Cardinality: 1
 37 NESTED LOOPS Cost: 17,073 Bytes: 2,374 Cardinality: 1
 34 NESTED LOOPS Cost: 17,070 Bytes: 2,362 Cardinality: 1
 31 NESTED LOOPS Cost: 17,066 Bytes: 2,347 Cardinality: 1
 29 NESTED LOOPS Cost: 17,066 Bytes: 2,339 Cardinality: 1
 26 NESTED LOOPS Cost: 17,065 Bytes: 2,312 Cardinality: 1
 23 NESTED LOOPS Cost: 17,064 Bytes: 2,287 Cardinality: 1
 20 NESTED LOOPS Cost: 17,062 Bytes: 2,261 Cardinality: 1
 17 NESTED LOOPS Cost: 17,056 Bytes: 6,678 Cardinality: 3
 15 HASH JOIN Cost: 17,056 Bytes: 6,663 Cardinality: 3
 13 MERGE JOIN CARTESIAN Cost: 135 Bytes: 30,352 Cardinality: 14
 5 VIEW VIEW DB2.DB2_FDW_MGMT_V Cost: 4 Bytes: 2,128 Cardinality: 1
 4 SORT UNIQUE Cost: 4 Cardinality: 1
 3 UNION-ALL
 1 REMOTE REMOTE SERIAL_FROM_REMOTE PRDFDW.WORLD
 2 FAST DUAL Cost: 3 Cardinality: 1
 12 BUFFER SORT Cost: 135 Bytes: 560 Cardinality: 14
 11 VIEW DB2. Cost: 131 Bytes: 560 Cardinality: 14
 10 SORT UNIQUE Cost: 131 Bytes: 310 Cardinality: 14
 9 UNION-ALL
 7 TABLE ACCESS BY INDEX ROWID TABLE GL.GL_DAILY_RATES Cost: 65 Bytes: 270 Cardinality: 9
 6 INDEX SKIP SCAN INDEX (UNIQUE) GL.GL_DAILY_RATES_U1 Cost: 64 Cardinality: 1
 8 INDEX SKIP SCAN INDEX (UNIQUE) GL.GL_DAILY_RATES_U1 Cost: 64 Bytes: 4,368 Cardinality: 546
 14 TABLE ACCESS FULL TABLE PO.PO_HEADERS_ALL Cost: 16,920 Bytes: 32,754 Cardinality: 618
 16 INDEX UNIQUE SCAN INDEX (UNIQUE) HR.HR_ORGANIZATION_UNITS_PK Cost: 0 Bytes: 5 Cardinality: 1
 19 TABLE ACCESS BY INDEX ROWID TABLE HR.HR_ORGANIZATION_INFORMATION Cost: 2 Bytes: 35 Cardinality: 1
 18 INDEX RANGE SCAN INDEX HR.HR_ORGANIZATION_INFORMATIO_FK2 Cost: 1 Cardinality: 2
 22 TABLE ACCESS BY INDEX ROWID TABLE HR.HR_ORGANIZATION_INFORMATION Cost: 2 Bytes: 26 Cardinality: 1
 21 INDEX RANGE SCAN INDEX HR.HR_ORGANIZATION_INFORMATIO_FK2 Cost: 1 Cardinality: 1
 25 TABLE ACCESS BY INDEX ROWID TABLE GL.GL_SETS_OF_BOOKS Cost: 1 Bytes: 25 Cardinality: 1
 24 INDEX UNIQUE SCAN INDEX (UNIQUE) GL.GL_SETS_OF_BOOKS_U2 Cost: 0 Cardinality: 1
 28 TABLE ACCESS BY INDEX ROWID TABLE PO.PO_VENDORS Cost: 1 Bytes: 27 Cardinality: 1
 27 INDEX UNIQUE SCAN INDEX (UNIQUE) PO.PO_VENDORS_U1 Cost: 0 Cardinality: 1
 30 INDEX UNIQUE SCAN INDEX (UNIQUE) HR.HR_ALL_ORGANIZATION_UNTS_TL_PK Cost: 0 Bytes: 8 Cardinality: 1
 33 TABLE ACCESS BY INDEX ROWID TABLE PO.PO_LINES_ALL Cost: 4 Bytes: 60 Cardinality: 4
 32 INDEX RANGE SCAN INDEX (UNIQUE) PO.PO_LINES_U2 Cost: 2 Cardinality: 4
 36 TABLE ACCESS BY INDEX ROWID TABLE PO.PO_LINE_LOCATIONS_ALL Cost: 3 Bytes: 12 Cardinality: 1
 35 INDEX RANGE SCAN INDEX PO.PO_LINE_LOCATIONS_N1 Cost: 2 Cardinality: 1
 38 INDEX RANGE SCAN INDEX PO.PO_DISTRIBUTIONS_N1 Cost: 2 Cardinality: 1
 62 VIEW DB2. Cost: 36,819 Bytes: 1,090 Cardinality: 10
 61 HASH UNIQUE Cost: 36,819 Bytes: 2,580 Cardinality: 10
 60 NESTED LOOPS Cost: 36,818 Bytes: 2,580 Cardinality: 10
 57 NESTED LOOPS Cost: 36,798 Bytes: 2,390 Cardinality: 10
 54 NESTED LOOPS Cost: 36,768 Bytes: 2,220 Cardinality: 10
 51 NESTED LOOPS Cost: 36,758 Bytes: 1,510 Cardinality: 10
 48 NESTED LOOPS Cost: 36,747 Bytes: 1,050 Cardinality: 10
 45 HASH JOIN Cost: 36,737 Bytes: 960 Cardinality: 10
 43 HASH JOIN Cost: 34,602 Bytes: 230,340 Cardinality: 3,490
 41 TABLE ACCESS FULL TABLE HR.PER_ALL_PEOPLE_F Cost: 1,284 Bytes: 1,848,420 Cardinality: 44,010
 42 TABLE ACCESS FULL TABLE PO.PO_REQUISITION_LINES_ALL Cost: 31,802 Bytes: 18,340,080 Cardinality: 764,170
 44 TABLE ACCESS FULL TABLE HR.PER_ALL_ASSIGNMENTS_F Cost: 2,134 Bytes: 822,540 Cardinality: 27,418
 47 TABLE ACCESS BY INDEX ROWID TABLE HR.HR_ALL_ORGANIZATION_UNITS Cost: 1 Bytes: 9 Cardinality: 1
 46 INDEX UNIQUE SCAN INDEX (UNIQUE) HR.HR_ORGANIZATION_UNITS_PK Cost: 0 Cardinality: 1
 50 TABLE ACCESS BY INDEX ROWID TABLE HR.PAY_COST_ALLOCATION_KEYFLEX Cost: 1 Bytes: 46 Cardinality: 1
 49 INDEX UNIQUE SCAN INDEX (UNIQUE) HR.PAY_COST_ALLOCATION_KEYFLE_PK Cost: 0 Cardinality: 1
 53 TABLE ACCESS BY INDEX ROWID TABLE PO.PO_REQUISITION_HEADERS_ALL Cost: 1 Bytes: 71 Cardinality: 1
 52 INDEX UNIQUE SCAN INDEX (UNIQUE) PO.PO_REQUISITION_HEADERS_U1 Cost: 0 Cardinality: 1
 56 TABLE ACCESS BY INDEX ROWID TABLE PO.PO_REQ_DISTRIBUTIONS_ALL Cost: 3 Bytes: 17 Cardinality: 1
 55 INDEX RANGE SCAN INDEX PO.PO_REQ_DISTRIBUTIONS_N1 Cost: 2 Cardinality: 1
 59 TABLE ACCESS BY INDEX ROWID TABLE GL.GL_CODE_COMBINATIONS Cost: 2 Bytes: 19 Cardinality: 1
 58 INDEX UNIQUE SCAN INDEX (UNIQUE) GL.GL_CODE_COMBINATIONS_U1 Cost: 1 Cardinality: 1
 65 TABLE ACCESS BY INDEX ROWID TABLE PO.PO_REQ_DISTRIBUTIONS_ALL Cost: 2 Bytes: 12 Cardinality: 1
 64 INDEX UNIQUE SCAN INDEX (UNIQUE) PO.PO_REQ_DISTRIBUTIONS_U1 Cost: 1 Cardinality: 1
 68 TABLE ACCESS BY INDEX ROWID TABLE PO.PO_REQUISITION_LINES_ALL Cost: 2 Bytes: 12 Cardinality: 1
 67 INDEX UNIQUE SCAN INDEX (UNIQUE) PO.PO_REQUISITION_LINES_U1 Cost: 1 Cardinality: 1
 71 TABLE ACCESS BY INDEX ROWID TABLE GL.GL_CODE_COMBINATIONS Cost: 2 Bytes: 19 Cardinality: 1
 70 INDEX UNIQUE SCAN INDEX (UNIQUE) GL.GL_CODE_COMBINATIONS_U1 Cost: 1 Cardinality: 1
 74 TABLE ACCESS BY INDEX ROWID TABLE AP.AP_INVOICE_DISTRIBUTIONS_ALL Cost: 26 Bytes: 16 Cardinality: 2
 73 INDEX RANGE SCAN INDEX AP.AP_INVOICE_DISTRIBUTIONS_N7 Cost: 2 Cardinality: 37
 77 TABLE ACCESS BY INDEX ROWID TABLE AP.AP_INVOICES_ALL Cost: 3 Bytes: 47 Cardinality: 1
 76 INDEX RANGE SCAN INDEX (UNIQUE) AP.AP_INVOICES_U1 Cost: 2 Cardinality: 1 Thanks

Forming a new table "new_table" with 3 tables which particiapate in CASE statement logic.
with DT_REQ_ALL as
 SELECT DISTINCT
 PO_RDA.DISTRIBUTION_ID,
 PO_RLA.requisition_line_id,
 PO_RHA.DESCRIPTION PO_Descr,
 PO_RHA.NOTE_TO_AUTHORIZER PO_Justification,
 Req_Emp.FULL_NAME,
 GL_CC.SEGMENT1 Req_Company_Code,
 GL_CC.SEGMENT2 Req_Cost_Center,
 Req_Emp_CC.SEGMENT1 Emp_Company_Code,
 Req_Emp_CC.SEGMENT2 Emp_Cost_Center,
 (Case
 When GL_CC.SEGMENT2 8000
 Then TRUNC(GL_CC.SEGMENT1) || TRUNC(GL_CC.SEGMENT2) || '_' || NVL(GL_CC.SEGMENT6,'000')
 Else TRUNC(Req_Emp_CC.SEGMENT1) || TRUNC(Req_Emp_CC.SEGMENT2) || '_' || NVL(Req_Emp_CC.SEGMENT6,'000')
 End) EmpMgmtCD
 FROM
 PO.po_requisition_lines_all PO_rla,
 PO.po_requisition_headers_all PO_rha,
 PO.PO_REQ_DISTRIBUTIONS_ALL po_RDA,
 GL.GL_CODE_COMBINATIONS gl_cc,
 HR.PER_ALL_PEOPLE_F Req_Emp,
 HR.PER_ALL_ASSIGNMENTS_F Req_Emp_Assign,
 HR.hr_all_organization_units Req_Emp_Org,
 HR.pay_cost_allocation_keyflex Req_Emp_CC
 WHERE
 PO_RDA.CODE_COMBINATION_ID = GL_CC.CODE_COMBINATION_ID and
 PO_RLA.REQUISITION_LINE_ID = PO_RDA.REQUISITION_LINE_ID AND
 PO_RLA.to_person_id = Req_Emp.PERSON_ID AND
 PO_RLA.REQUISITION_HEADER_ID = PO_RHA.REQUISITION_HEADER_ID AND
 (trunc(PO_rla.CREATION_DATE) between Req_Emp.effective_start_date and Req_Emp.effective_end_date OR
 Req_Emp.effective_start_date IS NULL) AND
 Req_Emp.PERSON_ID = Req_Emp_Assign.PERSON_ID AND
 Req_Emp_Assign.organization_id = Req_Emp_Org.organization_id AND
 (trunc(PO_rla.CREATION_DATE) between Req_Emp_Assign.effective_start_date and Req_Emp_Assign.effective_end_date OR
 Req_Emp_Assign.effective_start_date IS NULL) AND
 Req_Emp_Assign.primary_flag = 'Y' AND
 Req_Emp_Assign.assignment_type = 'E' AND
 Req_Emp_Org.cost_allocation_keyflex_id = Req_Emp_CC.cost_allocation_keyflex_id
SELECT DISTINCT
D.DB2_FDW_MGMT_V.RC_PARENT,
DT_REQ_ALL.FULL_NAME,
DT_REQ_ALL.EMP_COMPANY_CODE,
DT_REQ_ALL.EMP_COST_CENTER,
PO.PO_VENDORS.VENDOR_NAME,
PO_PO_HEADERS_ALL2.SEGMENT1,
PO_PO_HEADERS_ALL2.CREATION_DATE,
PO_DIST_GL_CODE_COMB.SEGMENT1,
PO_DIST_GL_CODE_COMB.SEGMENT2,
PO_PO_HEADERS_ALL2.CURRENCY_CODE,
PO_INV_DIST_ALL.INVOICE_NUM,
PO_INV_DIST_ALL.INVOICE_DATE,
(PO_INV_DIST_ALL.INVOICE_AMOUNT* PO_Rates_GL_DR.CONVERSION_RATE),
(NVL(to_number(PO_DIST_ALL.AMOUNT_BILLED),0) * PO_Rates_GL_DR.CONVERSION_RATE),
PO_LINES_LOC.LINE_NUM,
GL.GL_SETS_OF_BOOKS.NAME,
CASE
 WHEN TRUNC(PO_PO_HEADERS_ALL2.CREATION_DATE) > PO_INV_DIST_ALL.INVOICE_DATE
 THEN 1
 ELSE 0
 END ,
PO.PO_REQUISITION_LINES_ALL.LINE_LOCATION_ID,
TRUNC(PO_PO_HEADERS_ALL2.CREATION_DATE,'WW') + 8 WEEK_Ending
FROM
( SELECT * FROM
 DB2.DB2_FDW_MGMT_V,
 GL.GL_CODE_COMBINATIONS PO_DIST_GL_CODE_COMB,
 DT_REQ_ALL
 WHERE
 DB2.DB2_FDW_MGMT_V.RC_PARENT In ( 'Unavailable','Corp','Commercial' )
 AND
 CASE
 WHEN PO_DIST_GL_CODE_COMB.SEGMENT2 <> '1000'
 THEN PO_DIST_GL_CODE_COMB.SEGMENT1 || PO_DIST_GL_CODE_COMB.SEGMENT2 || '_' || NVL(PO_DIST_GL_CODE_COMB.SEGMENT6,'000')
 WHEN DT_REQ_ALL.EMPMGMTCD IS NOT NULL AND
 PO_DIST_GL_CODE_COMB.SEGMENT2 = '1000'
 THEN DT_REQ_ALL.EMPMGMTCD
 END =DB2.DB2_FDW_MGMT_V.MH_CHILD
 ) new_table,
 PO.PO_VENDORS,
PO.PO_HEADERS_ALL PO_PO_HEADERS_ALL2,
AP.AP_INVOICES_ALL PO_INV_DIST_ALL,
 PO.PO_DISTRIBUTIONS_ALL PO_DIST_ALL,
PO.PO_LINES_ALL PO_LINES_LOC,
GL.GL_SETS_OF_BOOKS,
PO.PO_REQUISITION_LINES_ALL,
PO.PO_LINE_LOCATIONS_ALL,
AP.AP_INVOICE_DISTRIBUTIONS_ALL PO_DIST_INV_DIST_ALL,
APPS.HR_OPERATING_UNITS,
PO.PO_REQ_DISTRIBUTIONS_ALL,
SELECT
 FROM_CURRENCY,
 TO_CURRENCY,
 CONVERSION_DATE,
 CONVERSION_RATE
 FROM GL.GL_DAILY_RATES
 UNION
 SELECT Distinct
 'USD',
 'USD',
 CONVERSION_DATE,
 1
 FROM GL.GL_DAILY_RATES
) PO_Rates_GL_DR
WHERE
( PO_DIST_GL_CODE_COMB.CODE_COMBINATION_ID=PO_DIST_ALL.CODE_COMBINATION_ID )
AND ( PO_DIST_ALL.LINE_LOCATION_ID=PO.PO_LINE_LOCATIONS_ALL.LINE_LOCATION_ID )
AND ( PO_PO_HEADERS_ALL2.VENDOR_ID=PO.PO_VENDORS.VENDOR_ID )
AND ( PO_PO_HEADERS_ALL2.ORG_ID=APPS.HR_OPERATING_UNITS.ORGANIZATION_ID )
AND ( GL.GL_SETS_OF_BOOKS.SET_OF_BOOKS_ID=APPS.HR_OPERATING_UNITS.SET_OF_BOOKS_ID )
AND ( PO_PO_HEADERS_ALL2.CURRENCY_CODE=PO_Rates_GL_DR.FROM_CURRENCY )
AND ( trunc(PO_PO_HEADERS_ALL2.CREATION_DATE)=PO_Rates_GL_DR.CONVERSION_DATE )
AND ( PO_DIST_ALL.REQ_DISTRIBUTION_ID=PO.PO_REQ_DISTRIBUTIONS_ALL.DISTRIBUTION_ID(+) )
AND ( PO.PO_REQ_DISTRIBUTIONS_ALL.REQUISITION_LINE_ID=PO.PO_REQUISITION_LINES_ALL.REQUISITION_LINE_ID(+) )
AND ( PO_LINES_LOC.PO_HEADER_ID=PO_PO_HEADERS_ALL2.PO_HEADER_ID )
AND ( PO.PO_LINE_LOCATIONS_ALL.PO_LINE_ID=PO_LINES_LOC.PO_LINE_ID )
AND ( PO_DIST_ALL.REQ_DISTRIBUTION_ID=DT_REQ_ALL.DISTRIBUTION_ID(+) )
AND ( PO_DIST_ALL.PO_DISTRIBUTION_ID=PO_DIST_INV_DIST_ALL.PO_DISTRIBUTION_ID(+) )
AND ( PO_INV_DIST_ALL.INVOICE_ID(+)=PO_DIST_INV_DIST_ALL.INVOICE_ID )
AND ( PO_INV_DIST_ALL.SOURCE(+) 'XML GATEWAY' )
AND
 ( NVL(PO_PO_HEADERS_ALL2.CANCEL_FLAG,'N') 'Y' )
 AND
 ( NVL(PO_PO_HEADERS_ALL2.CLOSED_CODE, 'OPEN') 'FINALLY CLOSED' )
 AND
 ( NVL(PO_PO_HEADERS_ALL2.AUTHORIZATION_STATUS,'IN PROCESS') 'REJECTED' )
 AND
 ( TRUNC(PO_PO_HEADERS_ALL2.CREATION_DATE) BETWEEN TO_DATE('01-jan-2011') AND TO_DATE('04-jan-2011') )
 AND
 PO_Rates_GL_DR.TO_CURRENCY = 'USD'

Creating view containing case statements received error ORA-22992

We have a create view referencing table through dblink. The select statement in the create view has case statements, when running the Select statement alone, results are return. However, when executing the create view, it returns:
SQL Error: ORA-22992: cannot use LOB locators selected from remote tables
22992. 00000 - "cannot use LOB locators selected from remote tables"
*Cause: A remote LOB column cannot be referenced.
*Action: Remove references to LOBs in remote tables.
One of the source table has LOB column but not in the select statement. The strange thing is when removing the case statement from the select, create view works fine. Can anybody tell me what caused the error and how to fix it?
Create View Snippet:
CREATE OR REPLACE VIEW "ABC"."XYZ" (....
AS SELECT
CASE
WHEN A.OUTAGE =1
THEN 'Y'
ELSE 'N'
END AS OUTAGE,
FROM
TABLEA@XXXX A
LEFT JOIN TABLEB@XXXX B
ON
A.LOC =B.LO
AND A.SITE =B.SITE
WHERE
A.CLASS ='CUSTOMER'
AND A.PLUSSISGIS =1;

What is your 4 digit Oracle version?
Try rewriting the query to not use ANSI SQL92 joins. I found a link where this solved a problem similar to yours.
DBLink problem ORA-22992
>
But, look at this curious thing: I re-write the query as follows:
SELECT A.ID, A.ID_REF, A.EVENDATE, B.DESCRIPTION
FROM A@ORCL A, B@ORCL B
WHERE A.ID_REF = B.ID_REF;
and it works fine... It seems like Oracle don't like the ANSI SQL92...
>
Several similar links by googling: 'SQL Error: ORA-22992'
http://www.dbuggr.com/smallwei/solution-error-ora-22992-lob-locators-selected-remote-tabl/
>
Fixing ORA-22992 “cannot use LOB locators selected from remote tables” error
You have migrated your Oracle 9i database to 10g and a distributed statement which worked fine in 9i now is getting error ORA-22992 “cannot use LOB locators selected from remote tables”. Even though the related remote table(s) does not contain any LOB column datatype.
FIX:
There is a bug on 9i,10g, and 11g that is related to this error. It is being fixed in 11.2. It can also be backported for previous 9i, 10g and 11g releases under the latest patchsets.
You may also do a workaround as follow:
Modify the affected SQL by adding the TO_CHAR function. For example:
-- Original SQL:
SELECT NVL2('a', 'b','c' ) FROM dual@remote_db;
-- Modified SQL:
SELECT TO_CHAR(NVL2('a','b','c')) FROM dual@remote_db;
>
See if that helps.

Help with multiple case statements

Hello,
I am new to BO. I am on XI 3.0. SQL 2005. In Designer, I am trying to create a measure in a financial universe that would end up being multiple case statements within one select. This is what I tried to do, but it doesn't work with the two case statements. Can I use an ELSE leading into the second CASE WHEN somehow? How can I accomplish this? Sorry for my ignorance!
CASE WHEN dbo.ClientBudgetYear.DateStage1Approved > 01/01/1900 AND dbo.ClientBudgetMonth.Month = 12 THEN dbo.ClientBudgetMonth.Stage1Sales END
CASE WHEN dbo.ClientBudgetYear.DateStage1Approved > 01/01/1900 AND dbo.ClientBudgetMonth.Month = 11 THEN dbo.ClientBudgetMonth.Stage1Sales END
Any Suggestions?
Thanks,
Holly

Holly,
I don't know enough about your data or requirement to provide a solution, however, the construct that you post will not work because it causes you to build an object with multiple case statements when only one case statement per object is permitted. From what I see in your code I would be inclined to combine the two statements into one as such:
CASE WHEN dbo.ClientBudgetYear.DateStage1Approved > 01/01/1900 AND dbo.ClientBudgetMonth.Month in (11,12) THEN dbo.ClientBudgetMonth.Stage1Sales else null END
Thanks,
John

Using case statement in merge when matched

Hi,
I want to use case statement in the when matched clause of merge statement to ensure that I update only those fields that are undated.
create table TEST1
NAME1 VARCHAR2(25),
NAME2 VARCHAR2(25),
ID NUMBER not null
create table TEST2
ID NUMBER not null,
ID2 NUMBER not null,
NAME1 VARCHAR2(25),
NAME2 VARCHAR2(25)
merge into test1 t1
using
test2 t2
ON (t1.id = t2.id)
when matched
then
case
when t1.name1 != t2.name1
then
update set t1.name1 != t2.name1
when t1.name2 != t2.name2
then
update set t1.name2 != t2.name2
else
null;
end
it does not work and raises invalid sql command. Any idea how can I do that?
Thanks.
Sajid
Edited by: 808255 on Nov 12, 2010 4:22 AM

Hi
In that case you would have to use multiple statements and you may as well just use UPDATE instead of MERGE. Also, are you sure that you aren't trying to to fix a problem that doesn't actually exist.
Think about where the execution time is going to come from...
I would be tempted to do 1 UPDATE like this...
   UPDATE test1 t1
   SET    (t1.name1,
           t1.name2) = (SELECT t2.name1,
                                t2.name2
                        FROM    test2 t2
                        WHERE t1.id = t2.id
                        AND   (t1.name1 != t2.name1
                         OR    t1.name2 != t2.name2))If you get specific performance issue with this, then post an explain plan and trace and I'll have a look.
I don't this the cost of the update is going to be as great as you think.
Cheers
Ben

Is it possible to use a case statement when joining different tables based on input parameters?

Hi,
I have a scenario where my stored procedure takes 5 parameters and the users can pass NULL or some value to these parameters and based on the parameters, I need to pull data from various tables.
Is it possible to use a case statement in the join, similar the one in the below example. I'm getting error when I use the below type of statement.
select a.*
from a
case
when parameter1=1 then
inner join a on a.id = b.id
when parameter1=2 then
inner join a on a.id = c.id
end;
Please let me know, if this type of statement works, and if it works will it create any performance issues?. If the above doesn't work, could you please give me some alternate solutions?
Thanks.

Here's a technique for joining A to B or C depending on the input parameters. In theory, you are joining to both tables but the execution plan includes filters to skip whichever join is not appropriate. The drawback is that you have to do outer joins, not inner ones.
CREATE TABLE A AS SELECT LEVEL ak FROM dual CONNECT BY LEVEL <= 100;
CREATE TABLE b AS SELECT ak, bk
FROM A, (SELECT LEVEL bk FROM dual CONNECT BY LEVEL <= 10);
CREATE TABLE c(ak, ck) AS SELECT ak, bk*10 FROM b;
variable p1 NUMBER;
variable p2 NUMBER;
exec :p1 := 1;
exec :p2 := 20;
SELECT /*+ gather_plan_statistics */ A.ak, nvl(b.bk, c.ck) otherk FROM A
LEFT JOIN b ON A.ak = b.ak AND :p1 IS NOT NULL AND b.bk = :p1
LEFT JOIN c ON A.ak = c.ak AND :p1 is null and :p2 IS NOT NULL and c.ck = :p2
WHERE A.ak <= 9;
SELECT * FROM TABLE(dbms_xplan.display_cursor(NULL,NULL,'IOSTATS LAST'));
| Id | Operation | Name | Starts | E-Rows | A-Rows | A-Time | Buffers |
| 0 | SELECT STATEMENT | | 1 | | 9 |00:00:00.01 | 7 |
|* 1 | HASH JOIN OUTER | | 1 | 9 | 9 |00:00:00.01 | 7 |
|* 2 | HASH JOIN OUTER | | 1 | 9 | 9 |00:00:00.01 | 7 |
|* 3 | TABLE ACCESS FULL | A | 1 | 9 | 9 |00:00:00.01 | 3 |
| 4 | VIEW | VW_DCL_5532A50F | 1 | 9 | 9 |00:00:00.01 | 4 |
|* 5 | FILTER | | 1 | | 9 |00:00:00.01 | 4 |
|* 6 | TABLE ACCESS FULL| B | 1 | 9 | 9 |00:00:00.01 | 4 |
| 7 | VIEW | VW_DCL_5532A50F | 1 | 9 | 0 |00:00:00.01 | 0 |
|* 8 | FILTER | | 1 | | 0 |00:00:00.01 | 0 |
|* 9 | TABLE ACCESS FULL | C | 0 | 9 | 0 |00:00:00.01 | 0 |
Predicate Information (identified by operation id):
 1 - access("A"."AK"="ITEM_0")
 2 - access("A"."AK"="ITEM_1")
 3 - filter("A"."AK"<=9)
5 - filter(:P1 IS NOT NULL)
 6 - filter(("B"."AK"<=9 AND "B"."BK"=:P1))
 8 - filter((:P2 IS NOT NULL AND :P1 IS NULL))
 9 - filter(("C"."AK"<=9 AND "C"."CK"=:P2))
You can see that table C was not really accessed: the buffer count is 0.
exec :p1 := NULL;
SELECT /*+ gather_plan_statistics */ A.ak, nvl(b.bk, c.ck) otherk FROM A
LEFT JOIN b ON A.ak = b.ak AND :p1 IS NOT NULL AND b.bk = :p1
LEFT JOIN c ON A.ak = c.ak AND :p1 is null and :p2 IS NOT NULL and c.ck = :p2
WHERE A.ak <= 9;
SELECT * FROM TABLE(dbms_xplan.display_cursor(NULL,NULL,'IOSTATS LAST'));
Now table B is not accessed.
| Id | Operation | Name | Starts | E-Rows | A-Rows | A-Time | Buffers | Reads |
| 0 | SELECT STATEMENT | | 1 | | 9 |00:00:00.02 | 7 | 2 |
|* 1 | HASH JOIN OUTER | | 1 | 9 | 9 |00:00:00.02 | 7 | 2 |
|* 2 | HASH JOIN OUTER | | 1 | 9 | 9 |00:00:00.01 | 3 | 0 |
|* 3 | TABLE ACCESS FULL | A | 1 | 9 | 9 |00:00:00.01 | 3 | 0 |
| 4 | VIEW | VW_DCL_5532A50F | 1 | 9 | 0 |00:00:00.01 | 0 | 0 |
|* 5 | FILTER | | 1 | | 0 |00:00:00.01 | 0 | 0 |
|* 6 | TABLE ACCESS FULL| B | 0 | 9 | 0 |00:00:00.01 | 0 | 0 |
| 7 | VIEW | VW_DCL_5532A50F | 1 | 9 | 9 |00:00:00.01 | 4 | 2 |
|* 8 | FILTER | | 1 | | 9 |00:00:00.01 | 4 | 2 |
|* 9 | TABLE ACCESS FULL | C | 1 | 9 | 9 |00:00:00.01 | 4 | 2 |

Case statement 'when IN cursor'

Hi folks.
I am wondering if it is possible to use the IN command within a CASE statement?
I am trying to see if a parameter falls under certain dates in another table. I have a cursor declared which points at that column of dates, and my case statement is like so
case parameter_date when IN certain_dates then if_holiday := 1 else if_holiday := 2 end;
It doesn't like it when I try to compile. And my procedure is listed as being Invalid.
Thanks for any help :)

I am wondering if it is possible to use the IN command within a CASE statement?Yes.
SQL> select dname
2         , case when deptno in ( select deptno from emp )
3                then 'Has staff' else 'empty' end
4 from dept
5 /
DNAME          CASEWHEND
ACCOUNTING     Has staff
RESEARCH       Has staff
SALES          Has staff
OPERATIONS     empty
SQL>What we can't do is use PL/SQL cursors like this
case parameter_date when IN certain_dates then if_holiday := 1 else if_holiday := 2 end;
                            ^^^^^^^^^^^^^They're not variables. At least, not that sort of variable.
Cheers, APC
blog: http://radiofreetooting.blogspot.com

When to use prepared statement in java?

Hi all,
If we have query like select * from {tablename} (Here tablename is the variable) then will the use of prepared staement improve the performance? My guess is use of statement in this case is a better option rather than prepared statement as the tablename may change for every other query.I think are not useful if tablename changes.They are useful only when the where clause has dynamic values.

cantor wrote:
Are you sure that your approach is possible? The next example causes exception for me.
PreparedStatement ps = conn.prepareStatement("select * from ?");
ps.setString(1, "TABLE_NAME");
ps.executeQuery();
I didn't say that he should solve it in that way. He should create one prepared statement like this "select a, b, c from tablename1" and another prepared statement when he wants to execute "select d, e, f from tablename2"
>
And as I understand, this code will not improve perfomance (and even will not work). As I said it can.
Prepared statements make possible usage compiled queries inside DB. When DB gets prepared statement call, it need to parse it only once. And it can collect some statistic to improve execution plan. But when table name is not specified, this approach will not work.Yes it might. There are database drivers that can cache prepared statements and it's isn't likely that he executes that query on more than e.g. 20 tables?
The database can also cache compiled statements in a cache.
Kaj

11g outer join with case statement - strange results.

Hello All,
I am experiencing a strange issues in 11g while using case statement.
I am not able to reproduce this using sample data. Not sure what is wrong.
I am not narrowing it to say the usage of case statemnt is giving wrong results, but that is my observation when I am doing trail and error testing.
Here are the details.
My Version
SQL> select * from v$version;
BANNER
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
PL/SQL Release 11.2.0.2.0 - Production
CORE 11.2.0.2.0 Production
TNS for Linux: Version 11.2.0.2.0 - Production
NLSRTL Version 11.2.0.2.0 - Production
SQL> My Query
SELECT *
FROM (SELECT DISTINCT mf.schedule,
 mf.cptcode,
 NVL (mf.modifier, '00') modifier2,
 CASE
 WHEN mf.feetype = 'H'
 AND mf.multiplier IS NOT NULL THEN
 ' 0.00'
 WHEN (mf.feetype != 'H'
 OR mf.feetype IS NULL)
 AND mf.rbrvsvalue IS NOT NULL
 AND mf.multiplier IS NOT NULL THEN
 LPAD ( TRIM (TO_CHAR ( (mf.rbrvsvalue * mf.multiplier) / 100, 9999999.99)), 10)
 ELSE
 NULL
 END
 fee
 FROM provider.mpifee mf, mpi_udffee.udffeeactivecptcodes vld
 WHERE mf.schedule = 'SAPG1'
 AND mf.cptcode = vld.cptcode
 AND NVL (mf.modifier, 'NULL') = NVL (vld.modifier, 'NULL')) inline_fee,
 (SELECT arc.schedule col1, arc.procedurecode col2, NVL (arc.modifier, '00') AS col3
 FROM mpi_udffee.udffeeancfeedata arc
 WHERE monthofextract = '201202'
 AND arc.schedule = 'SAPG1'
 AND TRUNC (SYSDATE - 10) BETWEEN arc.recordeffectivedate AND arc.recordterminationdate) inline_data
WHERE inline_fee.schedule = inline_data.col1(+)
 AND inline_fee.cptcode = inline_data.col2(+)
 AND inline_fee.modifier2 = inline_data.col3(+);
In the above query the inline view inline_data returns zero rows. but NVL is still getting applied for col3 and I am getting 00 in the results( strange ).
Results:
SCHEDULE CPTCO MODIFIER2 FEE COL1 COL2 COL3
SAPG1 49590 00 667.32 00
SAPG1 49611 00 781.03 00
SAPG1 49905 00 443.79 00
SAPG1 50205 00 883.56 00
SAPG1 50220 00 1315.15 00
SAPG1 50230 00 1638.74 00
SAPG1 50234 00 1666.16 00
SAPG1 50250 00 1566.14 00
SAPG1 50327 00 262.04 00
SAPG1 50541 00 1183.31 00
SAPG1 50620 00 1156.88 00
SAPG1 50650 00 1321.96 00
497 rows selected.
Just the inline view inline_data,
SQL> SELECT arc.schedule col1, arc.procedurecode col2, NVL (arc.modifier, '00') AS col3
2 FROM mpi_udffee.udffeeancfeedata arc
3 WHERE monthofextract = '201202'
4 AND arc.schedule = 'SAPG1'
5 AND TRUNC (SYSDATE - 10) BETWEEN arc.recordeffectivedate AND arc.recordterminationdate;
no rows selectedMuch unusual thing is when I just remove the case statement from the inline view "inline_fee", I am getting right results,
SELECT *
FROM (SELECT DISTINCT mf.schedule,
 mf.cptcode,
 NVL (mf.modifier, '00') modifier2 <-- Removed Case statement here
 FROM provider.mpifee mf, mpi_udffee.udffeeactivecptcodes vld
 WHERE mf.schedule = 'SAPG1'
 AND mf.cptcode = vld.cptcode
 AND NVL (mf.modifier, 'NULL') = NVL (vld.modifier, 'NULL')) inline_fee,
 (SELECT arc.schedule col1, arc.procedurecode col2, NVL (arc.modifier, '00') AS col3
 FROM mpi_udffee.udffeeancfeedata arc
 WHERE monthofextract = '201202'
 AND arc.schedule = 'SAPG1'
 AND TRUNC (SYSDATE - 10) BETWEEN arc.recordeffectivedate AND arc.recordterminationdate) inline_data
WHERE inline_fee.schedule = inline_data.col1(+)
 AND inline_fee.cptcode = inline_data.col2(+)
 AND inline_fee.modifier2 = inline_data.col3(+);
SCHEDULE CPTCO MODIFIER2 COL1 COL2 COL3
SAPG1 46730 00
SAPG1 46735 00
SAPG1 46748 00
SAPG1 46760 00
SAPG1 46942 00
SAPG1 46945 00
SAPG1 47015 00
SAPG1 47125 00
SAPG1 47350 00
SAPG1 47505 00
SAPG1 47553 00interestingly explain plan for both the statements are exactly same,
SELECT STATEMENT ALL_ROWSCost: 138 Bytes: 1,078,274 Cardinality: 11,471
 9 HASH JOIN RIGHT OUTER Cost: 138 Bytes: 1,078,274 Cardinality: 11,471
 2 PARTITION RANGE EMPTY Cost: 2 Bytes: 150 Cardinality: 3
 1 TABLE ACCESS FULL TABLE MPI_UDFFEE.UDFFEEANCFEEDATA Cost: 2 Bytes: 150 Cardinality: 3
 8 VIEW MPI_UDFFEE. Cost: 135 Bytes: 504,724 Cardinality: 11,471
 7 HASH UNIQUE Cost: 135 Bytes: 539,137 Cardinality: 11,471
 6 HASH JOIN Cost: 134 Bytes: 539,137 Cardinality: 11,471
 3 TABLE ACCESS FULL TABLE MPI_UDFFEE.UDFFEEACTIVECPTCODES Cost: 13 Bytes: 177,345 Cardinality: 25,335
 5 PARTITION LIST SINGLE Cost: 120 Bytes: 600,600 Cardinality: 15,015 Partition #: 8
 4 INDEX RANGE SCAN INDEX (UNIQUE) REPRICE.PK_MPIFEE Cost: 120 Bytes: 600,600 Cardinality: 15,015 Partition #: 9 Partitions accessed #11Is there anything wrong with the query? If not have anyone come across this issue or posted it as a bug or is there a patch?
Update:
when I set the parameter "_complex_view_merging"=false I am getting the right results even with case statement. But I don want to do some thing unsupported.
Are there any other viable solutions?
I appreciate the help.
Thanks,
G.
Edited by: Ganesh Srivatsav on Apr 10, 2012 12:37 PM

Hi Tubby,
Right, the query transformation is going wrong. Following is from trace,
SELECT "INLINE_FEE"."SCHEDULE" "SCHEDULE",
 "INLINE_FEE"."CPTCODE" "CPTCODE",
 "INLINE_FEE"."MODIFIER2" "MODIFIER2",
 "INLINE_FEE"."FEE" "FEE",
 "ARC"."SCHEDULE" "COL1",
 "ARC"."PROCEDURECODE" "COL2",
 CASE
 WHEN "ARC".ROWID IS NOT NULL THEN NVL ("ARC"."MODIFIER", '00')
 ELSE NULL
 END
 "COL3"
FROM (SELECT DISTINCT "MF"."SCHEDULE" "SCHEDULE",
 "MF"."CPTCODE" "CPTCODE",
 NVL ("MF"."MODIFIER", :B2) "MODIFIER2",
 CASE
 WHEN ("MF"."FEETYPE" = :B3
 AND "MF"."MULTIPLIER" IS NOT NULL) THEN
 :B4
 WHEN ( ("MF"."FEETYPE" <> :B5
 OR "MF"."FEETYPE" IS NULL)
 AND "MF"."RBRVSVALUE" IS NOT NULL
 AND "MF"."MULTIPLIER" IS NOT NULL) THEN
 LPAD ( TRIM (TO_CHAR ( "MF"."RBRVSVALUE" * "MF"."MULTIPLIER" / :B6, :B7)), :B8)
 ELSE
 NULL
 END
 "FEE"
 FROM "PROVIDER"."MPIFEE" "MF", "MPI_UDFFEE"."UDFFEEACTIVECPTCODES" "VLD"
 WHERE "MF"."SCHEDULE" = 'SAPG1'
 AND "MF"."CPTCODE" = "VLD"."CPTCODE"
 AND NVL ("MF"."MODIFIER", 'NULL') = NVL ("VLD"."MODIFIER", 'NULL')) "INLINE_FEE",
 "MPI_UDFFEE"."UDFFEEANCFEEDATA" "ARC"
WHERE "INLINE_FEE"."SCHEDULE" = "ARC"."SCHEDULE"(+)
 AND "INLINE_FEE"."CPTCODE" = "ARC"."PROCEDURECODE"(+)
 AND "INLINE_FEE"."MODIFIER2" = CASE
 WHEN ("ARC".ROWID(+) IS NOT NULL) THEN NVL ("ARC"."MODIFIER"(+), '00')
 ELSE NULL
 END
 AND "ARC"."MONTHOFEXTRACT"(+) = '201202'
 AND "ARC"."SCHEDULE"(+) = 'SAPG1'
 AND TRUNC (SYSDATE-10) >= "ARC"."RECORDEFFECTIVEDATE"(+)
 AND TRUNC (SYSDATE-10) <= "ARC"."RECORDTERMINATIONDATE"(+)Does this refer to a specific bug?
Thanks,
G.

Case Statement ....please help :)

Hi Guys\Gals,
Just wondering if anyone can tell me the correct usage of the case statement:)
I want to select counts for particular date ranges to come out as seperate columns.
Is the Sql Server Case appliable in oracle circumstances?
This is what im doing:
select count(case when to_char(logtime,'MM') = '01' then source else 0 end) as January
from messagetransactionlog
SQL Error: ORA-00932: inconsistent datatypes: expected CHAR got NUMBER
Then im getting something like from keyword not found!!
Plz help :)
Thanks
Robert

Hopefully im not boring people now :)
can the case statement, as follows:
count(case when logtime = '07-07' then UNIQUES else null end) as Jul
be changed to only count distinct rows?
count distinct (case when logtime = '07-07' then UNIQUES else null end) as Jul
#SQL Error: ORA-00923: FROM keyword not found where expected
count (case when logtime = '07-07' then distinct UNIQUES else null end) as Jul
#SQL Error: ORA-00923: FROM keyword not found where expected

[svn:fx-trunk] 7830: Update ASDoc on the new backgroundFrameRate property to WindowedApplication , to by default reduce the CPU usage in cases where an app is not 'active'.

Revision: 7830
Author:   [email protected]
Date:     2009-06-14 15:57:29 -0700 (Sun, 14 Jun 2009)
Log Message:
Update ASDoc on the new backgroundFrameRate property to WindowedApplication, to by default reduce the CPU usage in cases where an app is not 'active'.
Bugs: SDK-21135
Reviewer:
QE Notes:
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-21135
Modified Paths:
    flex/sdk/trunk/frameworks/projects/airframework/src/mx/core/WindowedApplication.as
    flex/sdk/trunk/frameworks/projects/airframework/src/spark/components/WindowedApplication. as

By the way, I agree with sybrand: you need to tune
your redo log size.
Regards
Ignacio
http://oracledisect.blogspot.com
Ignacio,
The excessive waits on log file parallel write and the related client wait of log file sync may be due to insufficient CPU availability, and may not point at an actual redo log size problem or a problem with the disk speed where the redo is written to disk, especially if there are 3 Oracle instances on the server with a single CPU.
Paraphrased from "Optimizing Oracle Performance":
The log file sync wait event is one of the first events to show increased latencies due to the time a process spends waiting in a CPU wait queue while processing excessive logical IOs.
Kevin Closson wrote a couple blog entries that examined the potential problems of insufficient CPU capacity and its effects on log file parallel write when writing to solid state disks, and even when writing redo was explicitly disabled:
http://kevinclosson.wordpress.com/2007/07/21/manly-men-only-use-solid-state-disk-for-redo-logging-lgwr-io-is-simple-but-not-lgwr-processing/
"Once LGWR loses his CPU it may be quite some time until he gets it back. For instance, if LGWR is preempted in the middle of trying to perform a redo buffer flush, there may be several time slices of execution for other processes before LGWR gets back on CPU..." Fix the CPU problem, and the other significant waits may decrease.
JesusLuvR,
yingkuan's suggestion to look at the SQL statement that performs the 4,365,564 logical IOs, consumes 186.03 CPU seconds, and has an execution time of 225.06 seconds, is likely a very good starting point. You might also want to check the value of the SESSION_CACHED_CURSORS parameter to see if it needs to be adjusted.
Charles Hooper
IT Manager/Oracle DBA
K&M Machine-Fabricating, Inc.

SQL Expression in decode function or case statement?

Can I put SQL expressions in decode function or case statement?
For example,
select le.profile, decode( select count(1) from profile_data where NAME= 'XXXX_AFTER' and object_id = le.profile, 0, 'N', 'Y')
from element le;
or
select le.profile, case WHEN ( select count(1) from profile_data where NAME= 'XXXX_AFTER' and object_id = le.profile) = 0 THEN 'N'
ELSE 'Y'
from element le;
None of the above work.
Can anyone tell me how to make it work?
Is there any workaround?
Thanks,
J

You simply needed and END to your CASE statement;
SQL> with profile_data as (
   select 'XXXX_AFTER' name, 1 object_id from dual),
     element as (
   select 1 profile from dual union all
   select 2 from dual)
select le.profile,
   case WHEN ( select count(1) from profile_data where NAME= 'XXXX_AFTER' and object_id = le.profile) = 0
   THEN 'N'
   ELSE 'Y'
   END new_col
from element le
   PROFILE N
         1 Y
         2 N

CASE not found while executing CASE statement on Submit Form

Hi to all APEX users and developers.
I have several APEX applications and they are all working well, but recently I got one strange exception when I try to submit page:
Session: Fetch session header information
...metadata, fetch page info
...Validate item page affinity.
...Validate hidden_protected items.
Add error onto error stack
...Error data:
......message: Error processing request.
......additional_info: ORA-06592: CASE not found while executing CASE statement
......display_location: ON_ERROR_PAGE
......is_internal_error: true
......apex_error_code: APEX.UNHANDLED_ERROR
......ora_sqlcode: -6592
......ora_sqlerrm: ORA-06592: CASE not found while executing CASE statement
.....error_backtrace: ORA-06512: at "APEX_040100.WWV_FLOW", line 9273
......component.type: APEX_APPLICATION_AUTH
......component.id: 41350431648668800
......component.name: MNRFR
...Show Error on Error Page
......Performing rollback
Processes - point: AFTER_ERROR_HEADER
Processes - point: BEFORE_ERROR_FOOTER
End Page Processinga
Page has more than 120 items (most of them are hidden), so my first thought is that page has problem with posting so many items, but APEX error message doesn't hel me at all. Any help would be very appreciated :)
Almir

Hi Almir,
actually it is the 100 page item limit. See (http://download.oracle.com/docs/cd/E17556_01/doc/user.40/e15517/limits.htm)
I also had a look into the source code and the code at the position where the error gets raised only supports 100 page items.
Can you have a look into the generated HTML code and look if you have a page items which is mapped to p_t101 or a higher number ?
I will file a bug to show a better error message.
Regards
Patrick
My Blog: http://www.inside-oracle-apex.com
APEX Plug-Ins: http://apex.oracle.com/plugins
Twitter: http://www.twitter.com/patrickwolf

Regading WHEN usage in CASE statement

Similar Messages

Maybe you are looking for