To_date gives inconsistent results?

I have a stored function that returns T or F depending on whether the past is valid for a past format string date. The relevant part of this function is

v_Result: = 't';
BEGIN
SELECT to_date (in_date_string, in_format_string) IN double v_good_date;
IF v_good_date IS NULL THEN
v_Result: = 'F';
END IF;
EXCEPTION WHEN OTHERS THEN
v_Result: = 'F';
END;
RETURN (v_Result);

Now, I have a table that contains the dates as varchar2 strings in the format YYYYMMDD. The dates may be incomplete, and I'm only interested in complete dates. If I use the function

Select a.stop_dt
address a
where is_valid_date (a.stop_dt, 'yyyymmdd') = 't'

It returns 69 lines.

But now I am only interested in the dates that are later than today ' hui. I add the line

and to_date (a.stop_dt, 'yyyymmdd') > trunc (sysdate)

Suddenly, I get an error ORA-01843. When I list the 69 records, none has an invalid month.

Does anyone have an idea what might be going on here? I guess my is_valid_date function is something unexpected, but I can't imagine what it might be. It seems that if somehow to_date in one case returns non null even if the date is not valid and in the other case will raise an error.
--
Helge moulding

Hi, Helge,

Welcome to the forum!

If you run a query like this:

select  a.stop_dt
from    address          a
where       is_valid_date (a.stop_dt,'yyyymmdd')     = 'T'
and         to_date (a.stop_dt,'yyyymmdd')           > trunc (sysdate)

The optimizer decides which of the conditions to assess the first; Apparently, he thinks that the new condition, using TO_DATE, will restrict the faster search, so he dioes than a first.

The best solution could be to o re is_valid_date - write or write a similar function, which, instead of return 't' or 'F', it returns the DATE when the string can be converted to a DATE, and NULL otherwise. The function will be equally effective; You must call TO_DATE anyway. In this case, it will be actually more efficient, since you only have to call time, inside the function TO_DATE, once again not in the query.
At the heart of the function can then be:

BEGIN
     SELECT  v_Result := to_date ( in_date_string, in_format_string);

EXCEPTION WHEN OTHERS THEN
      v_Result := NULL ;
END ;

RETURN( v_Result ) ;

Note that there is no need to use the table of double. In PL/SQL, you can call functions directly.

Without changing the function, you can make sure the conversion is made first, like this:

select  a.stop_dt
from    address          a
where       to_date ( CASE
                WHEN  is_valid_date (a.stop_dt,'yyyymmdd')     = 'T'
                THEN  a.stop_dt
                ELSE  NULL    -- This is the default; you don't have to say it explicitly
            END
          , 'yyyymmdd'
          )          > trunc (sysdate)

or you can compare strings rather than DATEs:

select  a.stop_dt
from    address          a
where       is_valid_date (a.stop_dt,'yyyymmdd')     = 'T'
and         a.stop_dt,'yyyymmdd'                > to_char (sysdate, 'yyyymmdd')

The results of the 2nd condition will be unreliable if a.stop_dt is incorrect. It's OK; the 1st condition will exclude any way these lines.

Published by: Frank Kulash, August 27, 2010 18:37
Additional function code

Tags: Database

Similar Questions

sdo_union gives inconsistent results
Hello

Oracle Database 10g Enterprise Edition Release 10.2.0.4.0

We use sdo_union to convert the geometries of the line. Some geometries inserted in our database have sdo_gtype 2006, but can be easily converted in 2002 using a query like:
```
update lines_tb l 
set    shape = case when sdo_geom.sdo_union(l.shape, l.shape, 0.001).sdo_gtype = 2002 
                    then sdo_geom.sdo_union(l.shape, l.shape, 0.001) 
                    else l.shape 
               end 
where  l.shape.sdo_gtype = 2006;
```
We note however is you run the query again, he continues to find results! It makes no sense at all...

Modesty only that I can do, is that sdo_union is not consistent with its findings!

Can someone confirm this behavior?

Thank you

ROP
Hi Rop,

Then it must be a problem already fixed, because I am using Oracle Database 11 g Enterprise Edition Release 11.2.0.1.0 - Production, and whenever I run this 2002 returns.

Time to migrate to 11g :)

It seems therefore ;-)

See you soon,.
Stefan

Inconsistent results Spotlight

I've known inconsistent results of Spotlight with OS X servers for a year or so now. I worked on that with Yosemite and El Capitan.

