RE: [sqr-users] Odd SQR Behavior - Return code 256

["Larry Roux" <lroux@syr.edu>]

I agree that the source data has either a date formatted not like the code is 
expecting, or is sending a null. Another possibility is that the data is 
getting out of synch (ie one character off) so the data being read into the 
variables is not being lined up as you would expect.  
 
In a case like this you could add a display statement in the error to show the 
date field being used 
 
We had a case like this once, and it was foreign names with cedillas or 
accents.  Those are read as 2 characters and it pushed the position of the data 
over 1 space - and thus it pushed all the other data elements over 1 space - 
causing dates to be read wrong and the error you show.
 
 
 
 
 
 

________________________________

From: sqr-users-bounces+lroux=syr.edu@sqrug.org on behalf of Schelske, Steve K.
Sent: Sat 9/8/2007 9:44 AM
To: This list is for discussion about the SQR database reportinglanguage 
fromHyperion Solutions.
Subject: RE: [sqr-users] Odd SQR Behavior - Return code 256



I understand the potential issue with the date formatting, but any ideas whe 
the program might run successfully 20 times, then fail, then run 20 times again 
without any changes to the program or data?

That is the problem I'm trying to get my hands around.

________________________________

From: sqr-users-bounces+skschelske=aaamichigan.com@sqrug.org on behalf of 
George Jansen
Sent: Fri 9/7/2007 4:09 PM
To: sqr-users@sqrug.org
Subject: Re: [sqr-users] Odd SQR Behavior - Return code 256



Agreed with Bob Stone, almost certainly it is the client feeding a slightly 
wrong date string.

If you are simply providing the current date, then either

Sysdate

or, if you need just the day

Trunc(Sysdate)

will eliminate the nuisance of fooling around with To_Date NLS_DATE_FORMAT, and 
all that.

>>> "Schelske, Steve K." <SKSchelske@aaamichigan.com> 9/7/2007 3:12 PM >>>
We are running SQRs on a Windows server via Perl scripts against an
Oracle 10g RAC database on Linux.

I am coming across a very odd situation with various SQR programs.  Here
is what happens.

A program will run that has run successfully many times an it will fail
with the following error

(SQR 5528) ORACLE OCIStmtExecute error 1861 in cursor 7:
   ORA-01861: literal does not match format string

In this case Cursor 7 is
 Cursor #7:
   SQL = Insert INTO PS_A_EARN_TOT_TBL      (ERNCD, A_EARNS_TOTAL,
         A_HRS_TOTAL, DESCR) Select AA.ERNCD, 0, 0, AA.DESCR From
         PS_EARNINGS_TBL AA Where AA.EFFDT    = (select MAX(AA1.EFFDT)
From
         PS_EARNINGS_TBL AA1 Where AA.ERNCD   = AA1.ERNCD And
AA1.EFFDT <=
         :1)

where :1 is a string variable containing the current date

Then without making any changes to the program or data, the program is
restarted and runs successfully.

This seems to happen maybe 1 percent of the time and we have only seen
it happen in our production environment.

Does anyone have any ideas what could be causing this?

_______________________________________________
sqr-users mailing list
sqr-users@sqrug.org
http://www.sqrug.org/mailman/listinfo/sqr-users


_______________________________________________
sqr-users mailing list
sqr-users@sqrug.org
http://www.sqrug.org/mailman/listinfo/sqr-users




_______________________________________________
sqr-users mailing list
sqr-users@sqrug.org
http://www.sqrug.org/mailman/listinfo/sqr-users