ALL_TABLES returns different results

Hello

Thinking of this query:

SELECT table_name
From all_tables
Owner WHERE = "SCHEMA_B";

The diagram that I work in is "SCHEMA_A".

When I run this statement in SQL Developer, Toad,... it will return me 4 rows.

Now I do the following (this is according to a procedure in a package):

PROCEDURE X
IS
CURSOR c_tab IS
SELECT table_name
From all_tables
Owner WHERE = "SCHEMA_B";
BEGIN
FOR r_tab IN c_tab LOOP
insert into test (test) values (r_tab.tab_nm);
commit;
END LOOP;
END X;

Now, I check the table 'TEST' and I have zero records in it. I wanted to see 4 records...

Someone at - it a solution?

Hello

Subsidies on the tables are probably a role.
It is why he "sees" no line in all_tables.
You can check this by doing a 'SET ROLE NONE' in sqlplus before making your selection.

Rgds,
Guido

Published by: Guido on October 28, 2008 12:46
Tried to be more specific...

Tags: Database

Similar Questions

SQL query return different result 11 GR 1 material and GR 11, 2

Problem: SQL returns different results in 11 GR 1 material and GR 11, 2 games.
Example script:
create the table tab_main
(
SOS number (2) not null,
contract number (2) null
)
/
create the table tab_sub
(
number (2) of contract non-null,.
SOS number (2) null
)
/
insert into tab_main values (1, 10);
insert into tab_main values (2, 20);
insert into tab_main values (3, null);
insert into tab_main values (4, null);
insert into tab_sub values (1, 10);
insert into tab_sub (20, 2) values;
commit;
The SQL code:
SELECT *.
OF tab_main.
tab_sub
WHERE tab_main.sos = tab_sub.sos (+) AND
tab_main. Contract = tab_sub.contract (+) and
tab_main. Contract not in (select 1 of the double);
The above query gives more results
-by 11.2.0.4
1 10 10 1
2 20 20 2
-in 11.1.0.7
1 10 10 1
2 20 20 2
4
3

Please tell us what could be the reason for the behaviour of offset lines thie.

Thank you
Piesset

I think it is probably a bug in 11.1.0.7 (and possibly other versions), I get the same results as your 11.2.0.4 9.2.0.7, 10.2.0.3 and 11.2.0.3, and this is the result, I expect.

Your not in the paragraph is equivalent to:

SELECT *.

OF tab_main, tab_sub

WHERE tab_main.sos = tab_sub.sos (+) AND

tab_main. Contract = tab_sub.contract (+) and

tab_main. Contract <> 1;

Since you have null values in tab_main.contract they are lost by the predicate since null = value is never true (or false).

John

query returns different results depends on the length of the day

Hello!

I have a query:

INSERT /*+ APPEND */ INTO pwa_process (
id,
id_session,
id_customer,
s2k_account,
service_seq_num,
msisdn,
id_tariff,
contract_end_date,
last_contract_date,
next_available_contract_date,
tariff_name,
description,
description_long,
imei_old,
activation_date,
id_customer_number,
arpu,
value0,
value1,
value2,
value3,
value4,
value5,
id_pricing_plan)
WITH msisdns AS (SELECT msisdn ms FROM customer_number cn
JOIN customer_s2kaccount cs ON cn.s2k_account = cs.s2k_account AND cs.id_customer = v_customerId)
SELECT
seq_pwa_process.NEXTVAL,
v_sessionId,
customer_s2kaccount.id_customer,
customer_s2kaccount.s2k_account,
customer_number.service_seq_num,
msisdn.msisdn,
tariff.id,
NVL(CASE WHEN date_contract_end IS NULL AND le_contract_end_date IS NOT NULL OR (date_contract_end < le_contract_end_date)
         THEN le_contract_end_date
         ELSE NVL(date_contract_end, ADD_MONTHS(customer_number.date_start, customer_number.ada_availability))
    END, TO_DATE('01.01.1970', 'DD.MM.YYYY')) contract_end_date,
CASE WHEN NOT customer_number.date_first_activation IS NULL AND customer_number.date_first_activation >      (CASE WHEN ada_priority = 1 THEN ada_date_pwa
        WHEN ada_priority <> 1 AND (date_pwa IS NULL AND exchange_date IS NOT NULL OR date_pwa < exchange_date) 
        THEN exchange_date 
        ELSE date_pwa 
  END) 
     THEN customer_number.date_first_activation
     ELSE   (CASE WHEN ada_priority = 1 THEN ada_date_pwa
        WHEN ada_priority <> 1 AND (date_pwa IS NULL AND exchange_date IS NOT NULL OR date_pwa < exchange_date) 
        THEN exchange_date 
        ELSE date_pwa 
  END) 
END last_contract_date,
ADD_MONTHS(CASE WHEN NOT customer_number.date_first_activation IS NULL AND customer_number.date_first_activation > NVL(  (CASE WHEN ada_priority = 1 THEN ada_date_pwa
        WHEN ada_priority <> 1 AND (date_pwa IS NULL AND exchange_date IS NOT NULL OR date_pwa < exchange_date) 
        THEN exchange_date 
        ELSE date_pwa 
  END) ,
                                                                                                                       NVL(customer_number.date_first_activation, NVL(customer_number.date_start, customer_number.date_effective)))
                THEN customer_number.date_first_activation
                ELSE NVL(  (CASE WHEN ada_priority = 1 THEN ada_date_pwa
        WHEN ada_priority <> 1 AND (date_pwa IS NULL AND exchange_date IS NOT NULL OR date_pwa < exchange_date) 
        THEN exchange_date 
        ELSE date_pwa 
  END) , NVL(customer_number.date_first_activation, NVL(customer_number.date_start, customer_number.date_effective)))
           END, customer_number.ada_availability - DECODE(NVL(customer_number.current_contract_type, 0), 2, DECODE(customer_number.reduced_contract_used, 0, NVL(customer_number.el_contract_calculated_reduc,0), 0), 0)) next_available_contract_date,
