cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
jmcleish
Reliable Contributor
Reliable Contributor
Report Inappropriate Content
Message 1 of 8

ePO DB mdf size failed in PIA for upgrade 5.3.1. to 5.9.1

Jump to solution

Hi,

I'm running the Pre-Installation auditor to check the issues with upgrading 5.3.1 to 5.9.1 and it fails on disk space.

Now something had gone wrong with my client purge events and the DB grew to 200GB. I've manually gone through purging a lot of events and now its down to ~45GB. THe MDF tho is still 200GB

The thing is the PIA thinks that is the actual DB sile size and therfore says theres not enough space for the upgrade. There is 136GB free on C:

Will the installation to 5.9.1 fail because the DB file is 200Gb?
What can i do?

I know its not recommended to shrink the DB and causes index fragmentation but might i need to as a one off so i can upgrade?
Any help appreciated.

 Thanks

Database File Growth Matrix:

DATABASE/LOG DRIVE CURRENT LIMIT EXPECTED
------------------------------------------------------------------------------------------------------
ePO Database C 195.38 GB Unlimited 293.06 GB
ePO transaction log C 1.88 GB 2.00 TB 195.38 GB
Temp Database C 8.00 MB Unlimited 136.76 GB
Temp transaction log C 512.00 KB Unlimited 100.00 MB


DRIVE AVAILABLE REQUIRED
------------------------------------------------------------------------------------------------------
c: 137.76 GB 428.04 GB


Drive c: does not have enough space

3 Solutions

Accepted Solutions
cdinet
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 2 of 8

Re: ePO DB mdf size failed in PIA for upgrade 5.3.1. to 5.9.1

Jump to solution

Yes, you can shrink it as a temporary measure.  And yes, it might fail the upgrade if you don't have at least double, preferably triple the free space.  What you can do is after the upgrade, run the reindex script that is attached to KB67184.

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

View solution in original post

cdinet
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 4 of 8

Re: ePO DB mdf size failed in PIA for upgrade 5.3.1. to 5.9.1

Jump to solution

The KB I referenced recommends using target_percent of 10%.  Example:

DBCC SHRINKDATABASE (EPOdbName, 10); 

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

View solution in original post

cdinet
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 8 of 8

Re: ePO DB mdf size failed in PIA for upgrade 5.3.1. to 5.9.1

Jump to solution

Ok, good!  Glad to help

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

View solution in original post

7 Replies
cdinet
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 2 of 8

Re: ePO DB mdf size failed in PIA for upgrade 5.3.1. to 5.9.1

Jump to solution

Yes, you can shrink it as a temporary measure.  And yes, it might fail the upgrade if you don't have at least double, preferably triple the free space.  What you can do is after the upgrade, run the reindex script that is attached to KB67184.

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

View solution in original post

jmcleish
Reliable Contributor
Reliable Contributor
Report Inappropriate Content
Message 3 of 8

Re: ePO DB mdf size failed in PIA for upgrade 5.3.1. to 5.9.1

Jump to solution

OK thanks for this. 

could you recommend what command options to use- do i use truncateonly? target_size? etc 

Smiley Happy 

Thanks

 

cdinet
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 4 of 8

Re: ePO DB mdf size failed in PIA for upgrade 5.3.1. to 5.9.1

Jump to solution

The KB I referenced recommends using target_percent of 10%.  Example:

DBCC SHRINKDATABASE (EPOdbName, 10); 

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

View solution in original post

jmcleish
Reliable Contributor
Reliable Contributor
Report Inappropriate Content
Message 5 of 8

Re: ePO DB mdf size failed in PIA for upgrade 5.3.1. to 5.9.1

Jump to solution

thanks...though target_size in thatinstance would make the file 10MB. i think you are referencing the indexing?

cdinet
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 6 of 8

Re: ePO DB mdf size failed in PIA for upgrade 5.3.1. to 5.9.1

Jump to solution

Yes, the kb uses that for referencing indexing, but I would also use that for shrinking the database.  The dbcc shrinkdatabase command should use the target_percentage rather than size.

https://docs.microsoft.com/en-us/sql/t-sql/database-console-commands/dbcc-shrinkdatabase-transact-sq...

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

jmcleish
Reliable Contributor
Reliable Contributor
Report Inappropriate Content
Message 7 of 8

Re: ePO DB mdf size failed in PIA for upgrade 5.3.1. to 5.9.1

Jump to solution

ahh ok .. i understand.

thanks very much for your help. I'll test it on a clone first. 

cdinet
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 8 of 8

Re: ePO DB mdf size failed in PIA for upgrade 5.3.1. to 5.9.1

Jump to solution

Ok, good!  Glad to help

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

View solution in original post

You Deserve an Award
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.

Community Help Hub

    New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from McAfee experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by McAfee employees.
Join the Community
Join the Community