Re: Value too large for the meta table FIELD_DISPROP table!!!

2008-05-14 Thread Joe DeSouza
It is a Unicode setup, and I had set the environment variable NLS_LANG on the 
database server to American_America.UTF8
Does this have to be setup in the ardbc.cfg file too? If so what is the 
paramter name?
Joe

- Original Message 
From: Walters, Mark [EMAIL PROTECTED]
To: arslist@ARSLIST.ORG
Sent: Tuesday, May 13, 2008 5:14:32 PM
Subject: Re: Value too large for the meta table FIELD_DISPROP table!!!

** 
Joe,
 
Is this a Unicode ARS installation and which platform is it on?  Does the view 
contain accented characters?  If so it may be that the NLS_LANG is not set 
correctly – for Unicode systems it should end .AL32UTF8
 
Mark Walters
 
The opinions, statements, and/or suggested courses of action expressed in this 
E-mail do not necessarily reflect those of BMC Software, Inc.  My voluntary 
participation in this forum is not intended to convey a role as a spokesperson, 
liaison or support representative for BMC Software, Inc.
 
 
 
From:Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] 
On Behalf Of Joe DeSouza
Sent: 13 May 2008 21:45
To: arslist@ARSLIST.ORG
Subject: Value too large for the meta table FIELD_DISPROP table!!!
 
** 
I got this strange error when the SLM install script was trying to import one 
of the views. This is strange considering that a value being inserted into a 
meta data table should not have technically overshot the column length..
 
Failure during SQL operation to the database: ORA-12899: value too large for 
column ARADMIN701.FIELD_DISPPROP.PROPSHORT (actual: 270, maximum: 255) 
(ARERR 552)
 
It looks like the data that needs to be written to this column is 15 characters 
too large..
 
Has anyone else seen a problem like this and if so how did you'll get around 
it? I'm not quite excited by the thought of having to alter a meta data table 
although that seems to be the only logical thing to do given this situation..
 
Cheers
 
Joe D'Souza
 
__Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are html___ 
__Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are html___




___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are

Re: Value too large for the meta table FIELD_DISPROP table!!!

2008-05-14 Thread Walters, Mark
What platform is the ARS server running on?  You mention ardb.cfg so is
it Windows?  The Oracle client used by ARS needs to have NLS_LANG set.
On Windows it is a registry key - exactly which one depends on the type
of Oracle client installed.  On Unix this can be done via the arsystem
script or an environment variable.   

 

I suspect you may find a registry key where NLS_LANG is set to
lang_country.WE8MSWIN1252 on the ARS server system.

 

Database server

 

NLS_LENGTH_SEMANTICS = BYTE

NLS_CHARACTERSET = language_country.UTF8 (or AL32UTF8)

 

Database CLIENT

 

NLS_LANG = language_country.UTF8 (or AL32UTF8)

 

Mark

 

From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Joe DeSouza
Sent: 14 May 2008 12:16
To: arslist@ARSLIST.ORG
Subject: Re: Value too large for the meta table FIELD_DISPROP table!!!

 

** 

It is a Unicode setup, and I had set the environment variable NLS_LANG
on the database server to American_America.UTF8

 

Does this have to be setup in the ardbc.cfg file too? If so what is the
paramter name?

 

Joe

- Original Message 
From: Walters, Mark [EMAIL PROTECTED]
To: arslist@ARSLIST.ORG
Sent: Tuesday, May 13, 2008 5:14:32 PM
Subject: Re: Value too large for the meta table FIELD_DISPROP table!!!

** 

Joe,

 

Is this a Unicode ARS installation and which platform is it on?  Does
the view contain accented characters?  If so it may be that the NLS_LANG
is not set correctly - for Unicode systems it should end .AL32UTF8

 

Mark Walters

 

The opinions, statements, and/or suggested courses of action expressed
in this E-mail do not necessarily reflect those of BMC Software, Inc.
My voluntary participation in this forum is not intended to convey a
role as a spokesperson, liaison or support representative for BMC
Software, Inc.

 

 

 

From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Joe DeSouza
Sent: 13 May 2008 21:45
To: arslist@ARSLIST.ORG
Subject: Value too large for the meta table FIELD_DISPROP table!!!

 

** 

I got this strange error when the SLM install script was trying to
import one of the views. This is strange considering that a value being
inserted into a meta data table should not have technically overshot the
column length..

 

Failure during SQL operation to the database: ORA-12899: value too large
for column ARADMIN701.FIELD_DISPPROP.PROPSHORT (actual: 270,
maximum: 255) (ARERR 552)

 

It looks like the data that needs to be written to this column is 15
characters too large..

 

Has anyone else seen a problem like this and if so how did you'll get
around it? I'm not quite excited by the thought of having to alter a
meta data table although that seems to be the only logical thing to do
given this situation..

 

Cheers

 

Joe D'Souza

 

__Platinum Sponsor: www.rmsportal.com http://www.rmsportal.com/
ARSlist: Where the Answers Are html___ 

