RE: [sqr-users] Error after Oracle update

["Fred Schiff" <fschiff@metlife.com>]

Thanks.
Could I depend on you to tell me what Peoplesoft's solution is?


                                 
         Fred Schiff             
         Information Systems     
         Consultant              
         Broker Dealer IT        
         fschiff@metlife.com     
         732-734-2155            
                                 





                      "Alexander, Steve"
                      <Steven.Alexander@sanjoseca.gov>            To:
"'This list is for discussion about the SQR database reportinglangu age   
                      Sent by:                                     from
Hyperion Solutions.'" <sqr-users@sqrug.org>                                   
                      sqr-users-bounces+fschiff=metlife.co        cc:
                      m@sqrug.org                                 Subject:
RE: [sqr-users] Error after Oracle update                                 
                      10/21/2004 02:30 PM
                      Please respond to "This list is for
                      discussion about the SQR database
                      reporting language from Hyperion
                      Solutions."





Here is some discussion from a year ago:

From: amy.harvel@phoenix.gov [mailto:amy.harvel@phoenix.gov]
Sent: Friday, October 17, 2003 8:54 AM
To: sqr-users@sqrug.org
Subject: Re: [sqr-users] (SQR 6806) String2Em: String to Decimal Object
Conversion Error.


Funny -- we had the same error yesterday -- there is a work around -- DONT
change any SQR's.

Find Solution id 200744351 on PeopleSoft's web.

What we found was the select works in Oracle -- not in SQR -- issue is the
numbers (comment them out in the SQR or make them to_char).  Describe the
view -- notice the numbers are just Number's not Number(38) or number
(5,2) -- SQR can't handle a number that has not length.  The solution
fixes the problem -- its an Oracle "behavior change"


Amy M. Harvel
City Of Phoenix Information Technology Department
Programmer III
602-261-8974





From: Peter Burton [mailto:pburton@brio.com]
Sent: Wednesday, September 17, 2003 2:03 AM
To: 'sqr-users@sqrug.org'
Cc: 'rawender_Guron@rta.nsw.gov.au'
Subject: RE: [sqr-users] '(SQR 6806) String2Em: String to Decimal Object
C onversion Error' on Oracle 9.2.0.3


Rawender,

Have a DBA issue the following command:

alter system set event='10499 trace name context forever,level 1'
COMMENT='return 0 for the scale if NUMBER created without specifying the
scale'
SCOPE=SPFILE

Peter





From: GURON Rawender [mailto:rawender_Guron@rta.nsw.gov.au]
Sent: Wednesday, September 17, 2003 2:52 AM
To: 'sqr-users@sqrug.org'
Subject: [sqr-users] '(SQR 6806) String2Em: String to Decimal Object
Conversion Error' on Oracle 9.2.0.3


Hi All,

I need help with this error. An sqr program with a simple sql:

begin-select
seq_test.nextval       &seq_test_val
from dual

end-select

Comes back with the error in the subject. The sqr version is 6.1.3 and it
compiles alright in oracle 9.2.0.3 but fails with the error at runtime. The
program works fine when compiled on Oracle 8.1.7.0 and run on Oracle
9.2.0.3. I relinked of sqr with Oracle 9 libraries, but the program still
fails with the same error.

As this problem seems to be quite widespread and a lot of people have
reported this. Does anyone know if Brio Software has come up with a patch
or
a solution to fix it?

I know there are workarounds, but they involve changing the code and we are
looking for some elegant solutiuon. We have hundreds of programs, therefore
changing the code to fix the problem is out of question.

Thanks
Rawender Guron





-----Original Message-----
From: Fred Schiff [mailto:fschiff@metlife.com]
Sent: Wednesday, October 20, 2004 7:33 AM
To: sqr-users@sqrug.org
Subject: [sqr-users] Error after Oracle update


I've been getting this error after an Oracle patch update on our HPUX box.

Error on line 302:
   (SQR 6806) String2Em: String to Decimal Object Conversion Error.

This seems to be because fields which were type NUMBER
have now become type FLOAT(*).

Odd thing is, that the fields show as type NUMBER in the database still,
but an sqlplus desc on the table shows them as type FLOAT(*).

(We are still using the dread SQL*FORMS 3, so I think we have done
something
to either our TNS or sqlplus to use the version from Oracle 7, to enable us
to still run forms)

Any ideas?




 (Embedded     Fred Schiff
 image moved   Information Systems
 to file:      Consultant
 pic02851.gif) Broker Dealer IT
               fschiff@metlife.com
               732-734-2155





The information contained in this message may be CONFIDENTIAL and is for
the
intended addressee only.  Any unauthorized use, dissemination of the
information, or copying of this message is prohibited.  If you are not the
intended addressee, please notify the sender immediately and delete this
message.

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






The information contained in this message may be CONFIDENTIAL and is for the
intended addressee only.  Any unauthorized use, dissemination of the
information, or copying of this message is prohibited.  If you are not the
intended addressee, please notify the sender immediately and delete this
message.


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