What is happening is that Spotlight does not see inside some files scattered in various actions. The problem is consistent if the search of a customer attached or on the server itself. It has many, many of these records.

I deleted it. Index files V100-focus on volumes several times with the following process:

sudo mdutil - a-i off

sudo rm - rfv. Spotlight-V100 (I run on each volume)

sudo mdutil - a-i on

sudo mdutil - Ea

However after letting the Spotlight re-indexing it does not fix things.

I think next reset the ACL on the volume where the data is stored. I first want to make sure that what I'm doing, that's enough:

sudo chmod-r/path/to/volume n

Then set the permissions for the shares as it should.

Suggestions or comments?

You happen to have the system during a rebuild Spotlight log tail? If Yes, have you seen errors, files or records which failed to index, or all mdworker default processes? The system log can provide valuable data as to why Spotlight does not complete.

Then, if you are going to strip the ACL, you will also remove user _spotlight. This system is essential for the proper functioning of the projector. Make sure that when you go to spread your new ACLs that account _Spotlight is listed as an ACE inherited. All files and folders on your part must contain this account from the ACL table service.

And finally, don't forget to watch the POSIX permissions. If you have restrictive permissions POSIX, you may have implemented a condition in which the mdworker process simply can not cross your data structure. Search for files located at 700 or files located at 600. Perhaps considered using the propagation process to restore all the POSIX permissions standard umask.

I hope this helps.

Reid

Apple Consultants Network

Author - "El Capitan Server - Foundation Services.

Author - "El Capitan Server - Collaboration & control»

Author - "El Capitan Server - Advanced Services '.

: IBooks exclusively available in Apple store

Satellite L10 and keyboard:-shift key gives wrong results

Using the SHIFT key with most of other than a-z keys gives bad result.
I tried to re - install a driver via Control Panel / keyboard with the Toshiba XP Home CD inserted but not better driver is found.
Control Panel / regional and language setting is English UK

Hello, Alan

It will be nice if you can give us more information. What specific keyboard of the country you have? What you want to do exactly? Give us a few examples please.

LEFTOUTER join querry which gives bad result

Hello
I have tables like below.when I perform a left outer join issue IDs and startdate he gives invalid results.when I write in request
It does not correct result because there is no data for 16 jan. It should give no results. But it shows all records. How do I solve this problem
SQL:
Select a.id, a.date, b.val, a.tot, b.net, b.cre
FROM table1 a
join table2 b left
"on a.id = b.id and a.date = b. and a.date ='02-Feb-2014."
In the tables below contains no data for the month of February but still im getting the incorrect data. He must not returnany files right?
Table1:
ID Date Val tot
1 January 1, 13 1 9
2 2 January 13 3 8
3 3 January 13 4 7
4 January 4, 13 5 6
5 5 January 13 6 5
Table2:
ID Date NET CRE
1 January 1, 13 1 9
2 13 January 13 3 8
3 3 January 13 4 7
4 January 4, 13 5 6
5 5 January 13 6 5

"It should not returnany files right?

Wrong, there is no where clause so it should return all the records in a padded with NULL values for b.

ASCIISTR function that gives different results
Hi Experts,

I use the function ASCIISTR and it gives different results in SQLPLUS and TOAD

SQLPLUS
```
SQL> SELECT ASCIISTR('é') UC FROM DUAL
  2  ;

UC
-----
\201A

SQL> SELECT ASCIISTR('ú') UC FROM DUAL;

UC
-----
\00A3
```
TOAD
```
SELECT ASCIISTR('ú') UC FROM DUAL

\00FA

SELECT ASCIISTR('é') UC FROM DUAL

\00E9
```
I know experts here will be reluctant to respond to questions about the TOAD, but I wanted to understand if I'm missing something. I checked the NLS_SESSION_PARAMETERS in SQLPLUS and TOAD, and they are the same. :-(does not understand this behavior

Version of database Oracle Database * 10g Enterprise Edition Release 10.2.0.3.0 - 64 bit Production *.

Thanks in advance!
The default code for the command line page is 437, identical to TOAD, you want to get the code page 1252
```
SQL> host chcp
Active code page: 437

SQL> SELECT ASCIISTR('é') UC FROM DUAL;

UC
_____
\201A

SQL> host chcp 1252
Active code page: 1252

SQL> SELECT ASCIISTR('é') UC FROM DUAL;

UC
_____
\00E9

SQL>
```