__Platinum Sponsor: www.rmsportal.com http://www.rmsportal.com/
ARSlist: Where the Answers Are html___

 

__Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are
html___ 


___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are


Re: Value too large for the meta table FIELD_DISPROP table!!!

2008-05-14 Thread Joe D'Souza
Thank you.. I'll check these settings as soon as I get to work..

Joe
  -Original Message-
  From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] Behalf Of Walters, Mark
  Sent: Wednesday, May 14, 2008 7:48 AM
  To: arslist@ARSLIST.ORG
  Subject: Re: Value too large for the meta table FIELD_DISPROP table!!!


  **
  What platform is the ARS server running on?  You mention ardb.cfg so is it
Windows?  The Oracle client used by ARS needs to have NLS_LANG set.  On
Windows it is a registry key – exactly which one depends on the type of
Oracle client installed.  On Unix this can be done via the arsystem script
or an environment variable.



  I suspect you may find a registry key where NLS_LANG is set to
lang_country.WE8MSWIN1252 on the ARS server system.



  Database server



  NLS_LENGTH_SEMANTICS = BYTE

  NLS_CHARACTERSET = language_country.UTF8 (or AL32UTF8)



  Database CLIENT



  NLS_LANG = language_country.UTF8 (or AL32UTF8)



  Mark



  From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Joe DeSouza
  Sent: 14 May 2008 12:16
  To: arslist@ARSLIST.ORG
  Subject: Re: Value too large for the meta table FIELD_DISPROP table!!!



  **

  It is a Unicode setup, and I had set the environment variable NLS_LANG on
the database server to American_America.UTF8



  Does this have to be setup in the ardbc.cfg file too? If so what is the
paramter name?



  Joe

  - Original Message 
  From: Walters, Mark [EMAIL PROTECTED]
  To: arslist@ARSLIST.ORG
  Sent: Tuesday, May 13, 2008 5:14:32 PM
  Subject: Re: Value too large for the meta table FIELD_DISPROP table!!!

  **

  Joe,



  Is this a Unicode ARS installation and which platform is it on?  Does the
view contain accented characters?  If so it may be that the NLS_LANG is not
set correctly – for Unicode systems it should end .AL32UTF8



  Mark Walters



  The opinions, statements, and/or suggested courses of action expressed in
this E-mail do not necessarily reflect those of BMC Software, Inc.  My
voluntary participation in this forum is not intended to convey a role as a
spokesperson, liaison or support representative for BMC Software, Inc.







  From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Joe DeSouza
  Sent: 13 May 2008 21:45
  To: arslist@ARSLIST.ORG
  Subject: Value too large for the meta table FIELD_DISPROP table!!!



  **

  I got this strange error when the SLM install script was trying to import
one of the views. This is strange considering that a value being inserted
into a meta data table should not have technically overshot the column
length..



  Failure during SQL operation to the database: ORA-12899: value too large
for column ARADMIN701.FIELD_DISPPROP.PROPSHORT (actual: 270, maximum:
255) (ARERR 552)



  It looks like the data that needs to be written to this column is 15
characters too large..



  Has anyone else seen a problem like this and if so how did you'll get
around it? I'm not quite excited by the thought of having to alter a meta
data table although that seems to be the only logical thing to do given this
situation..



  Cheers



  Joe D'Souza

No virus found in this outgoing message.
Checked by AVG.
Version: 7.5.524 / Virus Database: 269.23.16/1430 - Release Date: 5/13/2008
7:31 AM

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are


Re: Value too large for the meta table FIELD_DISPROP table!!!

2008-05-13 Thread Walters, Mark
Joe,

 

Is this a Unicode ARS installation and which platform is it on?  Does
the view contain accented characters?  If so it may be that the NLS_LANG
is not set correctly - for Unicode systems it should end .AL32UTF8

 

Mark Walters

 

The opinions, statements, and/or suggested courses of action expressed
in this E-mail do not necessarily reflect those of BMC Software, Inc.
My voluntary participation in this forum is not intended to convey a
role as a spokesperson, liaison or support representative for BMC
Software, Inc.

 

 

 

From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Joe DeSouza
Sent: 13 May 2008 21:45
To: arslist@ARSLIST.ORG
Subject: Value too large for the meta table FIELD_DISPROP table!!!

 

** 

I got this strange error when the SLM install script was trying to
import one of the views. This is strange considering that a value being
inserted into a meta data table should not have technically overshot the
column length..

 

Failure during SQL operation to the database: ORA-12899: value too large
for column ARADMIN701.FIELD_DISPPROP.PROPSHORT (actual: 270,
maximum: 255) (ARERR 552)

 

It looks like the data that needs to be written to this column is 15
characters too large..

 

Has anyone else seen a problem like this and if so how did you'll get
around it? I'm not quite excited by the thought of having to alter a
meta data table although that seems to be the only logical thing to do
given this situation..

 

Cheers

 

Joe D'Souza

 

__Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are
html___ 


___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are