Inconsistent ESB results

Hi
I have been trying to resolve a problem with an ESB, so I created a POC ESB to test the problem.
I have an ESB with 2 routing services:
The first routing service calls partner link A which is a database adaptor that inserts a record into the database.
The routing service has inut and output variables although the output variables are not assigned values. So effectively it is an asynchronous routing service.
The second routing service is exactly the same but does not have output variables. It calls the same partner link A to insert records.
I am calling each routing service seperately from a bpel process to test the outcomes.
The problem I am encountering is as follows.
When the database is down the first routing service fails and a fault is returned with with ORABPEL-08034 JTA Rollback requested details. However the returned fault is not caught in the BPEL process and when the ESB fails the BPEL process just fails and hangs.
When the database is down and the second routing service fails a JaxRpc Invoke: binding fault is returned and the process catches the fault in a catchall which means the process can conitnue.
Is there a problem with passing variables out of an ESB services? Does it mean that when there are output variables form any ESB then faults are not handled? this is a major issue because I have a system that requires ESB services to retrieve information from the database. If these cannot handle database down or other faults then this is a major issue.

Hi,
I applied the patch MLR6 and now has following scenario.
ESB is not even returning any fault when database adapter operation fails. I have been through the documentation available in Metalink and as per that the problem ESB Does Not Return Faults to BPEL (doc id 728491.1) should have been solved after applying MLR6.
This is referenced with bug no 5997936 which has been solved even before that in 10.1.3.4 Patchset for Oracle Application Server 10g Release 3.
Now I am confused. Please help. Following is the error log for reference
An unhandled exception has been thrown in the ESB system. The exception reported is: "org.collaxa.thirdparty.apache.wsif.WSIFException: esb:///ESB_Projects/TestESBServices_TestDBAdapters/PersonDetailsDBService1.wsdl [ PersonDetailsDBService1_ptt::insert(PersonDetailsCollection) ] - WSIF JCA Execute of operation 'insert' failed due to: DBWriteInteractionSpec Execute Failed Exception. insert failed. Descriptor name: [PersonDetailsDBService1.PersonDetails]. [Caused by: ORA-01400: cannot insert NULL into ("ESBADMIN"."PERSON_DETAILS"."LOGICAL_DELETE") ] ; nested exception is: ORABPEL-11616 DBWriteInteractionSpec Execute Failed Exception. insert failed. Descriptor name: [PersonDetailsDBService1.PersonDetails]. [Caused by: ORA-01400: cannot insert NULL into ("ESBADMIN"."PERSON_DETAILS"."LOGICAL_DELETE") ] Caused by Exception [TOPLINK-4002] (Oracle TopLink - 10g Release 3 (10.1.3.4.0) (Build 080602)): oracle.toplink.exceptions.DatabaseException Internal Exception: java.sql.BatchUpdateException: ORA-01400: cannot insert NULL into ("ESBADMIN"."PERSON_DETAILS"."LOGICAL_DELETE") Error Code: 1400. at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:644) at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeInputOnlyOperation(WSIFOperation_JCA.java:739) at oracle.tip.esb.server.common.wsif.WSIFInvoker.executeOperation(WSIFInvoker.java:927) at oracle.tip.esb.server.common.wsif.WSIFInvoker.nextService(WSIFInvoker.java:842) at oracle.tip.esb.server.common.wsif.WSIFInvoker.nextService(WSIFInvoker.java:865) at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.nextService(OutboundAdapterService.java:231) at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.processBusinessEvent(OutboundAdapterService.java:138) at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatchNonRoutingService(InitialEventDispatcher.java:411) at oracle.tip.esb.server.dispatch.InitialEventDispatch

Similar Messages

Inconsistent SDO_RELATE results when querying 2.5D data

