Anonymous_User Absent Member.
Absent Member.
2625 views

MSSQL database grown huge

Hi

I'm working with client on ZCM databse issue. SLES based Linux with
MSSQL2005 on W2K3 server. Were originally on 10.20, but have been 10.2.1
for 6 months. Have just updated to 10.2.2. successfully.

The SQL database .mdb is huge and has practically filled the 50GB volume.
When I check out the table sizes of live data I find the top 3 are
responsible:

zStatusEvent 10.1GB
zObjectInfo 35.6GB
zMessageParam 0.5GB

Now I can dealt with the excessive messages stored easy enough, but
zStatusEvent and zObjectInfo?

I notice a TID on this issue :
http://www.novell.com/support/viewContent.do?externalId=7004256&sliceId=1
which says :

"The zStatusEvent and zObjectInfo tables in the ZCM database may grow larger
than necessary and use up more space than required and degrade performance
from optimal levels."

In the immortal words of Jerry Lundegaard in Fargo: "Your darn'd tootin'!"

No additional info is given in the TID except to say it is fixed in 10.2.1.
Since they have been on 10.2.1 for a while, should they not have seen a
resolution? Is there anything I can do except log a Novell support call?

regards
Martin


Labels (2)
0 Likes
7 Replies
Micro Focus Expert
Micro Focus Expert

Re: MSSQL database grown huge

I will have someone update that TID update with additional details.
Ping back here if you don't see an update.



On 2/19/2010 8:23 AM, Martin Farrer wrote:
> Hi
>
> I'm working with client on ZCM databse issue. SLES based Linux with
> MSSQL2005 on W2K3 server. Were originally on 10.20, but have been 10.2.1
> for 6 months. Have just updated to 10.2.2. successfully.
>
> The SQL database .mdb is huge and has practically filled the 50GB
> volume. When I check out the table sizes of live data I find the top 3
> are responsible:
>
> zStatusEvent 10.1GB
> zObjectInfo 35.6GB
> zMessageParam 0.5GB
>
> Now I can dealt with the excessive messages stored easy enough, but
> zStatusEvent and zObjectInfo?
>
> I notice a TID on this issue :
> http://www.novell.com/support/viewContent.do?externalId=7004256&sliceId=1
> which says :
>
> "The zStatusEvent and zObjectInfo tables in the ZCM database may grow
> larger than necessary and use up more space than required and degrade
> performance from optimal levels."
>
> In the immortal words of Jerry Lundegaard in Fargo: "Your darn'd tootin'!"
>
> No additional info is given in the TID except to say it is fixed in
> 10.2.1. Since they have been on 10.2.1 for a while, should they not have
> seen a resolution? Is there anything I can do except log a Novell
> support call?
>
> regards
> Martin
>
>


--
Please give a hearty thumbs up to any post you find helpful!
To find articles by Craig Wilson simply follow the link: Craig Wilson's Tips!
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: MSSQL database grown huge

That's brilliant (I hope), and very fast too.

thanks

Martin

"craig wilson" <craig_d_wilson@yahoo.com> wrote in message
news:kywfn.3535$yE3.597@kovat.provo.novell.com...
> I will have someone update that TID update with additional details.
> Ping back here if you don't see an update.
>
>
>
> On 2/19/2010 8:23 AM, Martin Farrer wrote:
>> Hi
>>
>> I'm working with client on ZCM databse issue. SLES based Linux with
>> MSSQL2005 on W2K3 server. Were originally on 10.20, but have been 10.2.1
>> for 6 months. Have just updated to 10.2.2. successfully.
>>
>> The SQL database .mdb is huge and has practically filled the 50GB
>> volume. When I check out the table sizes of live data I find the top 3
>> are responsible:
>>
>> zStatusEvent 10.1GB
>> zObjectInfo 35.6GB
>> zMessageParam 0.5GB
>>
>> Now I can dealt with the excessive messages stored easy enough, but
>> zStatusEvent and zObjectInfo?
>>
>> I notice a TID on this issue :
>> http://www.novell.com/support/viewContent.do?externalId=7004256&sliceId=1
>> which says :
>>
>> "The zStatusEvent and zObjectInfo tables in the ZCM database may grow
>> larger than necessary and use up more space than required and degrade
>> performance from optimal levels."
>>
>> In the immortal words of Jerry Lundegaard in Fargo: "Your darn'd
>> tootin'!"
>>
>> No additional info is given in the TID except to say it is fixed in
>> 10.2.1. Since they have been on 10.2.1 for a while, should they not have
>> seen a resolution? Is there anything I can do except log a Novell
>> support call?
>>
>> regards
>> Martin
>>
>>

>

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: MSSQL database grown huge

No update as yet Craig. Big help if this is available for Wednesday. If
you could give someone a little poke that'd be great.