simulation of the same in different versions of multisim circuit design give different results

version of Multisim 10.0, PATTERN16T GIVES RESULTS on... DISPLAYSA2A20000A2A20000AAAA0000AAAA0000...

MULTISIM 10.1 VERISION, PATTERN16T RESULTS ON

POSTER A3A30000A3A30000A3A30000...

EACH PROGRAM MULTISIM, USE THE SAME CIRCUIT FOR ANALYSIS.

MULTISIM 10.0 VERSION GIVES A CORRECT RESULT.

YOU MAY NEED TO CHECK THE NEW VERSION OF THIS PROBLEM

WITH THE VERSION OF MULTISIM 10.0.

RICHARD RUHL

Hello

Could you please attach your additional troubleshooting circuits? What is your operating system?

Kind regards

Inconsistent results with Julian dates using OpenQuery

We have a MS SQL Server using Oracle via a linked server using the OleDb driver.
When I run the following query to MS SQL Server:
Select * from OPENQUERY (GMENU, 'select to_char (to_date(''01-JAN-2015''), 'J') of the double')
I get: 1721443
When I run this query in Oracle: select to_char (to_date('01-JAN-2015'), 'J') of the double
I get: 2457024
Can someone explain how I can get consistent results? Specifically, I'm trying to run queries that use dates in the where clause, and it seems that the only way to do that is using Julien dates. I had it once before, but now it is glitchy because the results are not consistent.

results change when you actually provide a format mask?

Select to_char (to_date('01-JAN-2015','DD-MON-YYYY'), 'J') of the double

Definition of the XMP data with inconsistent results

$. pipelineTools.MetadataController.prototype.setMediaStartTimecode = {function (timecode)}
var path = "Column.Intrinsic.MediaStart".
Test
Val = this.xmpMetadata.setStructField)
XMPConst.NS_DM,
"startTimecode,"
XMPConst.NS_DM,
'timeValue ',.
'00:00:00:00 '.
)
this.xmpMetaChanges.push (path)
// " http://ns.Adobe.com/XMP/1.0/DynamicMedia/ "
var val = this.xmpMetadata.setStructField)
XMPConst.NS_DM,
"altTimecode,"
XMPConst.NS_DM,
'timeValue ',.
timecode
)
this.xmpMetaChanges.push (path)
}
He always pays in ESTK correct timecode, but it is not always set the same value.
As you can see in ESTK:
However, the clips at random are preparing to 00:00:00:00
There is a logic to the way in which metadata are drawn? I tried to make sure that there is a field startTimecode first (because sometimes this field does not exist in some cases completely and must be created), but it doesn't matter. Alttimecode is the one we want to use because it is the lag that we use for the potential for additional images being made at some point.
Above is a clip that was supposed to have MediaStart the 00:00:04:05 value and this is a clip that was correctly configured value:
The two using the same code, the same calculation, the same session.
Seems to be incompatible and dumping the XMP files results in this:
grw020 (Successful):
< xmpDM:startTimecode rdf:parseType = "Resource" >
< xmpDM:timeFormat > 24Timecode < / xmpDM:timeFormat >
< xmpDM:timeValue > 00:00:00:00 < / xmpDM:timeValue >
< / xmpDM:startTimecode >
< xmpDM:altTimecode rdf:parseType = "Resource" >
< xmpDM:timeValue > 00:00:04:05 < / xmpDM:timeValue >
< xmpDM:timeFormat > 24Timecode < / xmpDM:timeFormat >
< / xmpDM:altTimecode >
soc020 (qualifications):
< xmpDM:altTimecode rdf:parseType = "Resource" >
< xmpDM:timeValue > 00:00:04:05 < / xmpDM:timeValue >
< / xmpDM:altTimecode >
< xmpDM:startTimecode rdf:parseType = "Resource" >
< xmpDM:timeValue > 00:00:00:00 < / xmpDM:timeValue >
< / xmpDM:startTimecode >

As you can see, grw020 somehow magically Gets the timeFormat string and using the same code in the same session, soc020 not get the timeFormat value.
Now I'm curious to know how the successful clip becomes the value lost, and secondly - why is it fill properly? There is a sequence to 23.976 and it is filling with 24Timecode - when it should be filling with 23976Timecode as I have seen in other clips.

Overall, this seems to be a very inconsistent data set.
Thank you.

I don't think that it is possible to set the framerate on a clip using XMP metadata project and first noticing the change. I am successfully able to change the startTimecode, altTimecode and other values, but if I put the XMP value or project metadata, there is no change in framerate.

