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 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.
midrange.com
