The syntax for in row and out of row LOBs is different. It takes place in
the create table statement. If it is not an installation option, there is no
way to tell the installer what to do, so the installer will do what it is
programmed to - create all lobs out of raw when you install new apps
(create new tables). The only fix would be a conversion script after the
tables are created.
Regards,
Nicky Madjarov
phone: 973-202-4278
Find out how to bust your AR System performance @
http://www.SpeedUpARS.com
----- Original Message -----
From: "William Rentfrow" <[email protected]>
Newsgroups: public.remedy.arsystem.general
To: <[email protected]>
Sent: Monday, April 27, 2009 5:01 PM
Subject: Re: Oracle LOB getting very big
A clever person might decide the obvious solution to this is to install
the AR Server, then switch the server setting to "in-row", run the
conversion, and then install the rest of the ITSM apps.
That clever person would be wrong. We tried this and the ITSM installer
(specifically IM and SLM if I remember correctly) conveniently reset the
option to out of row storage.
This definitely should be an installer option for the AR Server.
William Rentfrow
Principal Consultant, StrataCom Inc.
[email protected]
www.williamrentfrow.com
O 715-592-5185
C 715-410-8056
________________________________
From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of Axton
Sent: Monday, April 27, 2009 10:57 AM
To: [email protected]
Subject: Re: Oracle LOB getting very big
** Nope.
Take a look at the recommendation on page 5 of this Oracle white paper:
http://www.oracle.com/technology/products/database/application_developme
nt/pdf/lob_performance_guidelines.pdf
Axton Grams
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 public relations representative for
BMC Software, Inc.
On Mon, Apr 27, 2009 at 10:48 AM, Guillaume Rheault
<[email protected]> wrote:
**
Unfortunately with the BMC ITSM apps, we don't have a choice of
not using LOBs, right?
Or do we?
-Guillaume
-----Original Message-----
From: Action Request System discussion list(ARSList) on behalf
of Axton
Sent: Mon 04/27/09 11:42 AM
To: [email protected]
Subject: Re: Oracle LOB getting very big
Unless explicitly defined when creating a lob, storing the lob
out of row is
the default behavior. I'm guessing the authors wanted to adhere
to the
defaults. I do know that when performing the ARS installation,
the LOB
storage parameter for the meta-data tables (e.g, arschema) is
set to store
the lob in-row.
Imho, it's better to just not use lobs.
Axton
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 public relations representative for BMC
Software,
Inc.
On Mon, Apr 27, 2009 at 9:23 AM, Guillaume Rheault
<[email protected]>wrote:
**
That is the $60000 question.
Seems to me the ARS installer should ask what the value of
that setting
should be set to
-Guillaume
-----Original Message-----
From: Action Request System discussion list(ARSList) on behalf
of Misi
Mladoniczky
Sent: Mon 04/27/09 6:40 AM
To: [email protected]
Subject: Re: Oracle LOB getting very big
Hi,
Thank you all for the responses.
One thing confuses me though...
In all these comparisons, the In-Row-LOB requires less space
and is faster.
Why has BMC set the default to Out-Row-LOB? Especially since
older AR
System Versions seems to use the In-Row-LOB setting???
Best Regards - Misi, RRR AB, http://www.rrr.se
Products from RRR Scandinavia:
* RRR|License - Not enough Remedy licenses? Save money by
optimizing.
* RRR|Log - Performance issues or elusive bugs? Analyze your
Remedy logs.
* RRR|Translator - Manage and automate your language
translations.
Find these products, and many free tools and utilities, at
http://rrr.se.
> Just for everyone's records, there's also a white paper on
the subject:
>
> 17-Mar-2008 Using Oracle CLOBs with BMC Remedy Action
Request System
>
http://documents.bmc.com/supportu/documents/96/63/89663/89663.pdf
>
> -David J. Easter
> Sr. Product Manager, Solution Strategy and Development
> BMC Software, Inc.
> 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 public relations representative
for BMC
> Software, Inc.
>
> ________________________________________
> From: Action Request System discussion list(ARSList) [
[email protected]]
> On Behalf Of Shellman, David
[[email protected]]
> Sent: Friday, April 24, 2009 6:39 AM
> To: [email protected]
> Subject: Re: Oracle LOB getting very big
>
> Misi,
>
> I see Axton replied. He had some good info on this.
>
> Here is a sql command that BMC/Remedy support gave me to
show lob space
> allocation
>
> select substr(s.segment_name,1,30) Lobsegment, l.table_name,
> substr(l.column_name,1,12) Column_name,
sum(s.bytes/1024/1024) Mbytes
> from user_segments s, user_lobs l
> where l.segment_name = s.segment_name
> having sum(s.bytes/1024/1024) > 100
> group by s.segment_name, l.table_name, l.column_name
> order by sum(s.bytes/1024/1024);
>
> Dave
> -----Original Message-----
> From: Action Request System discussion list(ARSList)
</d_Platinum Sponsor: [email protected] ARSlist: "Where
the Answers Are"_
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