It seems that for a period indeterminate media Timebase will replace all attempts to set the framerate, even if the correct and desired information are in the XMP output and the metadata project out after importation.

I test this by setting the Timebase of media for an indefinite period to 59,97 fps and import a clip with no metadata on it.

Once this process is complete, waiting for the event loop complete the import and then try to set the framerate to 23.976 both XMP and metadata to the project. It does not change. However, all other values will not change.

view inline values, which gives bad result...

I saw a123 table with data below...

GRANT AMOUNT DRCR
1 1234 1000 D
2 1234 5000 C
3 12345 2000 C
4 12345 7000 D

Now I want below o/p of the table of the a123

GRANT BALANCE
1234 -4000
12345 -5000
To do this, I wrote below the query but its appropriate result not give...
Select grant, credit-debit balance of)
Select grant, sum (debit) Debit, sum (credit) credit of)
Select grant,
Drcr case when 'C' THEN amount *-1 Else NULL END in the form of credit.
Drcr case when had ' then amount end otherwise null flow
from a123)
Grant group);
top query results are below...
GRANT BALANCE
1 1234 6000
2 12345 9000
Please help me on this thanks...

Pretty obvious what is wrong:

you convert credit figures in negative numbers with the case statement

If you have

1 1234 1000 D

2 1234 -5000 C

3 12345 -2000 C

4 12345 7000 D

and after that you are subtracting these figures of your throughput numbers.

Therefore, do not convert negative credits before subtracting the or if you want to make negativ, then you must add them.

1000 + 5000 =-4000

1000-5000 = 6000

HTH

Text index CONTEXT Oracle which gives bad results!

Expert Oracle Text,

I'm on Oracle 11.2.0.2 on Solaris 10 and have implemented the Oracle text features using the CONTEXT index type, and I'm getting a few problems in. I have a need for research with joker as % and giving the wrong exit. Here's the scenario where I get incorrect results:

 

--creating preferences etc 
exec   ctxsys.ctx_ddl.create_preference ('cust_lexer', 'BASIC_LEXER'); 
exec   ctxsys.ctx_ddl.set_attribute ('cust_lexer', 'base_letter', 'YES'); -- removes diacritics 
exec   ctxsys.ctx_ddl.create_preference ('cust_wl', 'BASIC_WORDLIST') 
exec   ctxsys.ctx_ddl.set_attribute ;    ('cust_wl', 'SUBSTRING_INDEX', 'true'); 

--table set up 
CREATE TABLE TEST_USER 
( 
  FULL_NAME  VARCHAR2(64 CHAR)                  NOT NULL, 
  LAST_NAME  VARCHAR2(64 CHAR)                  NOT NULL 
); 


CREATE INDEX TEST_USER_IDX5 ON TEST_USER 
(FULL_NAME) 
INDEXTYPE IS CTXSYS.CONTEXT 
PARAMETERS('LEXER cust_lexer WORDLIST cust_wl SYNC (ON COMMIT)'); 

--data set up 
Insert into TEST_USER 
   (FULL_NAME, LAST_NAME) 
Values 
   ('Supervisor upervisor', 'upervisor'); 
Insert into TEST_USER 
   (FULL_NAME, LAST_NAME) 
Values 
   ('JOSEPH WILSON', 'WILSON'); 
Insert into TEST_USER 
   (FULL_NAME, LAST_NAME) 
Values 
   ('CHRISTOPHER Phil', 'TAYLOR'); 
Insert into TEST_USER 
   (FULL_NAME, LAST_NAME) 
Values 
   ('PAUL HERNANDEZ', 'HERNANDEZ'); 
Insert into TEST_USER 
   (FULL_NAME, LAST_NAME) 
Values 
   ('Betty Jipes', 'Jones'); 
Insert into TEST_USER 
   (FULL_NAME, LAST_NAME) 
Values 
   ('One Anna', 'Anna'); 
Insert into TEST_USER 
   (FULL_NAME, LAST_NAME) 
Values 
   ('Three Anna', 'Anna'); 
Insert into TEST_USER 
   (FULL_NAME, LAST_NAME) 
Values 
   ('Two Anna', 'Anna'); 
Insert into TEST_USER 
   (FULL_NAME, LAST_NAME) 
Values 
   ('Four Anna', 'Anna'); 
