Bless the ARSList! That is exactly the document I need! Thank you, Sean and Chris.
Jennifer Meyer Remedy Technical Support Specialist State of North Carolina Office of Information Technology Services Service Delivery Division ITSM & ITAM Services Office: 919-754-6543 ITS Service Desk: 919-754-6000 jennifer.me...@nc.gov<mailto:jennifer.me...@nc.gov> http://its.state.nc.us<http://its.state.nc.us/> E-mail correspondence to and from this address may be subject to the North Carolina Public Records Law and may be disclosed to third parties only by an authorized State Official. From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Garrison, Sean (Norcross) Sent: Wednesday, July 28, 2010 1:16 PM To: arslist@ARSLIST.ORG Subject: Possibly spam: Re: RRR|Chive SAN Disk Space issues ** Assuming you are using Oracle: BMC has a doc out there talking about LOB storage being "In-Row" vs "Out of Row". There is also a way to convert the data for existing tables using a stored procedure from "In-Row" from "Out of Row". The document is called "RemedyAndOracleClobs.pdf" Also make sure the "Store Clob In-Row" option is checked. This only helps for future tables not current ones. You have to run the stored procedure to fix the old ones. Doing this reduced our DB size considerably. Thanks, Sean From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Meyer, Jennifer L Sent: Wednesday, July 28, 2010 12:56 PM To: arslist@ARSLIST.ORG Subject: RRR|Chive SAN Disk Space issues ** Dear Listers, I have been archiving our NTE:Notifier Log records since the 15th of July using RRR|Chive to move records from NTE:Notifier Log to an archive table. The process has been smooth and quiet, but the Archive form has been eating up disk space. Yesterday, we nearly ran out of disk space on our SAN and had to add an emergency 200 GB of disk space. I moved 250K Notification Logs from the original NTE:Notification Log (T587) to the Notification Log Archive (T2057) yesterday. Those 250K records took up nearly 6G of table space. Growth (MB) Owner Type Segment Name Lob Parent Tabl Lob Column ------------- ---------- --------------- ------------------------- --------------- ------------------------- 2,954.77 ARADMIN LOBSEGMENT SYS_LOB0000426378C00018$$ T2057 C840000827 2,939.00 ARADMIN LOBSEGMENT SYS_LOB0000426378C00020$$ T2057 C840000820 156.77 ARADMIN LOBSEGMENT SYS_LOB0000084949C00022$$ T587 C1000000827 156.24 ARADMIN LOBSEGMENT SYS_LOB0000085002C00126$$ T590 C1000000827 154.55 ARADMIN LOBSEGMENT SYS_LOB0000053052C00021$$ T69 C18091 The question I have for the list is: has anyone else seen this out-of-control growth when archiving records? Is this perhaps due to a write process that may be sloppy? Is truncating LOBs the answer? Jennifer Meyer Remedy Technical Support Specialist State of North Carolina Office of Information Technology Services Service Delivery Division ITSM & ITAM Services Office: 919-754-6543 ITS Service Desk: 919-754-6000 jennifer.me...@nc.gov<mailto:jennifer.me...@nc.gov> http://its.state.nc.us<http://its.state.nc.us/> E-mail correspondence to and from this address may be subject to the North Carolina Public Records Law and may be disclosed to third parties only by an authorized State Official. _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"