Oracle 11.1.0.7 with Patch 8343061 on Windows Server 2003 32bit.
I'm getting inconsistent results from SDO_RELATE results when querying 2.5D data. Some geometries I expect to be OVERLAPBDYDISJOINT, are not always being returned by SDO_RELATE when using the OVERLAPBDYDISJOINT mask. It seems that the order of the tables makes a difference to the result.
Here's a table with one 2.5D geometry and a 2D index:
CREATE TABLE TEST1 (
ID                NUMBER PRIMARY KEY,
GEOMETRY     SDO_GEOMETRY);
INSERT INTO TEST1 (id, geometry) VALUES (
1,
SDO_GEOMETRY(3002, 2157, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(561695.935, 834005.726, 25.865,
561696.229, 834005.955, 25.867, 561686.278, 834015.727, 26.088, 561685.179, 834019.771, 26.226, 561680.716, 834022.389, 26.226,
561674.434, 834025.125, 26.171, 561671.963, 834032.137, 25.667, 561670.832, 834037.185, 25.619, 561667.946, 834042.976, 25.84,
561666.717, 834047.218, 26.171, 561664.229, 834051.781, 26.778, 561660.041, 834055.935, 26.64, 561657.514, 834061.742, 26.53,
561658.59, 834067.116, 27.882, 561657.67, 834070.739, 28.821, 561653.028, 834073.777, 29.042, 561653.234, 834078.769, 28.379,
561658.336, 834080.105, 29.511, 561664.582, 834079.468, 31.94, 561669.257, 834075.821, 33.707, 561672.716, 834074.456, 33.707,
561676.875, 834077.262, 33.735, 561675.868, 834081.55, 33.707, 561673.131, 834087.641, 33.679, 561672.208, 834093.502, 33.238,
561668.578, 834100.894, 33.735, 561666.013, 834106.399, 33.679, 561661.408, 834111.23, 33.514, 561654.854, 834117.181, 33.486,
561651.695, 834122.292, 33.569, 561649.112, 834128.847, 33.431, 561645.982, 834134.786, 33.293, 561642.485, 834141.235, 33.072,
561642.138, 834150.085, 33.293, 561646.072, 834159.721, 36.578, 561647.274, 834165.532, 37.02, 561646.359, 834170.867, 37.02,
561645.42, 834175.485, 36.799, 561642.44, 834180.977, 36.826, 561638.677, 834185.419, 36.771, 561636.693, 834194.824, 37.158,
561635.462, 834202.105, 37.241, 561631.998, 834208.745, 37.268, 561628.871, 834213.994, 37.241, 561627.554, 834220.393, 37.82,
561625.79, 834226.697, 39.532, 561620.561, 834236.494, 39.891, 561619.265, 834249.687, 39.697, 561619.883, 834260.02, 41.326,
561620.977, 834264.399, 43.093, 561622.557, 834270.723, 43.452, 561622.172, 834276.978, 43.452, 561621.347, 834285.541, 43.479,
561622.214, 834292.055, 43.645, 561619.718, 834302.583, 43.755, 561616.762, 834316.47, 43.755, 561608.842, 834328.241, 43.7,
561606.346, 834334.93, 43.7, 561605.27, 834341.929, 43.7, 561603.925, 834350.648, 43.728, 561602.462, 834358.405, 43.838,
561599.552, 834366.629, 44.031, 561594.551, 834374.291, 43.396, 561590.644, 834383.986, 43.065, 561588.48, 834392.21, 44.942,
561586.923, 834397.32, 46.737, 561584.608, 834402.898, 49.299, 561581.389, 834410.194, 50.077, 561580.437, 834419.49, 51.907,
561580.438, 834427.63, 53.127, 561582.245, 834433.389, 55.791, 561586.664, 834433.397, 57.503, 561593.88, 834433.608, 57.475,
561596.305,834439.653, 57.42, 561591.804, 834445.862, 57.309, 561589.097, 834447.689, 57.014)));
SELECT sdo_geom.validate_geometry_with_context(geometry, 0.0005) FROM TEST1;
DELETE FROM user_sdo_geom_metadata WHERE table_name = 'TEST1' AND column_name = 'GEOMETRY';
INSERT INTO user_sdo_geom_metadata VALUES ('TEST1','GEOMETRY',
     MDSYS.SDO_DIM_ARRAY(
     MDSYS.SDO_DIM_ELEMENT('X',400000,750000,0.0005),
     MDSYS.SDO_DIM_ELEMENT('Y',500000,1000000,0.0005),
     MDSYS.SDO_DIM_ELEMENT('Z',-10000,10000,0.0005)
), 2157);
DROP INDEX TEST1_SPIND;
CREATE INDEX TEST1_SPIND ON TEST1(GEOMETRY) INDEXTYPE IS MDSYS.SPATIAL_INDEX PARAMETERS ('layer_gtype=line sdo_indx_dims=2');And here's another table with a 2D geometry and a 2D index:
CREATE TABLE TEST2 (
ID                NUMBER PRIMARY KEY,
GEOMETRY     SDO_GEOMETRY);
INSERT INTO TEST2 (id, geometry) VALUES (
1,
SDO_GEOMETRY(2002, 2157, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(561816.516, 834055.581, 561819.504, 834057.173,
561817.942, 834060.818, 561810.044, 834078.997, 561805.576, 834087.634, 561801.572, 834094.299, 561798.558, 834100.467,
561796.254, 834107.637, 561793.754, 834115.605, 561794.049, 834123.694, 561793.698, 834130.518, 561792.905, 834138.883,
561787.867, 834145.772, 561782.544, 834150.548, 561777.707, 834156.53, 561773.945, 834161.32, 561771.061, 834166.957,
561768.155, 834173.131, 561764.735, 834178.744, 561759.603, 834187.782, 561756.146, 834195.493, 561753.416, 834198.821,
561754.141, 834205.691, 561756.768, 834209.681, 561757.217, 834216.701, 561753.086, 834232.46, 561744.371, 834254.589,
561740.936, 834263.001, 561737.198, 834272.208, 561732.231, 834284.915, 561730.52, 834297.01, 561728.339, 834310.053,
561727.825, 834328.069, 561730.461, 834342.992, 561729.808, 834367.948, 561730.216, 834396.988, 561732.273, 834419.047,
561732.783, 834424.668, 561731.647, 834432.212, 561731.872, 834439.436, 561731.39, 834449.269, 561732.041, 834462.813,
561733.583, 834471.926, 561733.229, 834485.049, 561730.868, 834498.462, 561726.379, 834512.59, 561725.776, 834528.932,
561727.488, 834555.23, 561729.357, 834577.873, 561731.05, 834595.931, 561731.163, 834611.928, 561734.057, 834637.031,
561732.67, 834636.4, 561725.401, 834633.796, 561721.039, 834632.493, 561718.777, 834632.167, 561710.437, 834632.888,
561647.929, 834636.658, 561644.963, 834630.085, 561632.796, 834629.813, 561625.553, 834627.647, 561620.473, 834626.711,
561608.718, 834624.94, 561599.935, 834619.684, 561596.67, 834613.843, 561594.27, 834607.774, 561592.513, 834601.752,
561591.349, 834593.899, 561597.265, 834584.888, 561595.956, 834571.479, 561595.075, 834556.196, 561593.997, 834539.68,
561594.316, 834528.071, 561595.261, 834516.44, 561595.538, 834504.804, 561597.227, 834497.417, 561599.3, 834490.416,
561601.265, 834482.61, 561605.126, 834475.502, 561599.232, 834473.683, 561593.076, 834471.379, 561599.154, 834451.112,
561589.097, 834447.689, 561591.804, 834445.862, 561596.305, 834439.653, 561593.88, 834433.608, 561582.245, 834433.389,
561580.438, 834427.63, 561580.437, 834419.49, 561581.389, 834410.194, 561584.608, 834402.898, 561586.923, 834397.32,
561588.48, 834392.21, 561590.644, 834383.986, 561594.551, 834374.291, 561599.552, 834366.629, 561602.462, 834358.405,
561603.925, 834350.648, 561605.27, 834341.929, 561606.346, 834334.93, 561608.842, 834328.241, 561616.762, 834316.47,
561619.718, 834302.583, 561622.214, 834292.055, 561621.347, 834285.541, 561622.172, 834276.978, 561622.557, 834270.723,
561620.977, 834264.399, 561619.883, 834260.02, 561619.265, 834249.687, 561620.561, 834236.494, 561625.79, 834226.697,
561627.554, 834220.393, 561628.871, 834213.994, 561631.998, 834208.745, 561635.462, 834202.105, 561636.693, 834194.824,
561638.677, 834185.419, 561642.44, 834180.977, 561645.42, 834175.485, 561646.359, 834170.867, 561647.274, 834165.532,
561646.072, 834159.721, 561642.138, 834150.085, 561642.485, 834141.235, 561645.982, 834134.786, 561649.112, 834128.847,
561651.695, 834122.292, 561654.854, 834117.181, 561661.408, 834111.23, 561666.013, 834106.399, 561668.578, 834100.894,
561672.208, 834093.502,561673.131, 834087.641, 561675.868, 834081.55, 561676.875, 834077.262, 561672.716, 834074.456,
561669.257, 834075.821, 561664.582, 834079.468, 561658.336, 834080.105, 561653.234, 834078.769, 561653.028, 834073.777,
561657.67, 834070.739, 561658.59, 834067.116, 561657.514, 834061.742, 561660.041, 834055.935, 561664.229, 834051.781,
561666.717, 834047.218, 561667.946, 834042.976, 561670.832, 834037.185, 561671.963, 834032.137, 561674.434, 834025.125,
561680.716, 834022.389, 561685.179, 834019.771, 561686.278, 834015.727, 561696.229, 834005.955, 561695.935, 834005.726,
561677.805, 833994.91, 561683.163, 833985.817, 561703.01, 833949.434, 561725.891, 833961.856, 561744.35, 833971.197,
561768.396, 833983.86, 561777.842, 833988.883, 561798.333, 833999.743, 561797.243, 834005.725, 561783.574, 834040.515,
561798.127, 834046.391, 561807.001, 834050.509, 561816.516, 834055.581)));
SELECT sdo_geom.validate_geometry_with_context(geometry, 0.0005) FROM TEST2;
DELETE FROM user_sdo_geom_metadata WHERE table_name = 'TEST2' AND column_name = 'GEOMETRY';
INSERT INTO user_sdo_geom_metadata VALUES ('TEST2','GEOMETRY',
     MDSYS.SDO_DIM_ARRAY(
     MDSYS.SDO_DIM_ELEMENT('X',400000,750000,0.0005),
     MDSYS.SDO_DIM_ELEMENT('Y',500000,1000000,0.0005)
), 2157);
DROP INDEX TEST2_SPIND;
CREATE INDEX TEST2_SPIND ON TEST2(GEOMETRY) INDEXTYPE IS MDSYS.SPATIAL_INDEX PARAMETERS ('layer_gtype=line sdo_indx_dims=2');Now if I check how these two geometries relate to each other, the answer is OVERLAPBDYDISJOINT, which makes sense when inspecting the geometries.
SQL> SELECT
2 sdo_geom.relate(t1.geometry, 'determine', t2.geometry, 0.0005) relate_1_to_2,
3 sdo_geom.relate(t2.geometry, 'determine', t1.geometry, 0.0005) relate_2_to_1
4 FROM test2 t2, test1 t1
5 WHERE t1.id = t2.id;
RELATE_1_TO_2        RELATE_2_TO_1
OVERLAPBDYDISJOINT   OVERLAPBDYDISJOINT
1 row selected.So, I'd expect this query to return something...
SELECT /*+ ORDERED */ t1.id, t2.id, sdo_geom.relate(t1.geometry, 'determine', t2.geometry, 0.0005) relate
FROM test2 t2, test1 t1
WHERE sdo_relate(t1.geometry, t2.geometry, 'mask=overlapbdydisjoint') = 'TRUE'
AND t1.id = 1
AND t2.id = 1;Nada. And this...
SELECT /*+ ORDERED */ t1.id, t2.id, sdo_geom.relate(t1.geometry, 'determine', t2.geometry, 0.0005) relate
FROM test1 t1, test2 t2
WHERE sdo_relate(t2.geometry, t1.geometry, 'mask=overlapbdydisjoint') = 'TRUE'
AND t1.id = 1
AND t2.id = 1;Nada.
And this...
SQL> SELECT /*+ ORDERED */ t1.id, t2.id, sdo_geom.relate(t1.geometry, 'determine', t2.geometry, 0.0005) relate
2 FROM test2 t2, test1 t1
3 WHERE sdo_relate(t2.geometry, t1.geometry, 'mask=overlapbdydisjoint') = 'TRUE'
4 AND t1.id = 1
5 AND t2.id = 1;
        ID         ID RELATE
         1          1 OVERLAPBDYDISJOINT