Insert into TEST_USER 
   (FULL_NAME, LAST_NAME) 
Values 
   ('Gary Barrow', 'Barrow'); 
COMMIT; 

--query using CONTAINS which gives WRONG output - because out intention is to return only those strings that START WITH the letter P but it returns another string that has P not at the starting!! 

SQL> select full_name from test_user where contains(full_name,'P%')>0; 

FULL_NAME 
---------------------------------------------------------------- 
PAUL HERNANDEZ 
CHRISTOPHER Phil 

-- I need output as follows in which the second value is not returned...meaning 'CHRISTOPHER Phil' should NOT be returned by the CONTAINS clause just as the LIKE operator below doesn't return it. 
SQL> select full_name from test_user where full_name like 'P%'; 

FULL_NAME 
---------------------------------------------------------------- 
PAUL HERNANDEZ

Please can anyone suggest what to do about it?

Thank you
OrauserN

No, you can skip all those, if you use SUBSTRING_INDEX.

MONTHS_BETWEEN gives strange results. What is the logic behind this?
Hello

Why third and fourth queries displays values less than 1?

SELECT MONTHS_BETWEEN (TO_DATE('28-FEB-2011'),

TO_DATE('01-FEB-2011')) FROM DUAL; -0.870967741935484

SELECT MONTHS_BETWEEN (TO_DATE('28-FEB-2011'),

TO_DATE('31-JAN-2011')) FROM DUAL; -1

SELECT MONTHS_BETWEEN (TO_DATE('28-FEB-2011'),

TO_DATE('30-JAN-2011')) FROM DUAL; -0.935483870967742?

SELECT MONTHS_BETWEEN (TO_DATE('28-FEB-2011'),

TO_DATE('29-JAN-2011')) FROM DUAL; -0.967741935483871?

SELECT MONTHS_BETWEEN (TO_DATE('28-FEB-2011'),

TO_DATE('28-JAN-2011')) FROM DUAL; -1

My understanding is that, for the first and the second query, oracle considers only 28 days in February and for the rest of the queries, oracle considers only 31 days in January. But even then, when you look at the output, it is not look great!

If the user asks about me, I'll have to give at least a stupid escape response!

There is another logic behind it?

Sébastien Thomas
Check out this link.

http://asktom.Oracle.com/pls/Apex/f?p=100:11:0:P11_QUESTION_ID:53374949268527

Concerning

REDA

sdo_cs. Transform gives incorrect results...
Hi all

I try to convert the projection Ordnance Survey coordinates WGS84, British National Grid. When the conversion comes out all points are approximately 100 metres west northwest. The native srid is 81989 (BGSO) and I am trying to convert 8307 or 4326, all two wgs84 lat/long and give the same results.

Is it possible the problem lies in the conversion between a Cartesian and spherical coordinate system?

Here is the code:

Select sdo_cs.transform (SDO_GEOMETRY (2001, 81989, SDO_POINT (367597, 80975, NULL), NULL, NULL), 8307) twice;

which translates into:

MDSYS. SDO_GEOMETRY (2001,8307, MDSYS. SDO_POINT_TYPE(-2.45816262176897,50.6276801063492,null), NULL, null)

However, the returned coordinates must be:

-2.45950270 / / 50.62750125

All comments appreciated! Thank you.
Yes, 10g did not have reference parameters required in the definition.

If you're on 10 gr 2 (for example, 10.2.0.4), you can update your SRID, with the following script (if you're on 10gR 1, please let me know, first of all).

(You can change the WKTEXT back the same way, if you cut and paste the current value of WKTEXT into a text backup file). Usually, we do not suggest to change the existing definitions, but rather to create new variants of these definitions. In this case, however, you simply change the definition of 10g in the definition of 11g, which is fine.
```
SQL> update
  sdo_cs_srs
set
  wktext =
'PROJCS["British National Grid",
  GEOGCS [ "Ordnance Survey Great Brit",
    DATUM ["Ordnance Survey Great Brit",
      SPHEROID ["Airy 1830", 6377563.396, 299.3249646], 375, -111,  431, 0, 0, 0, 1],
    PRIMEM [ "Greenwich", 0.000000 ],
    UNIT ["Decimal Degree", 0.01745329251994330]],
  PROJECTION ["Transverse Mercator"],
  PARAMETER ["Scale_Factor", 0.9996012717],
  PARAMETER ["Central_Meridian", -2.000000],
  PARAMETER ["Latitude_Of_Origin", 49.000000],
  PARAMETER ["False_Easting", 400000.000000],
  PARAMETER ["False_Northing", -100000.000000],
  UNIT ["Meter", 1.000000000000]]'
where
  srid = 81989;

1 row updated.

SQL> commit;

Commit complete.

SQL> select sdo_cs.transform(SDO_GEOMETRY(2001, 81989, SDO_POINT_TYPE(367597, 80975, NULL), NULL, NULL), 8307) fr
om dual;

SDO_CS.TRANSFORM(SDO_GEOMETRY(2001,81989,SDO_POINT_TYPE(367597,80975,NULL),NULL,
--------------------------------------------------------------------------------
SDO_GEOMETRY(2001, 8307, SDO_POINT_TYPE(-2.4595026, 50.6275011, NULL), NULL, NUL
L)
```
It works for you?

