× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Thanks for the reply. I was planning on adding the delete to our backup process. (shut down subsystems, do backup, delete object, run startup).

For a longer term solution I was thinking of either doing this weekly (feels like overkill and a potential to add overhead that is not needed) or monthly. Maybe I could build a process to look at all packages and only delete when they get near the maximum size or are older than xxxxx days

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jack Kingsley
Sent: Thursday, January 05, 2012 10:14 AM
To: Midrange Systems Technical Discussion
Subject: Re: *SQLPKG object maintenance

Mike, I have had to do this a couple of times, you will have to have exclusive rights to the object in order to delete it.

On Thu, Jan 5, 2012 at 8:52 AM, Mike Cunningham <mike.cunningham@xxxxxxx>wrote:

We have an *SQLPKG object that has reached its maximum size and so we
are seeing errors in some remote ODBC connections. They are working OK
but probably not as efficiently as they could be. IBM documentation
says to just delete the object (once you can get a lock on it) and it
will start to rebuild itself. Since this is the first time we have
come across this issue I just wanted to see if anyone has ever seen
this issue and is the delete as safe as IBM says it is? We also
happened across this error by accident as it is not an easy one to
find. Does anyone just do a routine review of these objects and delete them on a regular basis?
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.