"craig wilson" <craig_d_wilson@yahoo.com> wrote in message
news:kywfn.3535$yE3.597@kovat.provo.novell.com...
> I will have someone update that TID update with additional details.
> Ping back here if you don't see an update.
>
>
>
> On 2/19/2010 8:23 AM, Martin Farrer wrote:
>> Hi
>>
>> I'm working with client on ZCM databse issue. SLES based Linux with
>> MSSQL2005 on W2K3 server. Were originally on 10.20, but have been 10.2.1
>> for 6 months. Have just updated to 10.2.2. successfully.
>>
>> The SQL database .mdb is huge and has practically filled the 50GB
>> volume. When I check out the table sizes of live data I find the top 3
>> are responsible:
>>
>> zStatusEvent 10.1GB
>> zObjectInfo 35.6GB
>> zMessageParam 0.5GB
>>
>> Now I can dealt with the excessive messages stored easy enough, but
>> zStatusEvent and zObjectInfo?
>>
>> I notice a TID on this issue :
>> http://www.novell.com/support/viewContent.do?externalId=7004256&sliceId=1
>> which says :
>>
>> "The zStatusEvent and zObjectInfo tables in the ZCM database may grow
>> larger than necessary and use up more space than required and degrade
>> performance from optimal levels."
>>
>> In the immortal words of Jerry Lundegaard in Fargo: "Your darn'd
>> tootin'!"
>>
>> No additional info is given in the TID except to say it is fixed in
>> 10.2.1. Since they have been on 10.2.1 for a while, should they not have
>> seen a resolution? Is there anything I can do except log a Novell
>> support call?
>>
>> regards
>> Martin
>>
>>

>

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: MSSQL database grown huge

Hi Craig,
still no update on that TID. 😞

regards
Martin

"craig wilson" <craig_d_wilson@yahoo.com> wrote in message
news:kywfn.3535$yE3.597@kovat.provo.novell.com...
> I will have someone update that TID update with additional details.
> Ping back here if you don't see an update.
>
>
>
> On 2/19/2010 8:23 AM, Martin Farrer wrote:
>> Hi
>>
>> I'm working with client on ZCM databse issue. SLES based Linux with
>> MSSQL2005 on W2K3 server. Were originally on 10.20, but have been 10.2.1
>> for 6 months. Have just updated to 10.2.2. successfully.
>>
>> The SQL database .mdb is huge and has practically filled the 50GB
>> volume. When I check out the table sizes of live data I find the top 3
>> are responsible:
>>
>> zStatusEvent 10.1GB
>> zObjectInfo 35.6GB
>> zMessageParam 0.5GB
>>
>> Now I can dealt with the excessive messages stored easy enough, but
>> zStatusEvent and zObjectInfo?
>>
>> I notice a TID on this issue :
>> http://www.novell.com/support/viewContent.do?externalId=7004256&sliceId=1
>> which says :
>>
>> "The zStatusEvent and zObjectInfo tables in the ZCM database may grow
>> larger than necessary and use up more space than required and degrade
>> performance from optimal levels."
>>
>> In the immortal words of Jerry Lundegaard in Fargo: "Your darn'd
>> tootin'!"
>>
>> No additional info is given in the TID except to say it is fixed in
>> 10.2.1. Since they have been on 10.2.1 for a while, should they not have
>> seen a resolution? Is there anything I can do except log a Novell
>> support call?
>>
>> regards
>> Martin
>>
>>

>

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: MSSQL database grown huge

Ah thanks Craig, the TID's now been updated. I'm thinking that's going to
take some time to clear out 4 million records. Fun, fun, fun!

regards
Martin

"craig wilson" <craig_d_wilson@yahoo.com> wrote in message
news:kywfn.3535$yE3.597@kovat.provo.novell.com...
> I will have someone update that TID update with additional details.
> Ping back here if you don't see an update.
>
>
>
> On 2/19/2010 8:23 AM, Martin Farrer wrote:
>> Hi
>>
>> I'm working with client on ZCM databse issue. SLES based Linux with
>> MSSQL2005 on W2K3 server. Were originally on 10.20, but have been 10.2.1
>> for 6 months. Have just updated to 10.2.2. successfully.
>>
>> The SQL database .mdb is huge and has practically filled the 50GB
>> volume. When I check out the table sizes of live data I find the top 3
>> are responsible:
>>
>> zStatusEvent 10.1GB
>> zObjectInfo 35.6GB
>> zMessageParam 0.5GB
>>
>> Now I can dealt with the excessive messages stored easy enough, but
>> zStatusEvent and zObjectInfo?
>>
>> I notice a TID on this issue :
>> http://www.novell.com/support/viewContent.do?externalId=7004256&sliceId=1
>> which says :
>>
>> "The zStatusEvent and zObjectInfo tables in the ZCM database may grow
>> larger than necessary and use up more space than required and degrade
>> performance from optimal levels."
>>
>> In the immortal words of Jerry Lundegaard in Fargo: "Your darn'd
>> tootin'!"
>>
>> No additional info is given in the TID except to say it is fixed in
>> 10.2.1. Since they have been on 10.2.1 for a while, should they not have
>> seen a resolution? Is there anything I can do except log a Novell
>> support call?
>>
>> regards
>> Martin
>>
>>

>

0 Likes
icsbergs Absent Member.
Absent Member.

Re: MSSQL database grown huge

I had this same problem with 10.2.1 causing my database to grow to 4-5 GB with the same table taking a alot of space.

Any way to clean this up?
0 Likes
jbericks Frequent Contributor.
Frequent Contributor.

Re: MSSQL database grown huge

We had a table (zStatusEvent, I think) that had about 3.2 million rows. Ran a query to clean it up, and a couple weeks later it was back up to around 300,000. Hopefully this bug is fixed in 10.3.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.