Plugin Check gives poor results for some Mac

On a Mac under OS X 10.6.8 (Snow Leopard) or versions earlier, Plugin check mark indicates the Applet Java plug-in and QuickTime plug-ins are obsolete.

Steps to reproduce:
Tools-> Add-ons-> Plugins-> check to see if your plugins are up to date

The results show:
Java Applet plugin update now
QuickTime plugin 7.6.6 update now

Explanation:
1. before Apple OS X 10.7 (Mountain Lion) provided Java. Apple did not provide an update. [thejava.com siteupdate requires Mac OS X (10.7.3 version and above)]
2. There is no update QuickTime plugin 7.6.6 for some Mac; It is a more recent OS x 10.6.3 via 10.6.8.

Plugin Check can be fixed?
Macs can get better help? (Some bugs without go back to Firefox 3.5 and before!)

I see your vote in: Bug 565832 - Plugin Check indicating QuickTime plugin 7.6.3 is "Obsolète"

7.6.6 also reported

do not have a new bug, it's ok. (I vote also)

Thank you

assessment polynomial vi giving inconsistent results

I'm looking at an easier method to evaluate polynomial, rather than using formulas nodes that I currently use. I found the "polynomial evaluation vi' who would think based on aid would be able to calculate the result of a polynomial Exhibitor multi.

Currently, I would do something like the following in a node of the formula:

float64 D1 = 0.387481063640E - 01;
float64 D2 = 0.332922278800E - 04;
float64 D3 = 0.206182434040E - 06;
float64 D4 = - 0.218822568460E - 08.
float64 D5 = 0.109968809280E - 10;
float64 D6 = - 0.308157587720E - 13;
float64 D7 = 0.454791352900E - 16;
float64 D8 = - 0.275129016730E - 19;

DC = (V * D1) +(D2*V**2) +(D3*V**3) +(D4*V**4) +(D5*V**5) +(D6*V**6) +(D7*V**7) +(D8*V**8).

I tried the same calculation by writing a little VI which used the polymomial assessment vi and get seriously incorrect results. (my vi attached).

Research in the evaluation of the polynomial vi, honestly, I don't know how it is supposed to work, unless he's trying to do something completely different that I do. (With the help of labview 2015)

I'm open to suggestions here. Thank you! Mitch

The first table is the constant term (V ^ 0 = 1), if you need to add an element that is equal to zero in the table of coefficients.

The polynomial is defined as:

DC = D0 + (V * D1) +(D2*V**2) +(D3*V**3) +(D4*V**4) +(D5*V**5) +(D6*V**6) +(D7*V**7) +(D8*V**8)

In your case, D0 = 0, but there still need to be there.

... and are not the constant diagram EXT. As you can see about to constraint, it will be converted in any case to DBL.

ID	Date	Val	tot
1	January 1, 13	1	9
2	2 January 13	3	8
3	3 January 13	4	7
4	January 4, 13	5	6
5	5 January 13	6	5

ID	Date	NET	CRE
1	January 1, 13	1	9
2	13 January 13	3	8
3	3 January 13	4	7
4	January 4, 13	5	6
5	5 January 13	6	5

	GRANT	AMOUNT	DRCR
1	1234	1000	D
2	1234	5000	C
3	12345	2000	C
4	12345	7000	D

GRANT	BALANCE
1234	-4000
12345	-5000

	GRANT	BALANCE
1	1234	6000
2	12345	9000

1	1234	1000	D
2	1234	-5000	C
3	12345	-2000	C
4	12345	7000	D

To_date gives inconsistent results?

Similar Questions

Maybe you are looking for