1 row selected.This version gives the right answer.
Can anyone explain this?

Hi,-
I think you are running into these bugs 7158518 and 7710726.
Could you please request the patch for the bugs so that they are published on Metalink
if they dont exist there?
Please let us know if these fix your problem.
Best regards
baris

Inconsistent Query Result in SEM-BCS using Virtual Info Provider

We have just upgraded to BW 7.0 and SEM-BCS 6.0. When we run an existing 3.5 BW query for BCS through the Virtual Info Provider against the basic consolidation cube, we are getting inconsistent results. Sometimes we get the correct result, and other times our results are not rolling up correctly causing an out of balance on our balance sheet query. We did not make any hierarchy changes between the query executions. Has anyone else experienced this? We cannot see the cause of the inconsistency. Everything looks good when running through RSRT DEBUG. Any help on pushing us in the right direction to solve this would be appreciated.
Thanks,
Rob

Hi Rob,
Could you please let me know how you have resolved this issue? Thanks.
Regards,
Ashok

Getting Inconsistent Query Results

I am getting inconsistent results when trying to filter data based on the DATETIME stamp. Any help will be appreciated.
Here is my table information.
TableA:
SR DATE
15     8/30/2007 9:34:41 AM
16     9/4/2007 1:03:38 PM
17     9/4/2007 2:50:48 PM
18     9/4/2007 3:04:03 PM
19     9/5/2007 11:47:58 AM
20     9/5/2007 12:16:23 PM
21     9/6/2007 3:34:38 PM
22     9/6/2007 3:43:27 PM
23     9/6/2007 3:46:27 PM
24     9/7/2007 10:14:26 AM
25     9/7/2007 10:16:11 AM
26     9/18/2007 1:03:47 PM
27     9/19/2007 9:31:14 AM
28     9/19/2007 9:44:36 AM
29     9/19/2007 4:18:05 PM
30     9/21/2007 10:44:52 AM
Now if I execute this query,
SELECT * FROM TableA WHERE DATE >= '9/3/2007 9:34:41 AM'
Result (Missing all 2 digit dates:
16     9/4/2007 1:03:38 PM
17     9/4/2007 2:50:48 PM
18     9/4/2007 3:04:03 PM
19     9/5/2007 11:47:58 AM
20     9/5/2007 12:16:23 PM
21     9/6/2007 3:34:38 PM
22     9/6/2007 3:43:27 PM
23     9/6/2007 3:46:27 PM
24     9/7/2007 10:14:26 AM
25     9/7/2007 10:16:11 AM
If I change the day in query to 2 digit then I am getting correct results.
SELECT * FROM TableA WHERE DATE >= '9/03/2007 9:34:41 AM'
But If I run this query:
SELECT * FROM TableA WHERE DATE >= '9/05/2007 9:34:41 AM'
Results (Getting all the dates even less than '9/5/2007':
16     9/4/2007 1:03:38 PM
17     9/4/2007 2:50:48 PM
18     9/4/2007 3:04:03 PM
19     9/5/2007 11:47:58 AM
20     9/5/2007 12:16:23 PM
21     9/6/2007 3:34:38 PM
22     9/6/2007 3:43:27 PM
23     9/6/2007 3:46:27 PM
24     9/7/2007 10:14:26 AM
25     9/7/2007 10:16:11 AM
26     9/18/2007 1:03:47 PM
27     9/19/2007 9:31:14 AM
28     9/19/2007 9:44:36 AM
29     9/19/2007 4:18:05 PM
30     9/21/2007 10:44:52 AM
The results are so inconsistent with different combination, I could not figure out the main reason behind this.
The datatype for this field in database is "VARCHAR2(250)" and because of some restrictions, I could not change datatype of this field in the table.

SQL> DESC t;
Name                                      Null?    Type
COL                                                VARCHAR2(50)
SQL> SELECT col FROM t ORDER BY col;
COL
8/30/2007 9:34:41 AM
9/03/2007 9:34:41 AM
9/05/2007 9:34:41 AM
9/18/2007 1:03:47 PM
9/19/2007 4:18:05 PM
9/19/2007 9:31:14 AM
9/19/2007 9:44:36 AM
9/21/2007 10:44:52 AM
9/3/2007 9:34:41 AM
9/4/2007 1:03:38 PM
9/4/2007 2:50:48 PM
9/4/2007 3:04:03 PM
9/5/2007 11:47:58 AM
9/5/2007 12:16:23 PM
9/6/2007 3:34:38 PM
9/6/2007 3:43:27 PM
9/6/2007 3:46:27 PM
9/7/2007 10:14:26 AM
9/7/2007 10:16:11 AMThe ones in bold are your predicate "dates". Do you see why it doesn't work as you expect?
John

Inconsistent MRP results

Dear Sir / Madam
Our users are continuously complaining that the MRP results are inconsistent. We are using MD61 transaction for entering Planned Independant Requirements. Planning run is executed using 1 3 1 3 1 parameters in md01. We are using multi level BOMs. Backflush indicator 1. Strategy group for BOM components is 40. Strategy group 11 is used for FG.
KIndly suggest how to get consistent MRP results.
Thanks in advance.

Dear Sagar ,
I would like to comment on the same issue that MRP is one of the most high level functionality in SAP specially in supply chain , which is intregarted with core module like MM-SD-PP-PS-FICO etc .
There are two different aspect which one should be very much aware about MRP : Excution of MRP based on business requirement based on Demand situation and Analysing the MRP result for decision making as a planner ( Why did it happen -What needs to be done ) .There are bvarious exception messages MRP generates in MD04-Dyanamic result which indicates the reason and needs farther investigation to conclude on the result .
Now in your case , as you have mentioned some of the activity . I would suggest the following :
1.Re-check the MRP excution parameters selection in MD01/MD02/MD03 ( Processing Key -NETCH , Create PR-2 OR 1 , MRP List -3 , Scheudle Line -3 , Planning Mode -1 for frist time , 3-Delete and re-create )
2.Check all the MRP1-MRP4 parameters .Specially for depedent compoenets , you must have BOM explosion and selection methods is important and OPPQ-Carry all over all plant parameters -BOM explosion is very important .
3.If you delete planned order , then open demand or current demand will be treated in MRP and it will generate planned order based on the planning horzon or Process key seletion .
4.Finally , it needs extensive training and understanding for user level to have clarity on MRP concept .
Hope its helps
Reagrds
JH

Inconsistent SELECT results in PL/SQL package

Inside an Oracle package, I populate variables with "SELECT ... INTO ... FROM <table name> WHERE ...;"
Should be straightforward, but I have found it inconsistent. Sometimes the variables are not populated, sometimes they are (using the same WHERE). Any possible reasons for this behavior?
Edited by: user12236430 on Jan 31, 2012 5:46 AM

user12236430 wrote:
I'll bring a snippet home from the office with me. It doesn't throw the NO_DATA_FOUND exception, because one of the variables it (sometimes) populates is used in an INSERT later, and when it's not set I get a "Precision Error occurred" exception. It's straightforward PL/SQL as best I can tell, but I'll update with actual code later today.Could the select be reading NULL values?

Inconsistent SQL results when using View with UNION-ALL and table function

Can any of you please execute the below scripts and check the output. In the table type variable, I am adding 4 distinct object ids, where as in the result, I get only the row pertaining to last id in the table type variable. Same row is returned 4 times (4= number of values in the table type).
This scenario is occurring in our product with a SQL with exactly same pattern. I could simulate the same issue with the sample script I have provided.
Database version: 11.2.0.3 Enterprise Edition, Single node
Thank you.
CREATE TABLE TEMP_T1 AS SELECT * FROM ALL_OBJECTS;
CREATE TABLE TEMP_T2 AS SELECT * FROM ALL_OBJECTS;
UPDATE TEMP_T2 SET OBJECT_ID = OBJECT_ID * 37;
CREATE UNIQUE INDEX TEMP_T1_U1 ON TEMP_T1(OBJECT_ID);
CREATE UNIQUE INDEX TEMP_T2_U1 ON TEMP_T2(OBJECT_ID);
CREATE OR REPLACE VIEW TEMP_T1T2_V AS
SELECT * FROM TEMP_T1 UNION ALL SELECT * FROM TEMP_T2;
CREATE OR REPLACE TYPE TEMP_OBJ_TYPE AS OBJECT (OBJ_ID NUMBER);
CREATE OR REPLACE TYPE TEMP_OBJ_TAB_TYPE IS TABLE OF TEMP_OBJ_TYPE;
SET SERVEROUTPUT ON;
DECLARE
TYPE TEMP_T1T2_V_ROW_TAB_TYPE IS TABLE OF TEMP_T1T2_V%ROWTYPE;
TEMP_T1T2_V_ROW_TAB TEMP_T1T2_V_ROW_TAB_TYPE;
TEMP_OBJ_TAB TEMP_OBJ_TAB_TYPE := TEMP_OBJ_TAB_TYPE();
PROCEDURE ADD_TO_TEMP_OBJ_TAB(OBJ_ID IN NUMBER) IS
BEGIN
TEMP_OBJ_TAB.EXTEND;
TEMP_OBJ_TAB(TEMP_OBJ_TAB.LAST) := TEMP_OBJ_TYPE(OBJ_ID);
END;
BEGIN
ADD_TO_TEMP_OBJ_TAB(100);
ADD_TO_TEMP_OBJ_TAB(116);
ADD_TO_TEMP_OBJ_TAB(279);
ADD_TO_TEMP_OBJ_TAB(364);
DBMS_OUTPUT.PUT_LINE('=====================');
FOR I IN TEMP_OBJ_TAB.FIRST..TEMP_OBJ_TAB.LAST
LOOP
DBMS_OUTPUT.PUT_LINE('OBJ_ID = '||TEMP_OBJ_TAB(I).OBJ_ID);
END LOOP;
DBMS_OUTPUT.PUT_LINE('---------------------');
SELECT * BULK COLLECT INTO TEMP_T1T2_V_ROW_TAB
FROM TEMP_T1T2_V VW
WHERE ((VW.OBJECT_ID) IN (SELECT OBJ_ID
FROM TABLE(CAST(TEMP_OBJ_TAB AS TEMP_OBJ_TAB_TYPE))));
FOR I IN TEMP_OBJ_TAB.FIRST..TEMP_OBJ_TAB.LAST
LOOP
DBMS_OUTPUT.PUT_LINE('OBJ_ID = '||TEMP_OBJ_TAB(I).OBJ_ID);
END LOOP;
DBMS_OUTPUT.PUT_LINE('---------------------');
IF TEMP_T1T2_V_ROW_TAB.COUNT > 0 THEN
FOR I IN TEMP_T1T2_V_ROW_TAB.FIRST..TEMP_T1T2_V_ROW_TAB.LAST
LOOP
DBMS_OUTPUT.PUT_LINE(TEMP_T1T2_V_ROW_TAB(I).OBJECT_ID||' : '||TEMP_T1T2_V_ROW_TAB(I).OBJECT_NAME);
END LOOP;
ELSE
DBMS_OUTPUT.PUT_LINE('NO ROWS RETURNED!');
END IF;
DBMS_OUTPUT.PUT_LINE('---------------------');
END;
/

I can reproduce it:
SQL*Plus: Release 11.2.0.3.0 Production on Tue Oct 30 14:05:39 2012
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Enter user-name: scott
Enter password:
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> select *
2    from v$version
3 /
BANNER
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
PL/SQL Release 11.2.0.3.0 - Production
CORE    11.2.0.3.0      Production
TNS for 64-bit Windows: Version 11.2.0.3.0 - Production
NLSRTL Version 11.2.0.3.0 - Production
SQL> CREATE TABLE TEMP_T1 AS SELECT * FROM ALL_OBJECTS;
Table created.
SQL>
SQL> CREATE TABLE TEMP_T2 AS SELECT * FROM ALL_OBJECTS;
Table created.
SQL>
SQL> UPDATE TEMP_T2 SET OBJECT_ID = OBJECT_ID * 37;
72883 rows updated.
SQL>
SQL> CREATE UNIQUE INDEX TEMP_T1_U1 ON TEMP_T1(OBJECT_ID);
Index created.
SQL>
SQL> CREATE UNIQUE INDEX TEMP_T2_U1 ON TEMP_T2(OBJECT_ID);
Index created.
SQL>
SQL> CREATE OR REPLACE VIEW TEMP_T1T2_V AS
2 SELECT * FROM TEMP_T1 UNION ALL SELECT * FROM TEMP_T2;
View created.
SQL>
SQL> CREATE OR REPLACE TYPE TEMP_OBJ_TYPE AS OBJECT (OBJ_ID NUMBER)
2 /
Type created.
SQL> CREATE OR REPLACE TYPE TEMP_OBJ_TAB_TYPE IS TABLE OF TEMP_OBJ_TYPE
2 /
Type created.
SQL> SET SERVEROUTPUT ON;
SQL>
SQL> DECLARE
2 TYPE TEMP_T1T2_V_ROW_TAB_TYPE IS TABLE OF TEMP_T1T2_V%ROWTYPE;
3 TEMP_T1T2_V_ROW_TAB TEMP_T1T2_V_ROW_TAB_TYPE;
4 TEMP_OBJ_TAB TEMP_OBJ_TAB_TYPE := TEMP_OBJ_TAB_TYPE();
5 PROCEDURE ADD_TO_TEMP_OBJ_TAB(OBJ_ID IN NUMBER) IS
6 BEGIN
7 TEMP_OBJ_TAB.EXTEND;
8 TEMP_OBJ_TAB(TEMP_OBJ_TAB.LAST) := TEMP_OBJ_TYPE(OBJ_ID);
9 END;
10 BEGIN
11 ADD_TO_TEMP_OBJ_TAB(100);
12 ADD_TO_TEMP_OBJ_TAB(116);
13 ADD_TO_TEMP_OBJ_TAB(279);
14 ADD_TO_TEMP_OBJ_TAB(364);
15 DBMS_OUTPUT.PUT_LINE('=====================');
16 FOR I IN TEMP_OBJ_TAB.FIRST..TEMP_OBJ_TAB.LAST
17 LOOP
18 DBMS_OUTPUT.PUT_LINE('OBJ_ID = '||TEMP_OBJ_TAB(I).OBJ_ID);
19 END LOOP;
20 DBMS_OUTPUT.PUT_LINE('---------------------');
21 SELECT * BULK COLLECT INTO TEMP_T1T2_V_ROW_TAB
22 FROM TEMP_T1T2_V VW
23 WHERE ((VW.OBJECT_ID) IN (SELECT OBJ_ID
24 FROM TABLE(CAST(TEMP_OBJ_TAB AS TEMP_OBJ_TAB_TYPE))));
25 FOR I IN TEMP_OBJ_TAB.FIRST..TEMP_OBJ_TAB.LAST
26 LOOP
27 DBMS_OUTPUT.PUT_LINE('OBJ_ID = '||TEMP_OBJ_TAB(I).OBJ_ID);
28 END LOOP;
29 DBMS_OUTPUT.PUT_LINE('---------------------');
30 IF TEMP_T1T2_V_ROW_TAB.COUNT > 0 THEN
31 FOR I IN TEMP_T1T2_V_ROW_TAB.FIRST..TEMP_T1T2_V_ROW_TAB.LAST
32 LOOP
33 DBMS_OUTPUT.PUT_LINE(TEMP_T1T2_V_ROW_TAB(I).OBJECT_ID||' : '||TEMP_T1T2_V_ROW_TAB(I).OBJECT_NAME);
34 END LOOP;
35 ELSE
36 DBMS_OUTPUT.PUT_LINE('NO ROWS RETURNED!');
37 END IF;
38 DBMS_OUTPUT.PUT_LINE('---------------------');
39 END;
40 /
=====================
OBJ_ID = 100
OBJ_ID = 116
OBJ_ID = 279
OBJ_ID = 364
OBJ_ID = 100
OBJ_ID = 116
OBJ_ID = 279
OBJ_ID = 364
364 : I_AUDIT
364 : I_AUDIT
364 : I_AUDIT
364 : I_AUDIT
PL/SQL procedure successfully completed.
SQL> column object_name format a30
SQL> select object_id,
2          object_name
3    from dba_objects
4    where object_id in (100,116,279,364)
5 /
OBJECT_ID OBJECT_NAME
       100 ORA$BASE
       116 DUAL
       279 MAP_OBJECT
       364 I_AUDIT
SQL> Works fine in:
=====================
OBJ_ID = 100
OBJ_ID = 116
OBJ_ID = 279
OBJ_ID = 364
OBJ_ID = 100
OBJ_ID = 116
OBJ_ID = 279
OBJ_ID = 364
100 : ORA$BASE
116 : DUAL
364 : SYSTEM_PRIVILEGE_MAP
279 : MAP_OBJECT
PL/SQL procedure successfully completed.
SQL> select object_id,
2          object_name
3    from dba_objects
4    where object_id in (100,116,279,364)
5 /
OBJECT_ID OBJECT_NAME
      100 ORA$BASE
      116 DUAL
      364 SYSTEM_PRIVILEGE_MAP
      279 MAP_OBJECT
SQL> select *
2    from v$version
3 /
BANNER
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
PL/SQL Release 11.2.0.1.0 - Production
CORE    11.2.0.1.0      Production
TNS for 32-bit Windows: Version 11.2.0.1.0 - Production
NLSRTL Version 11.2.0.1.0 - Production
SQL>SY.
Edited by: Solomon Yakobson on Oct 30, 2012 2:14 PM

Inconsistency of results using adaptive RFC

I'm calling a function from a R/3 System using Adaptive RFC and i'm having different results from my webdynpro application that the ones that i'm having in the R/3.
If someone could tell me why this happen I will appreciate.
Thanks.

Hi Frank,
Iin another opportunity I had tried to do the same procedure you are trying and not getting hit. I ended up using the parameter "sap-wd-client = WmlClient" in the url of the application ... What makes this return in xml format and can be accessed like a Web Service. It really is not a proper use for a Web Dynpro application, but with some customization finally meet demand.
Regards,
Angelo

Multiselect begins with gives inconsistent fetch results

Hi All,
We have a Multiselect item in our Dashboard Tab Page. We are making the values coming from database as UPPER to avoid case sensitive search.
The problem now comes when the user keys in different partial values of same word, the results are different.
To illustrate,
When we search by OPI and option is "begins with", it fetches all the comapny names starting with OPI incluidng OPITZ SOLUTIONS which we are looking for.
But when we give OPITZ or OPIT, it does not fetch any results.
When I give OPITZ i.e. with space, again the results are fetched.
Is there any explanation for this behaviour?

Thanks to both of you for your inputs.
-> I checked the SQL generated after applying the filters - it is same for all columns. Moreover this is an issue that I see on the using the "begins with" option to restrict the number of available choices - so at that level I am not sure how the corresponding SQL can be tracked.
-> Also, there is no data level security implemented for any column/table in the repository.
I am still working to resolve this and would get back if there is any luck. Please do let me know if you have additional inputs on this issue.
Thanks,
Piyush

Inconsistent Speedtest Results

I recently noticed slow speeds so I tried two speedtests right after eachother. The first was on speedtest.net and had this result: http://www.speedtest.net/my-result/4464458407 The second was on speedtest.comcast.net and had this result: http://results.speedtest.comcast.net/result/944128404.png Why the huge difference? My internet speeds on all websites I've checked are consistent with the first, slower test.

This may now be fixed for you. If you check my thread "How do I report slow download speeds from out-of-area servers?" you'll see that it was spontaneously resolved around midnight mountain time. The problem seems to have been in Denver Comcast's network connection to the outside world. The Comcast network in Colorado, New Mexico and Arizona seems to be a common "local" network, and connecting from your home to that network always showed a good speed. That's why http://speedtest.comcast.com gave a good result: because it was local. However, if the data you were trying to download needed to come from outside those three states, it balked. That happened when either you used http://speedtest.comcast.com and pointed it to any server outside those three states (instead of just using the local default), or you used http://speedtest.net instead. I can't tell you whether it was deliberately fixed or whether it just happened because some machine got a scheduled reset at midnight. But it's OK now. Till the next time.

On2flix inconsistent results

Using On2Flix standard (current power mac version)
to compress video for web. I haven't attempted to send it to my web
designer for upload yet, I'm just at the stage of testing the
quality, and playing on my hard drive.
I'm getting very inconsistent play results when I encode the
same video with exactly the same encode settings ( a 7 minute video
exported from final cut pro).
With one of the test flv encodes, a window with the video
came up with the name indicating it was a temporary swf, and jerky
video played until I accidently got it to open in a different type
of window - then it played beautifully. Sometimes when the encode
is completed, an flv window (instead of tmp swf) opens and plays
the video (also jerky).
Just once I stumbled on a way to get the same encode to play
smoothly. I noticed that once the initial window appeared with the
encoded video, with that window active,I could choose to create an
Swf Player. When I clicked on the resulting Swf Player icon, it
automatically opened within my LiveType application, and a
different type of player window automatically opened with my video
in it, and the video played smoothly & looked good.
But the next day when I clicked on the same Swf Player icon,
it opened in LiveType, but with no video.
Starting from scratch, I encoded a new flv file from the same
final cut exported movie, went through the same steps, but can't
get it to play smoothly or get it to play through an Swf Player. I
created the Swf Player the same way as yesterday, it opens using
LiveType, but it's a black screen - can't get my video to come up
in this player.
I can't find any instructions other than the suggestions for
encoding settings. I can't figure out what to do after the encode
to get it to play smoothly. There's no problem with the video -
it's the same one that encoded and play beautifully the previous
day.

I believe I have solved this problem myself and thought others might benefit from what I found. It turns out to be what I believe as a glitch in iTunes. iTunes creates a cache of all the photos that you synch with your iPad, iPhone etc. Apparently it does not update that cache when you change the photo. At least not the Geotagging data. The file modify date was changing but that wasn't enough to cause iTunes to update the cache of the photos. I deleted the cache of all the photos and re-synched and presto now all my photos where showing up at the correct location in the iPad "places" view.
I might add that I called Apple tech support and was routed to a higher tier support person and was very disappointed with his response. He basically told me that the "place" view in the iPad and iPhone was designed to be only used with an Apple computer and Apple software and was surprised the places view was working at all with pictures synched with a Windows based machine. He also said he was unable to help me since he couldn't provide support for non-Apple products. Although I understand this to a point I think he was too quick to make this decision. The solution after all was a simple one and one I think he should have known. I would think this cache problem would happen whether I was using Apple products as well. I view this as a bug in iTunes. Apple needs to compare the modified date of the file and update the cache if it has changed.

Incorrect Search results number

Hi!
I'm currently working at search center and recently I've noticed that the number of search results in "About xx results" can vary a a lot.
I've found the similar question here: http://community.office365.com/en-us/f/154/t/204676.aspx - the given answer seemed good untill I tried to check the logic and to calculate results count in my test environment.
So, I have 45 total results. One of this results has duplicate. The results are shown by 10 per page. The duplicated results is shown at the first page. If I click on the next pages, I see the following (Im sorry for this clip2net logo, this is not an advertising:)
about 41
about 43
about 44
44 results total
I can't get, why it shows 41 and even 43 on the first 2 pages, while there is only 1 duplicate that might be hidden...
Please help me to understand this logic.
Any help or info would be greatly appreciated.

Hi Martynenko,
I understand that the results count is incorrect in SharePoint Search Results web part.
It is by design that the number on search result web part is a very rough number related to the mechanism within search engine.
It is not accurate because the accurate count of the
search result is not the main target for
search engine.
If we need the accurate number of some specific type of files, we can use the
SharePoint search APIs to get the
search result, and this is same as the result from web part.
http://spbreed.wordpress.com/2013/09/14/sharepoint-2013-solution-to-inconsistent-search-results-count/
Or you can set the query to include the duplicates.
Best regards.
Thanks
Victoria Xia
TechNet Community Support

Different Files Returned when using the Drop Down list on the Search Results Page

Hi
I have a result set of 22 documents when I select Date (Newest) from the drop down on the search results page. The third document down is called "LL".
If I now select Date (Oldest) I have a result Set of 22 documents. However, when I move to the second page. The number of documents has reduced to 20 documents and my document "LL" which I would have expected to be the third from bottom document
is not there.
Am I doing something wrong here ? Search is OOTB. I have added some refiner columns.
Regards
Nigel
Nigel Price NJPEnterprises

Hi Nigel,
It is by design. The "About x results" is presented when the total number of results is uncertain, and that is when collapsing (i.e. duplicate detection in this case) is enabled and the result set is partially processed. By default, a result page
shows 10 results at the time. Therefore, for result sets with less than or equal to 10 results you will always get an accurate number of results and hence “About” is omitted. For more than 10 results you will get the “About x results” on the first page until
you get to the last page of results and only then we know the exact number of results and hence can omit the “About”.
Note that when you page out in the result set you will notice that the X in the “About X results” can vary quite a lot. That is because the total number of results is estimated based on the collapsing done so far. This is a common way of doing it by other
search engines as well.
Here is a simlar post for your reference:
http://spbreed.wordpress.com/2013/09/14/sharepoint-2013-solution-to-inconsistent-search-results-count/
I hope this helps.
Thanks,
Wendy
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Wendy Li
TechNet Community Support

Inconsistent selection behavior when deleting files in Cover Flow

I love browsing through my pictures folder using Cover Flow. However, I've noticed that deleting a file by pressing Cmd-Delete produces inconsistent selection results. Sometimes Finder will select the next file down the list, and sometimes it will select no file at all. However, the Cover Flow portion of the window will always show the next file.
It is misleading when Cover Flow shows the next file, but the file selection pane shows no file selected. I often hit the down-arrow (or right-arrow) key, expecting to skip to the next file, but the first file in the folder gets selected, Cover Flow re-winds its view, and I have to re-find my last position.
There is also no way to select the current file by clicking on the Cover Flow preview currently showing. I have to click some other file and re-browse to the current file in order to sync up the two panes.
Is this a bug? Does Apple know about it?

As mentioned, cover flow does not change the basic Finder operation. Return allows editing the name and Cmd-O or Cmd-downarrow opens the item. It also functions similar to the list view, when you open a folder, the subfolders are added to the cover flow; they do not replace the cover flow icons.

Incorrect Search Results

We have a PDF file of 1 page created through SAP (ERP Application). The PDF has a name "AD" which is displayed and printed. When we search the PDF using search option for name "ZZ", it gives the search results by selecting name "AD". Also, the PDF is sent to Blackberry device of "AD" with details of "ZZ".
This is similar to mirror image but I have no idea as to how to view this.
Regards,
Amar

Hi Martynenko,
I understand that the results count is incorrect in SharePoint Search Results web part.
It is by design that the number on search result web part is a very rough number related to the mechanism within search engine.
It is not accurate because the accurate count of the
search result is not the main target for
search engine.
If we need the accurate number of some specific type of files, we can use the
SharePoint search APIs to get the
search result, and this is same as the result from web part.
http://spbreed.wordpress.com/2013/09/14/sharepoint-2013-solution-to-inconsistent-search-results-count/
Or you can set the query to include the duplicates.
Best regards.
Thanks
Victoria Xia
TechNet Community Support

Inconsistent ESB results

Similar Messages

Maybe you are looking for