tariff.name_ada,
DECODE(msisdn_group.def_column, 0, msisdn.value0, 1, msisdn.value1, 2, msisdn.value2, 3, msisdn.value3, 4, msisdn.value4, 5, msisdn.value5, msisdn.value0),
msisdn.value0 || ';' || NVL(msisdn.value1, '') || ';' || NVL(msisdn.value2,'') || ';' || NVL(msisdn.value3,'') || ';' || NVL(msisdn.value4, '') || ';' || NVL(msisdn.value5, ''),
customer_number.imei,
NVL(customer_number.date_first_activation, NVL(customer_number.date_start, customer_number.date_effective)) date_start,
customer_number.id,
NVL(s2kaccount.arpu1,0),
msisdn.value0,
msisdn.value1,
msisdn.value2,
msisdn.value3,
msisdn.value4,
msisdn.value5,
customer_number.id_pricing_plan
FROM customer_s2kaccount
JOIN customer_number ON customer_number.s2k_account = customer_s2kaccount.s2k_account AND customer_number.service_state = 'AB'
JOIN msisdn ON msisdn.msisdn = customer_number.msisdn
JOIN TABLE(CAST(v_tmp_table AS ADA.NUMBER_TABLE)) ids ON ids.column_value = msisdn.id
JOIN msisdn_group ON msisdn_group.id = msisdn.id_msisdn_group
JOIN pricing_plan ON pricing_plan.id = customer_number.id_pricing_plan AND pricing_plan.is_for_pwa = 1
JOIN tariff ON tariff.name = pricing_plan.id
JOIN s2kaccount ON s2kaccount.s2k_account = customer_number.s2k_account
LEFT
JOIN (SELECT msisdn, exchange_date, ADD_MONTHS(exchange_date, MAX(prolongation)) le_contract_end_date
FROM loyalty_exchange a, msisdns
WHERE a.msisdn = msisdns.ms AND exchange_date >= ALL (SELECT exchange_date FROM loyalty_exchange b WHERE b.msisdn = a.msisdn)
GROUP BY msisdn, exchange_date) le ON le.msisdn = customer_number.msisdn
WHERE customer_s2kaccount.id_customer = v_customerId;

This query returns different results in the morning (09:00) and afternoon (16:00) on the same database for the same input data (I have prepared a script to test).
Oracle 9.2.0.6 @solaris
I checked the query plans, but they look the same in the morning and the afternoon. I don't know where to look for a problem/bug.
Please help me with suggestions. is in bug with join ansi? or a left outer join?

Published by: batonoff on February 16, 2009 16:56

Published by: batonoff on February 16, 2009 16:58

Published by: batonoff on February 16, 2009 17:00

I recommend you post your declaration in the {} code tags (without the spaces) so that we can actually read.

You are absolutely positive that nothing has changed on the data between when you run in the morning and in the afternoon?

OBIEE logical column has same SQL but returns different results

