I hate those.but I can't really complain to BMC about it J

 

From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Kemes, Lisa
Sent: Thursday, April 05, 2012 9:33 AM
To: arslist@ARSLIST.ORG
Subject: Re: Large Character Fields even Larger?

 

** 

Thanks LJ!

 

I agree that it's probably #2 as well.  My fields are usually over 100,000
characters (or more) and no errors ever appeared even though I set it to
90,000 characters in the old system.  When I increased it to a more accurate
level in the new system, no more errors!

 

There have been other things that I've noticed as well that 7.6.04 SP2 is
catching that 7.1 p7 never caught before.

 

Thanks! 

Lisa 

 

 

  _____  

From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of LJ LongWing
Sent: Thursday, April 05, 2012 11:29 AM
To: arslist@ARSLIST.ORG
Subject: Re: Large Character Fields even Larger?

** 

Lisa,

As I move through the upgrades over the years I often start experiencing
issues with my application that I didn't have before the upgrade.  As I dig
into the issues I find one of two things

 

1 - The problem I'm having is a NEW bug in Remedy that's preventing
something from occurring properly that should work just fine, and did before
the upgrade

Or

2 - Remedy had what I call a 'functional bug' where something in their code
was not working properly.but now IS.and because it wasn't working properly
in the past, but allowed to do what I wanted, despite the fact that it
wasn't configured properly.I think it's #1, but it's really a problem in my
code, not theirs.

 

Your situation sounds like it might fall in the category of #2.where it
SHOULD have been throwing an error before.but because of a functional bug,
it allowed you to do something that you shouldn't have been able to do.but
now that they have tightened their net.your loophole is now closed J.  I
consider these good things because it means they are closing bugs in their
system that cause unanticipated behavior.

 

From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Kemes, Lisa
Sent: Thursday, April 05, 2012 9:03 AM
To: arslist@ARSLIST.ORG
Subject: Re: Large Character Fields even Larger?

 

** 

Possibly.  I was able to move the data from our current production (7.6.04
SP2) to our old production 7.1p7 and run my workflow and I didn't get any
errors.

 

It looks like when a field was updated with a filter the character limit
didn't matter (if it were manually updated through user tool or midtier it
would have popped up an error).  That was in 7.1 p7.

 

Now it looks like it matters whether it's populated with a filter or manual
in 7.6.04 SP2.....

 

Thanks! 

Lisa 

 

 

  _____  

From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Joe Martin D'Souza
Sent: Wednesday, April 04, 2012 4:55 PM
To: arslist@ARSLIST.ORG
Subject: Re: Large Character Fields even Larger?

** 

 

Have the DBA's converted the data to unicode? That would explain the
additional space requirement..

 

Joe

 

From: Kemes, Lisa <mailto:lisa.ke...@te.com>  

Sent: Wednesday, April 04, 2012 2:50 PM

Newsgroups: public.remedy.arsystem.general

To: arslist@ARSLIST.ORG 

Subject: Re: Large Character Fields even Larger?

 

** 

287,351 characters....

 

Thanks! 

Lisa 

 

 

  _____  

From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Grooms, Frederick W
Sent: Wednesday, April 04, 2012 2:44 PM
To: arslist@ARSLIST.ORG
Subject: Re: Large Character Fields even Larger?

** 

What is the largest amount of data in that field?

 

 

From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Kemes, Lisa
Sent: Wednesday, April 04, 2012 1:02 PM
To: arslist@ARSLIST.ORG
Subject: Re: Large Character Fields even Larger?

 

** 

Nevermind, when I increased it to 400,000 it now works.  Why would it work
in 7.1 p7 with 90000, but I have to increase it to 400,000 in 7.6.04 SP2?
The data is basically the same.  

 

Thanks! 

Lisa 

 

 

  _____  

From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Kemes, Lisa
Sent: Wednesday, April 04, 2012 1:57 PM
To: arslist@ARSLIST.ORG
Subject: Re: Large Character Fields even Larger?

** 

Sorry, I meant to say that I increased it to 200,000....

 

I just increased it again to 450,000 still same error message.

Thanks! 

Lisa 

 

 

  _____  

From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Kemes, Lisa
Sent: Wednesday, April 04, 2012 1:27 PM
To: arslist@ARSLIST.ORG
Subject: Large Character Fields even Larger?

** 

We upgraded from ARS 7.1 p7 to 7.6.04 SP2 and I'm found that one of my large
character fields that I've set to 90000 (for example) is getting errors that
the "Character String exceed maximum size allowed: 536870919" when I try to
set it.  It only happens to those records that do have quite a large amount
of characters, but this never happened in 7.1 p7.

 

I pushed it up to 20000 characters and I'm still getting the error.  Looks
like this is more on the DB side?  Should I talk to my DBA?

 

 

 

Lisa Kemes

AR System Developer
TEIS - USA

+1 717 810 2408 tel
+1 717 602 9460 mobile
lisa.ke...@te.com
100 Amp Drive

Harrisburg, PA 17112

 <http://www.te.com/> 

www.te.com <http://www.te.com/>  

 <http://twitter.com/teconnectivity>
<http://www.facebook.com/teconnectivity>
<http://www.flickr.com/photos/teconnectivity/>
<http://www.linkedin.com/groups?gid=1591657>
<http://www.youtube.com/teconnectivity> 

 

_attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ 

_attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ 

_attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_

_attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ 


_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"

Reply via email to