I have a SQL query with a case statement that returns the correct results by operating in Oracle SQL Developer. I've created several logical columns in OBIEE, one for each case in the original query. However, the results returned by each logical column OBIEE are radically different from the original SQL query results, even if the SQL code is virtually identical.
For example, a column logical OBIEE that returns incorrect results contains the following SQL code:
SUM (CASE when
("Registration - College". "" Effective colleges F. ("" Postal code "like '% a %') or
("Registration - College". "" Effective colleges F. ("" Postal code "like '%B %') or
("Registration - College". "" Effective colleges F. ("" Postal code "like '%c %') or
("Registration - College". "" Effective colleges F. ("" Postal code "like"% %") or
("Registration - College". "" Effective colleges F. ("" Postal code "like '%G %') or
("Registration - College". "" Effective colleges F. ("" Postal code "like"hour %") or
("Registration - College". "" Effective colleges F. ("" Postal code "like"%%J") or
("Registration - College". "" Effective colleges F. ("' Postal code ' like '%R %') or
("Registration - College". "" Effective colleges F. ("" Postal code "like '%s %') or
("Registration - College". "" Effective colleges F. ("" Postal code "like '%T %') or
("Registration - College". "" Effective colleges F. ("" Postal code "like"% %") or
("Registration - College". "" Effective colleges F. ("" Postal code "like '%x %') or
("Registration - College". "" Effective colleges F. ("' Postal code ' like '%Y %')
THEN 0 OTHERWISE 1 END)
The case statement in the original SQL query, which returns the correct results, is as follows:
CASE
WHEN (postal_zip_code_permanent like "%%K") or (postal_zip_code_permanent like '% %') or (postal_zip_code_permanent like '%m %') or (postal_zip_code_permanent like '%n %') or (postal_zip_code_permanent like "%p %") THEN "Ontario".
WHEN (postal_zip_code_permanent like '% a %') or (postal_zip_code_permanent like '%B %') or (postal_zip_code_permanent like '%c %') or (postal_zip_code_permanent like '% %') or (postal_zip_code_permanent like '%G %') or (postal_zip_code_permanent like "%hour") or (postal_zip_code_permanent like "%%J") or (postal_zip_code_permanent like "%%R") or (postal_zip_code_permanent like '%s %') or (postal_zip_code_permanent like '%t %') or (postal_zip_code_permanent like '% %') or (postal_zip_ code_permanent like '%x %') or (postal_zip_code_permanent like "%%Y") THEN "Canada, other than Ontario.
WHEN (substr(postal_zip_code_permanent,1,1) IN ('1 ', '2', '3', '4', '5', '6' ', 7',' 8 ', ' 9',' 0') or (postal_zip_code_permanent like '%d %') or (postal_zip_code_permanent like '%f %') or (postal_zip_code_permanent like ' % I %') or (postal_zip_code_permanent like "% O") or (postal_zip_code_permanent like "%%Q") or (postal_zip_code_permanent like "%%U") or (postal_zip_code_permanent like ' % W ') or (postal_zip_code_permanent like "%%Z")) THEN 'other')
WHEN (postal_zip_code_permanent like '% + %') or (postal_zip_code_permanent like '%. %') or (postal_zip_code_permanent like ' %? %') or (postal_zip_code_permanent like '% %') or postal_zip_code_permanent IN ('+ ','.', '?)) (',',') And THEN "Invalid."
WHEN postal_zip_code_permanent is null THEN 'Blank '.
Of OTHER postal_zip_code_permanent
END

Now I see what the problem was. In the original SQL query, each condition is exclusive, for each record will only be categorized in one of the scenarios WHEN. But in OBIEE, each logical column is autonomous, so some records were classified into more than logical column, even if each logical column was supposed to be exclusive.

Smart collection returns different results to the library filter?

This is such a stupid thing, and I barely noticed. I have smart collections simply gather all the images with a particular star of note, very very simple! I have a 1 star, a Star 2 and one for the 3 stars and more. So far so good, use these for centuries-, but I noticed that if I go to Catalog/All photos and place a filter of the same library (this is the filter at the top of the library grid view) I get different results. Actually if I place a filter attribute that says '= 2 stars' images only I can watch the tape that works at the bottom of the screen (sorry I have no idea what it's called) and he said that "all photos / 1056 1647 photos» If I can clear this filter and scroll down to my smart collection that applies the filter even to the entire catalog (and I triple checked this, no difference at all, I don't have lower or higher than the here is the self same "=" only!) and it says "1066"! Thus, the smart collection search 10 images more than other, identical filters working on the entire catalog - I am confused? Anyone had this problem, I missed something? If it wasn't for the number of images concerned I'd them and try to find the additional files by hand!
Popular indices, and LR3 passing on Mac.
Tim.

You can check if the images are stacked differently (and thus not counted) in both points of view.

dbms_sqlhash and online md5 calculator return different results
Does anyone know how dbms_sqlhash.gethash () works?
I get the same result for string 123456.
Md5 (http://md5-hash-online.waraxe.us/) online calculator returns e10adc3949ba59abbe56e057f20f883e.
DBMS_SQLHASH. GETHASH() returns 7E8FEB2276322ECDDD4423B649DFD4D9.
```
--the second parameter value 2 means MD5 hash.
select DBMS_SQLHASH.GETHASH('select 123456 from dual',2) from dual;
```
Hello
>
I get the same result for string 123456.
Md5 (http://md5-hash-online.waraxe.us/) online calculator returns e10adc3949ba59abbe56e057f20f883e.
DBMS_SQLHASH. GETHASH() returns 7E8FEB2276322ECDDD4423B649DFD4D9.
```
--the second parameter value 2 means MD5 hash.
select DBMS_SQLHASH.GETHASH('select 123456 from dual',2) from dual;
```
DBMS_SQLHASH. GETHASH returns the hash of the SQL statement in the first parameter Select 123456 of double, not 123456

To get the MD5 hash of the 123456 you should use DBMS_OBFUSCATION_TOOLKIT or DBMS_CRYPTO packages. The latest is preferable and more recent.

Kind regards

Select on ALL_TABLES gives different results (SQL vs PROCEDURE)
Hello

I am connected with the user and I ran this SQL:
```
SELECT COUNT(*)
FROM ALL_TABLES
WHERE Table_Name = 'SRMD'
AND Owner = 'DMI';
```
The count() returns the value 1.

Then, I created a procedure called TestAllTables with exactly the same statement:
```
CREATE OR REPLACE PROCEDURE A.TestAllTables(p_Table IN VARCHAR2, p_Schema IN VARCHAR2) IS
  l_Nb  NUMBER;
 
BEGIN
  SELECT COUNT(*) 
  INTO l_Nb
  FROM ALL_TABLES
  WHERE Table_Name = p_Table
    AND Owner = p_Schema;
    
  IF l_Nb = 0 THEN 
    dbms_output.put_line('KO !');
  ELSE
    dbms_output.put_line('OK...');
  END IF;
END;
```
.. .and I ran, it is always connected to A:
```
BEGIN
    TestAllTables('SRMD','DMI');
END;
/
```
.. .and it gives me this incomprehensible error: KO!

Please can someone explain to me why?

Thks.
Your access to the table of dmi.smrd was granted by a role.

If you want the query "ALL_TABLES" rights of a stored procedure DEFINER and see this table, you must have administrative privileges on the table given directly to you, rather than having acquired them via a role. The DBA or the owner of the table need run
```
GRANT SELECT ON dmi.smrd TO <>
```
Once they do this, the query will return a line even when you ran ' set no role ' and your procedure will be able to see the table.

Justin

Calculations to return different results depending on the responsibility
Hello

We have a report that uses a PL/SQL function in a calculation.

When a single responsibility runs the report, the calculation returns figures empty or incorrect.

When another executes it, it works fine.

When the function is created, are there grants that must be given to ensure that all responsibilities can use this?

All the responsibilities have access to the data in the application.

The service is owned by APPS and it was registered in the EUL.

Also, there seems to be a difference in if this is executed from SSO launch Viewer or office.

Kind regards

Rachael
Hello

Your basic problem is that you have

EXCEPTION
while others then
return sqlcode;

at the end of your code. This means that if an error occurs when you run the function it will be completed successfully, but with some bad days.

With this exception handling it is difficult to know what you encounter the error, but it could be a problem of access to the tables or type conversion problem.

Rod West

A few keys return a different result example I press o and he returned .o

My son has been on the computer (asus k53s) laptop. I don't know what he did, but now some of the traits keyboard return a different result, it feels almost like a kind of shortcut function. I restarted snd got the same result

Here are the problems I found.

o and. They all return two .o

q returns a q and a tab

m and refer my

v and t both return a vt

x starts the Help window

I can't use my laptop properly right now that one of the letters is used in the passwd file, I use the keyboard to the mouse on screen.

I need help asap thank you

You can try the system restore to go back before the problem?

How to repair the operating system and how to restore the configuration of the operating system to an earlier point in time in Windows Vista (or 7)
http://support.Microsoft.com/kb/936212/#appliesTo

I see that the OSK works for you, so perhaps the problem is a defective keyboard? Have you tried to turn the laptop upside down and gently pat down to try to remove some of the bread crumbs between the keys (Lol).

You can plug in another USB keyboard into the laptop and test with that?

Why can I get two different results from the same coefficients?

I get two different results of the evaluation of the polynomial function.

For the first, I get the coefficients of a polynomial function to adapt. I feed the coefficients of the function made the function Eval Poly and get the correct 12.8582 result when I evaluate 49940.

For the second, I create constant array of values that have been returned by the polynomial Fit function (I typed in). However, I get an incorrect result of - 120.7913 when I feed the constant table the function Eval Poly when I evauate 49940.

How this can happen when I use the same values in table?

A picture of what I explained is attached.

Hi Altran,

are you sure about using the 'same '?

You compare them? Do you have (at least) set them to 17 digits display properties?

Please attach a VI instead of an image...

RowNumber = 1 return different data

We are preparing the upgrade to oracle 11g 2 to 12 c.
We have some test environment to test extracts which is in c 11g 2 and 12.
Even extract script, the same data, another server with a different version of the database a to 11 g 2, the other is 12 c.
Most of the snippets returned exactly the same data.
But for a small number of extracts in .dat file returns a little bit different. We checked into it, it's because the script extracts using a function in the database and it uses rownumber = 1, same order. But another server returns a different record. For example, they return guardian meeting certain criteria, in this case, relatives are Ok, but we wonder why he returned differently. Is there a setting or is there a default sorting of columns in oracle if not specifically using order by?
Thank you

Hello

Oracle does not guarantee that queries would return the same results if used as below.

Select * from sample_table

where rownum = 1;

You may need to use like below to get the same results (Top N queries)

SELECT column_name, rownum AS rnum

FROM (SELECT column_name

OF sample_table

ORDER BY column_name)

WHERE rownum<=>

Kind regards

Wilson

Different results of exactly the same query

Hello

I wrote a function to calculate the days between 2 dates. If I am running in SQL Developer or directly on the oracle server, I get the results I expected. However, if I run on a client by using ODBC, or PHP connection via the OCI8 extension, I get an incorrect result.

The function takes 2 parameters: 1st and 2nd date and should output the number of non-working days (weekends and holidays) between 2 dates. The coding is not very pretty, but it does not work very well as I said since the client SQL Developer.

Here is the code:

create or replace
FUNCTION NON_WORKDAYS(fromdate IN DATE, todate IN DATE)
--Function to calculate non working days between 2 given dates (Weekends & Bank Holidays)
--Update: Added in a calendar for bank holidays. Bank holidays are listed to the end of 2013

RETURN NUMBER IS
BANK_HOLS NUMBER;
    ret NUMBER;
BEGIN
    SELECT count(mydate) INTO ret FROM 
 (SELECT     TO_DATE (fromdate, 'dd-mon-yyyy hh24:mi:ss') + LEVEL - 1 mydate
                FROM DUAL
           CONNECT BY LEVEL < =
                            TO_DATE (todate, 'dd-mon-yyyy hh24:mi:ss')
                          - TO_DATE (fromdate, 'dd-mon-yyyy hh24:mi:ss')
                          + 1)
     WHERE TO_CHAR (mydate, 'DY') IN ('SAT', 'SUN');
     
     
     select count(mydate) into BANK_HOLS from (
     SELECT     TO_DATE (fromdate, 'dd-mon-yyyy hh24:mi:ss') + LEVEL - 1 mydate
                FROM DUAL
           CONNECT BY LEVEL < =
                            TO_DATE (todate, 'dd-mon-yyyy hh24:mi:ss')
                          - TO_DATE (fromdate, 'dd-mon-yyyy hh24:mi:ss')
                          + 1
     )
     WHERE TO_CHAR (mydate, 'DD-MM-YYYY') IN 
     ('03-01-2011', 
     '22-04-2011',
     '25-04-2011',
     '29-04-2011',
     '02-05-2011',
     '30-05-2011',
     '29-08-2011',
     '26-12-2011',
     '27-12-2011',
     '02-01-2012',
     '06-04-2012',
     '09-04-2012',
     '07-05-2012',
     '04-06-2012',
     '05-06-2012',
     '12-07-2012',
     '27-08-2012',
     '25-12-2012',
     '26-12-2012',
     '01-01-2013',
     '29-03-2013',
     '01-04-2013',
     '06-05-2013',
     '27-05-2013',
     '12-07-2013',
     '26-08-2013',
     '25-12-2013',
     '26-12-2013'
     );
     ret:= ret + BANK_HOLS;
     
    RETURN ret;
end;

The problem is only with certain dates. For example, if I use the date '17-SEP-2012' for the two input parameters, I'm waiting for a result draw. In the SQL Developer client, I get the expected result. However, using ODBC or PHP OCI8 (which I believe is using a direct connection to TNS in the DB), the result returned is '1', which is incorrect ("17-SEP-2012" has been a MONDAY ""). If I use the current date (20-SEP-2012), I get the expected (zero) result in both the SQL Developer client and ODBC/PHP client.

I also tried to use variants of SYSDATE in place and place the date string, to see if I get different results (i.e. today is 20-SEP-2012, so I used SYSDATE-3 to 17-SEP-2012).

To be clear, I call the function in a select statement: select (sysdate-3, sysdate-3) non_workdays of the double; or select non_workdays (TO_DATE('17-SEP-2012'), TO_DATE('17-SEP-2012')) of double;

I have spent hours and hours of troubleshooting this, and it makes me crazy!

I also checked the view V$ SQLAREA the Oracle DB to see what is actually passed to the ODBC client database engine. I was expecting the statement became corrupted somehow, that's why I get strange results, but this was not the case. The statement in the column SQL_FULLTEXT of V$ SQLAREA, showed exactly the statement I performed on the ODBC Client. I tried with the oracle instantclient and full client (10g).

Can someone help save my sanity please? I am eternally grateful!

Sorry for the massive post!

Published by: user12199535 on 20-Sep-2012 12:20

Your code is a mess. You convert DATE to DATE, e.g. TO_DATE (fromdate, 'dd-mon-yyyy hh24:mi:ss'). TO_DATE function first parameter is a string, while fromdate is the date. That's why Oracle implicitly converts fromdate to the string of default date format that is client dependent and therefore can produce different results on different customers boxes. In addition, your code is dependent on NLS. If the customer has other date language settings, for example German, Sun and SAT are false. And there is no need to separately calculate the weekends and holidays:

create or replace
  FUNCTION NON_WORKDAYS(fromdate IN DATE, todate IN DATE)
  --Function to calculate non working days between 2 given dates (Weekends & Bank Holidays)
  --Update: Added in a calendar for bank holidays. Bank holidays are listed to the end of 2013
    RETURN NUMBER
    IS
        BANK_HOLS NUMBER;
        ret NUMBER;
    BEGIN
        SELECT  count(mydate)
          INTO  ret
          FROM  (
                 SELECT  trunc(fromdate) + LEVEL - 1 mydate
                   FROM  DUAL
                   CONNECT BY LEVEL < = trunc(todate) - trunc(fromdate) + 1
                )
          WHERE TO_CHAR(mydate,'DY','NLS_DATE_LANGUAGE = ENGLISH') IN ('SAT','SUN')
             OR mydate IN (
                           DATE '2011-01-03',
                           DATE '2011-04-22',
                           DATE '2011-04-25',
                           DATE '2011-04-29',
                           DATE '2011-05-02',
                           DATE '2011-05-30',
                           DATE '2011-08-29',
                           DATE '2011-12-26',
                           DATE '2011-12-27',
                           DATE '2012-01-02',
                           DATE '2012-04-06',
                           DATE '2012-04-09',
                           DATE '2012-05-07',
                           DATE '2012-06-04',
                           DATE '2012-06-05',
                           DATE '2012-07-12',
                           DATE '2012-08-27',
                           DATE '2012-12-25',
                           DATE '2012-12-26',
                           DATE '2013-01-01',
                           DATE '2013-03-29',
                           DATE '2013-04-01',
                           DATE '2013-05-06',
                           DATE '2013-05-27',
                           DATE '2013-07-12',
                           DATE '2013-08-26',
                           DATE '2013-12-25',
                           DATE '2013-12-26'
                          );
        RETURN ret;
end;
/

SY.
P.S. I think that I converted your vacation to literals correctly, but still double check date.

Display different results in a hardcoded LOV
version 4.0.2.00.06

Hello

I have a list of selection multiple selection that I now need to display different results depending on the value in a hidden field, cust_type. Display and return values are hard coded values that they don't have a table.

If the cust_type = 'R' I need the results are:
0
1-50
50-100
100-500
500-1 000
more than 1000

If the cust_type = 'B', I need the results are:
0
1-1 000
1 000-5 000
5 000-10 000
10 000-25 000
25 000 +.

Could someone help me with how to do this?

Thank you
Joe
check the link againg, I changed the code.

* Mark correct if the code has helped you! *

Why do I get different results of these
I use the HR diagram and study the nested instructions. When I run these two SQL statistics I get a different result. Someone knows why?

Select avg (salary), country_id of
(select department_id, location_id, salary, country_id of)
employees join natural services locations of natural join)
Country_id group;

Select avg (salary), country_id (select country_id, treatment)
employees join departments using (department_id)
Join the locations using (location_id))
Country_id group;

Thanks in advance.
Natural join joins the tables on columns with the same name. If you look at HR. EMPLOYEES and human resources. Tables of DEPARTMENTS, they share two columns department_id and MANAGER_ID while your second query attached just the department_id. If you add MANAGER_ID to the second query that both return the same results:
```
SQL> select  avg(salary),
  2          country_id
  3    from  (
  4           select  salary,
  5                   department_id,
  6                   location_id,
  7                   country_id
  8             from  hr.employees natural join hr.departments natural join hr.locations
  9          )
 10  group by country_id;

AVG(SALARY) CO
----------- --
       5640 US
       6000 CA
       8500 UK

SQL> select  avg(salary),
  2          country_id
  3    from  (
  4           select  salary,
  5                   country_id
  6             from  hr.employees join hr.departments using(department_id,manager_id)
  7                   join hr.locations using (location_id)
  8          )
  9  group by country_id;

AVG(SALARY) CO
----------- --
       5640 US
       6000 CA
       8500 UK

SQL> 
```
SY.

Consistency of return null results.
Hello
We are facing difficulties to conduct subtle understanding of the coherence. We see the results of coherence as null when they are run repeatedly customer. In the first round, we see results & when I run my key objects changing client program then I see the result with the value null to get some. But when I recycle or restart cache loader and run the same customer with the same data, so we are able to see the results.

Please guide us to understand behavior, we strive for consistency for the first time.

CacheLoader.java:
import java.util.HashMap;

import com.tangosol.net.cache.AbstractCacheLoader;
import com.tangosol.util.WrapperException;

SerializableAttribute public class CacheLoader extends AbstractCacheLoader implements com.tangosol.net.cache.CacheLoader {}
int i;
@Override
public Object Load (Object argKey) {}
HashMap dataMap = null;
Key = argKey (Key);
try {}
System.out.println("Key::"+Key.ToString());)
dataMap (HashMap) = key.retrieve ();
System.out.println (++ i + ": result of retreive::"+dataMap.size()); ")
}
{} catch (Exception wrapEx)
wrapEx.printStackTrace ();
throw new WrapperException (wrapEx.getMessage () + wrapEx.getCause ());
}
return dataMap;
}
}

Client program:
MPort com.tangosol.net.CacheFactory;
import com.tangosol.net.NamedCache;

public class CoherenceClient {}

/**
@param args
*/
Public Shared Sub main (String [] args) {}
TODO self-generating method stub
new CoherenceClient () .invokeStorageNode ();
}

private void invokeStorageNode() {}
String cacheName = ResultKey.class.getSimpleName ();
ResultKey resultKey = new ResultKey ("Suhas", "Louise", 30);
NamedCache cache = CacheFactory.getCache (cacheName);
try {}
for (int i = 1; i < 100; i ++) {}
resultKey = new ResultKey ("Suhas", "Xavier" + i, 30 + i);
System.out.println (i + ": - > cache Result::"+cache.get(resultKey)); ")
}
}
catch (Exception ex) {}
ex.printStackTrace ();
}
}
}

the cache config xml loader:
<? XML version = "1.0" encoding = "UTF-8"? >
<! SYSTEM cache-config DOCTYPE "cache - config.dtd" >

<>cache-config
< cache-system-mapping >
<>cache-mapping
< name-cache > ResultKey < / cache-name >
< scheme name > distributed plan < / system-name >
< init-params >
< init-param >
< param-name > cache-store-class-name < / param-name >
CacheLoader < param-value > < / param-value >
< / init-param >
< / init-params >
< / cache-mapping >

< / cache-system-mapping >

<>- cached patterns
< distributed plan >
< scheme name > distributed plan < / system-name >
< service name > DistributedCache < / service-name >
< support-map-plan >
< reading-writing-support-map-plan >

< internal-cache-system >
< local plan >
< system-Ref > LocalSizeLimited < / plan-ref >
< / local plan >
< / internal-cache-system >
< dumps-plan >
schema < class >
< class name > {cache-store-class-name} < / class name >
< / class-system >
< / dumps-plan >
< rollback-dumps-chess > true < / restoration-dumps-chess >
< / reading-writing-support-map-plan >
< / support-map-plan >
< number of partition > 5557 < / partition-County >
> number of backup < 1 < / backup-County >
< number > 10 threads < / thread count >
< autostart > true < / autostart >
< / distributed plan >

< local plan >
< scheme name > LocalSizeLimited < / system-name >
< high-units > 500000000 < / high units >
< bass-units > 10000 < / bass-units >
< Unit Calculator > BINARY < / Unit-Calculator >
< / local plan >
< / cache-plans >

< / cache-config >

client config xml:
<? XML version = "1.0"? >
<! SYSTEM cache-config DOCTYPE "cache - config.dtd" >
<>cache-config
< cache-system-mapping >
<! - caches with any name will be created as a default replicated. - >
<>cache-mapping
< name-cache > ResultKey < / cache-name >
< scheme name > distributed_cache < / system-name >
< / cache-mapping >
< / cache-system-mapping >

<>- cached patterns

< distributed plan >
< scheme name > distributed_cache < / system-name >
< service name > DistributedCache < / service-name >
< support-map-plan >
< rollback-dumps-chess > true < / restoration-dumps-chess >
schema < class >
< system-Ref > by default-support-map < / plan-ref >
< / class-system >
< / support-map-plan >
< / distributed plan >
<!--
By default, backup of schema definition of card used by all
Caches that don't require any deportation policy
->
schema < class >
< scheme name > - by default-support-map < / system-name >
> class name < com.tangosol.util.SafeHashMap < / class name >
< / class-system >
< / cache-plans >
< / cache-config >

How to reproduce:
(1) start Cache loader by using com.tangosol.net.DefaultCacheServer as a class main-server-Xms64m-Xmx64m - Dtangosol.coherence.wka = *ipaddressipaddress*-Dtangosol.coherence.cacheconfig=\conf\server-cache-config.xml-Dtangosol.coherence.extend.address=* *.

(2) run the client with the following information as VM arguments:
-Server-Xms64m-Xmx64m - Dtangosol.coherence.wka = *ipaddressipaddress*-Dtangosol.coherence.cacheconfig=conf\client-cache-config.xml-Dtangosol.coherence.extend.address=* *.

(3) run the client program as it is for the first time. We see the result as below:
1: - > cache result: {NAME = Suhas, AGE = 31, LAST NAME is Madap1}
2: - > cache result: {NAME = Suhas, AGE = 32, LAST NAME is Madap2}
3: - > cache result: {NAME = Suhas, AGE = 33, LAST NAME is Madap3}
4: - > cache result: {NAME = Suhas, AGE = 34, LAST NAME is Madap4}
5: - > cache result: {NAME = Suhas, AGE = 35, LAST NAME is Madap5}
6: - > cache result: {NAME = Suhas, AGE = 36, LAST NAME is Madap6}
7: - > cache result: {NAME = Suhas, AGE = 37, LAST NAME is Madap7}
8: - > cache result: {NAME = Suhas, AGE = 38, LAST NAME is Madap8}
9: - > cache result: {NAME = Suhas, AGE = 39, LAST NAME is Madap9}
10: - > cache result: {NAME = Suhas, AGE = 40, LAST NAME is Madap10}
11: - > cache result: {NAME = Suhas, AGE = 41, LAST NAME is Madap11}
12: - > cache result: {NAME = Suhas, AGE = 42, LAST NAME is Madap12}
13: - > cache result: {NAME = Suhas, AGE = 43, LAST NAME is Madap13}
14: - > cache result: {NAME = Suhas, AGE = 44, LAST NAME is Madap14}
15: - > cache result: {NAME = Suhas, AGE = 45, LAST NAME is Madap15}
16: - > cache result: {NAME = Suhas, AGE = 46, LAST NAME is Madap16}
17: - > cache result: {NAME = Suhas, AGE = 47, LAST NAME is Madap17}
18: - > cache result: {NAME = Suhas, AGE = 48, LAST NAME is Madap18}
19: - > cache result: {NAME = Suhas, AGE = 49, LAST NAME is Madap19}
20: - > cache result: {NAME = Suhas, AGE = 50, LAST NAME is Madap20}
21: - > cache result: {NAME = Suhas, AGE = 51, LAST NAME is Madap21}
22: - > cache result: {NAME = Suhas, AGE = 52, LAST NAME is Madap22}
23: - > cache result: {NAME = Suhas, AGE = 53, LAST NAME is Madap23}
24: - > cache result: {NAME = Suhas, AGE = 54, LAST NAME is Madap24}
25: - > cache result: {NAME = Suhas, AGE = 55, LAST NAME is Madap25}
26: - > cache result: {NAME = Suhas, AGE = 56, LAST NAME is Madap26}
27: - > cache result: {NAME = Suhas, AGE = 57, LAST NAME is Madap27}
28: - > cache result: {NAME = Suhas, AGE = 58, LAST NAME is Madap28}
29: - > cache result: {NAME = Suhas, AGE = 59, LAST NAME is Madap29}
30: - > cache result: {NAME = Suhas, AGE = 60, LAST NAME is Madap30}
31: - > cache result: {NAME = Suhas, AGE = 61, LAST NAME is Madap31}
32: - > cache result: {NAME = Suhas, AGE = 62, LAST NAME is Madap32}
33: - > cache result: {NAME = Suhas, AGE = 63, LAST NAME is Madap33}
34: - > cache result: {NAME = Suhas, AGE = 64, LAST NAME is Madap34}
35: - > cache result: {NAME = Suhas, AGE = 65, LAST NAME is Madap35}
36: - > cache result: {NAME = Suhas, AGE = 66, LAST NAME is Madap36}
37: - > cache result: {NAME = Suhas, AGE = 67, LAST NAME is Madap37}
38: - > cache result: {NAME = Suhas, AGE = 68, LAST NAME is Madap38}
39: - > cache result: {NAME = Suhas, AGE = 69, LAST NAME is Madap39}
40: - > cache result: {NAME = Suhas, AGE = 70, LAST NAME is Madap40}
41: - > cache result: {NAME = Suhas, AGE = 71, LAST NAME is Madap41}
42: - > cache result: {NAME = Suhas, AGE = 72, LAST NAME is Madap42}
43: - > cache result: {NAME = Suhas, AGE = 73, LAST NAME is Madap43}
44: - > cache result: {NAME = Suhas, AGE = 74, LAST NAME is Madap44}
45: - > cache result: {NAME = Suhas, AGE = 75, LAST NAME is Madap45}
46: - > cache result: {NAME = Suhas, AGE = 76, LAST NAME is Madap46}
47: - > cache result: {NAME = Suhas, AGE = 77, LAST NAME is Madap47}
48: - > cache result: {NAME = Suhas, AGE = 78, LAST NAME is Madap48}
49: - > cache result: {NAME = Suhas, AGE = 79, LAST NAME is Madap49}
50: - > cache result: {NAME = Suhas, AGE = 80, LAST NAME is Madap50}
51: - > cache result: {NAME = Suhas, AGE = 81, LAST NAME is Madap51}
52: - > cache result: {NAME = Suhas, AGE = 82, LAST NAME is Madap52}
53: - > cache result: {NAME = Suhas, AGE = 83, LAST NAME is Madap53}
54: - > cache result: {NAME = Suhas, AGE = 84, LAST NAME is Madap54}
55: - > cache result: {NAME = Suhas, AGE = 85, LAST NAME is Madap55}
56: - > cache result: {NAME = Suhas, AGE = 86, LAST NAME is Madap56}
57: - > cache result: {NAME = Suhas, AGE = 87, LAST NAME is Madap57}
58: - > cache result: {NAME = Suhas, AGE = 88, LAST NAME is Madap58}
59: - > cache result: {NAME = Suhas, AGE = 89, LAST NAME is Madap59}
60: - > cache result: {NAME = Suhas, AGE = 90, LAST NAME is Madap60}
61: - > cache result: {NAME = Suhas, AGE = 91, LAST NAME is Madap61}
62: - > cache result: {NAME = Suhas, AGE = 92, LAST NAME is Madap62}
63: - > cache result: {NAME = Suhas, AGE = 93, LAST NAME is Madap63}
64: - > cache result: {NAME = Suhas, AGE = 94, LAST NAME is Madap64}
65: - > cache result: {NAME = Suhas, AGE = 95, LAST NAME is Madap65}
66: - > cache result: {NAME = Suhas, AGE = 96, LAST NAME is Madap66}
67: - > cache result: {NAME = Suhas, AGE = 97, LAST NAME is Madap67}
68: - > cache result: {NAME = Suhas, AGE = 98, LAST NAME is Madap68}
69: - > cache result: {NAME = Suhas, AGE = 99, LAST NAME is Madap69}
70: - > cache result: {NAME = Suhas, AGE = 100, LAST NAME is Madap70}
71: - > cache result: {NAME = Suhas, AGE = 101, LAST NAME is Madap71}
72: - > cache result: {NAME = Suhas, AGE = 102, LAST NAME is Madap72}
73: - > cache result: {NAME = Suhas, AGE = 103, LAST NAME is Madap73}
74: - > cache result: {NAME = Suhas, AGE = 104, LAST NAME is Madap74}
75: - > cache result: {NAME = Suhas, AGE = 105, LAST NAME is Madap75}
76: - > cache result: {NAME = Suhas, AGE = 106, LAST NAME is Madap76}
77: - > cache result: {NAME = Suhas, AGE = 107, LAST NAME is Madap77}
78: - > cache result: {NAME = Suhas, AGE = 108, LAST NAME is Madap78}
79: - > cache result: {NAME = Suhas, AGE = 109, LAST NAME is Madap79}
80: - > cache result: {NAME = Suhas, AGE = 110, LAST NAME is Madap80}
81: - > cache result: {NAME = Suhas, AGE = 111, LAST NAME is Madap81}
82: - > cache result: {NAME = Suhas, AGE = 112, LAST NAME is Madap82}
83: - > cache result: {NAME = Suhas, AGE = 113, LAST NAME is Madap83}
84: - > cache result: {NAME = Suhas, AGE = 114, LAST NAME is Madap84}
85: - > cache result: {NAME = Suhas, AGE = 115, LAST NAME is Madap85}
86: - > cache result: {NAME = Suhas, AGE = 116, LAST NAME is Madap86}
87: - > cache result: {NAME = Suhas, AGE = 117, LAST NAME is Madap87}
88: - > cache result: {NAME = Suhas, AGE = 118, LAST NAME is Madap88}
89: - > cache result: {NAME = Suhas, AGE = 119, LAST NAME is Madap89}
90: - > cache result: {NAME = Suhas, AGE = 120, LAST NAME is Madap90}
91: - > cache result: {NAME = Suhas, AGE = 121, LAST NAME is Madap91}
92: - > cache result: {NAME = Suhas, AGE = 122, LAST NAME is Madap92}
93: - > cache result: {NAME = Suhas, AGE = 123, LAST NAME is Madap93}
94: - > cache result: {NAME = Suhas, AGE = 124, LAST NAME is Madap94}
95: - > cache result: {NAME = Suhas, AGE = 125, LAST NAME is Madap95}
96: - > cache result: {NAME = Suhas, AGE = 126, LAST NAME is Madap96}
97: - > cache result: {NAME = Suhas, AGE = 127, LAST NAME is Madap97}
98: - > cache result: {NAME = Suhas, AGE = 128, LAST NAME is Madap98}
99: - > cache result: {NAME = Suhas, AGE = 129, LAST NAME is Madap99}

(4) run the client program changing once more result key object to:
for (int i = 1; i < 100; i ++) {}
resultKey = new ResultKey ("Suhas", "Louise", 30 + i);
System.out.println (i + ": - > cache Result::"+cache.get(resultKey)); ")
}
We see the result with the value null for some keys:
1: - > cache result: {NAME = Suhas, AGE = 31, LAST NAME is Makitantu}
2010-08-09 15:34:20.514/1.906 Oracle coherence GE 3.5.3/465 < D4 > (thread = DistributedCache, Member = 2): ask Member 1 2778 primary partitions
2010-08-09 15:34:21.546/2.938 Oracle coherence GE 3.5.3/465 < D5 > (thread = TcpRingListener, 2 = member): TcpRing: connection to members 1 using TcpSocket {State = STATE_OPEN, Socket=Socket[addr=/10.136.109.206,port=1556,localport=8089]}
2: - > Hide Result::null
2010-08-09 15:34:22.061/3.453 Oracle coherence GE 3.5.3/465 < D5 > (thread = DistributedCache, Member = 2): postponement of the distribution because of 2778 pending updated configuration
3: - > cache result: {NAME = Suhas, AGE = 33, LAST NAME is Makitantu}
4: - > Hide Result::null
5: - > cache result: {NAME = Suhas, AGE = 35, LAST NAME is Makitantu}
6: - > Hide Result::null
7: - > Hide Result::null
8: - > Hide Result::null
9: - > Hide Result::null
10: - > cache result: {NAME = Suhas, AGE = 40, LAST NAME is Makitantu}
11: - > cache result: {NAME = Suhas, AGE = 41, LAST NAME is Makitantu}
12: - > Hide Result::null
13: - > cache result: {NAME = Suhas, AGE = 43, LAST NAME is Makitantu}
14: - > Hide Result::null
15: - > cache result: {NAME = Suhas, AGE = 45, LAST NAME is Makitantu}
16: - > cache result: {NAME = Suhas, AGE = 46, LAST NAME is Makitantu}
17: - > Hide Result::null
18: - > Hide Result::null
19: - > cache result: {NAME = Suhas, AGE = 49, LAST NAME is Makitantu}
20: - > Hide Result::null
21: - > cache result: {NAME = Suhas, AGE = 51, LAST NAME is Makitantu}
22: - > cache result: {NAME = Suhas, AGE = 52, LAST NAME is Makitantu}
23: - > cache result: {NAME = Suhas, AGE = 53, LAST NAME is Makitantu}
24: - > Hide Result::null
25: - > Hide Result::null
26: - > cache result: {NAME = Suhas, AGE = 56, LAST NAME is Makitantu}
27: - > Hide Result::null
28: - > Hide Result::null
29: - > cache result: {NAME = Suhas, AGE = 59, LAST NAME is Makitantu}
30: - > Hide Result::null
31: - > cache result: {NAME = Suhas, AGE = 61, LAST NAME is Makitantu}
32: - > Hide Result::null
33: - > cache result: {NAME = Suhas, AGE = 63, LAST NAME is Makitantu}
34: - > Hide Result::null
35: - > Hide Result::null
36: - > cache result: {NAME = Suhas, AGE = 66, LAST NAME is Makitantu}
37: - > cache result: {NAME = Suhas, AGE = 67, LAST NAME is Makitantu}
38: - > cache result: {NAME = Suhas, AGE = 68, LAST NAME is Makitantu}
39: - > cache result: {NAME = Suhas, AGE = 69, LAST NAME is Makitantu}
40: - > Hide Result::null
41: - > Hide Result::null
42: - > Hide Result::null
43: - > Hide Result::null
44: - > Hide Result::null
45: - > cache result: {NAME = Suhas, AGE = 75, LAST NAME is Makitantu}
46: - > cache result: {NAME = Suhas, AGE = 76, LAST NAME is Makitantu}
47: - > cache result: {NAME = Suhas, AGE = 77, LAST NAME is Makitantu}
48: - > Hide Result::null
49: - > cache result: {NAME = Suhas, AGE = 79, LAST NAME is Makitantu}
50: - > cache result: {NAME = Suhas, AGE = 80, LAST NAME is Makitantu}
51: - > cache result: {NAME = Suhas, AGE = 81, LAST NAME is Makitantu}
52: - > cache result: {NAME = Suhas, AGE = 82, LAST NAME is Makitantu}
53: - > Hide Result::null
54: - > cache result: {NAME = Suhas, AGE = 84, LAST NAME is Makitantu}
55: - > Hide Result::null
56: - > cache result: {NAME = Suhas, AGE = 86, LAST NAME is Makitantu}
57: - > Hide Result::null
58: - > Hide Result::null
59: - > cache result: {NAME = Suhas, AGE = 89, LAST NAME is Makitantu}
60: - > Hide Result::null
61: - > cache result: {NAME = Suhas, AGE = 91, LAST NAME is Makitantu}
62: - > Hide Result::null
63: - > cache result: {NAME = Suhas, AGE = 93, LAST NAME is Makitantu}
64: - > cache result: {NAME = Suhas, AGE = 94, LAST NAME is Makitantu}
65: - > cache result: {NAME = Suhas, AGE = 95, LAST NAME is Makitantu}
66: - > Hide Result::null
67: - > cache result: {NAME = Suhas, AGE = 97, LAST NAME is Makitantu}
68: - > Hide Result::null
69: - > cache result: {NAME = Suhas, AGE = 99, LAST NAME is Makitantu}
70: - > Hide Result::null
71: - > cache result: {NAME = Suhas, AGE = 101, LAST NAME is Makitantu}
72: - > cache result: {NAME = Suhas, AGE = 102, LAST NAME is Makitantu}
73: - > cache result: {NAME = Suhas, AGE = 103, LAST NAME is Makitantu}
74: - > Hide Result::null
75: - > Hide Result::null
76: - > cache result: {NAME = Suhas, AGE = 106, LAST NAME is Makitantu}
77: - > cache result: {NAME = Suhas, AGE = 107, LAST NAME is Makitantu}
78: - > Hide Result::null
79: - > cache result: {NAME = Suhas, AGE = 109, LAST NAME is Makitantu}
80: - > cache result: {NAME = Suhas, AGE = 110, LAST NAME is Makitantu}
81: - > cache result: {NAME = Suhas, AGE = 111, LAST NAME is Makitantu}
82: - > cache result: {NAME = Suhas, AGE = 112, LAST NAME is Makitantu}
83: - > cache result: {NAME = Suhas, AGE = 113, LAST NAME is Makitantu}
84: - > cache result: {NAME = Suhas, AGE = 114, LAST NAME is Makitantu}
85: - > cache result: {NAME = Suhas, AGE = 115, LAST NAME is Makitantu}
86: - > Hide Result::null
87: - > cache result: {NAME = Suhas, AGE = 117, LAST NAME is Makitantu}
88: - > Hide Result::null
89: - > cache result: {NAME = Suhas, AGE = 119, NAME is Xavier}
90: - > cache result: {NAME = Suhas, AGE = 120, LAST NAME is Makitantu}
91: - > Hide Result::null
92: - > Hide Result::null
93: - > Hide Result::null
94: - > cache result: {NAME = Suhas, AGE = 124, LAST NAME is Makitantu}
95: - > Hide Result::null
96: - > cache result: {NAME = Suhas, AGE = 126, LAST NAME is Makitantu}
97: - > Hide Result::null
98: - > cache result: {NAME = Suhas, AGE = 128, LAST NAME is Makitantu}
99: - > cache result: {NAME = Suhas, AGE = 129, LAST NAME is Makitantu}

Whenever we see null as a response, we observed that the call from the client can't same cacheloader::load() method.

An additional point is, when we recycle or restart cache loader and run the client program in step 4 of the data. It returns the result.

Published by: Suhas Xavier on August 9, 2010 16:53
Hi Suhas,

The problem is in your configuration of cache files. You have different client and server cache configuration files, define all two distributed-scheme for ResultKey cache. In the client configuration file, SafeHashMap is used as card distributed system support while in the server configuration file, cache store is used. Since this is a distributed cache, storage/process of participation of the cache is divided between two nodes of coherence. The entries stored or processed by the cache on the client service would return zero, while the inputs processed by the cache on the Server service would return that store cache load returns. That's why you see some of some of the entries have a value and others are null.

Try to use the same cache for the client and the server configuration file. If you don't want the client to a storage node, set - Dtangosol.coherence.distributed.localstorage = false in your java command. What exactly do you want to the client and the server to do? Maybe close cache is something you are looking for?

-Luk

ALL_TABLES returns different results

Similar Questions

Maybe you are looking for