Logo 
Search:

MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

InvalidDatabaseSchema on PreUpgradeCheck

  Asked By: Tracey    Date: Mar 15    Category: MOSS    Views: 3489

I've been playing around with the upgrade process from MOSS 2007 to MSS 2010,
just to familiarize myself with the process, and I discovered something that
anyone else interested in upgrade would find useful to know.

One of the earliest steps, as many of you know, is to run PreUpgradeCheck, added
to the set of STSADM operations with 2007 Service Pack 2. PreUpgradeCheck
examines the farm for many things, one of which is altered database schemas. As
everyone on this list should know, changing the database schema for SharePoint
DBs is a strict no-no. But for the first time, the upgrade path from 2007 to
2010 will actually fail if changes have been made.

I've known since my early days of working with SP2003 that touching the database
was verboten, so I was very surprised to see that, when I ran PreUpgradeCheck on
my own farm, that this portion of the screening process failed. Upon looking
through the log files (see 12Hive\Logs\PreUpgradeCheck-YYYYMMDD-#####-####.log
and search for "InvalidDatabaseSchema" for more details), I saw the following:

[DatabaseSchema] [ERROR] [12/15/2009 11:19:25 AM]:
[MyContentDB_site].[CatBucketInfo] EXTRA Table
[DatabaseSchema] [ERROR] [12/15/2009 11:19:25 AM]: [MyContentDB_site].[CatDef]
EXTRA Table
[DatabaseSchema] [ERROR] [12/15/2009 11:19:25 AM]: [MyContentDB_site].[CatGroup]
EXTRA Table
[DatabaseSchema] [ERROR] [12/15/2009 11:19:25 AM]: [MyContentDB_site].[CatJoint]
EXTRA Table
[DatabaseSchema] [ERROR] [12/15/2009 11:19:25 AM]:
[MyContentDB_site].[CatKeyword] EXTRA Table
[DatabaseSchema] [ERROR] [12/15/2009 11:19:25 AM]:
[MyContentDB_site].[CatOrgleList] EXTRA Table
[DatabaseSchema] [ERROR] [12/15/2009 11:19:25 AM]: [MyContentDB_site].[CatPath]
EXTRA Table
[DatabaseSchema] [ERROR] [12/15/2009 11:19:25 AM]:
[MyContentDB_site].[CatPredefined] EXTRA Table
[DatabaseSchema] [ERROR] [12/15/2009 11:19:25 AM]:
[MyContentDB_site].[PortalPerm] EXTRA Table
[DatabaseSchema] [ERROR] [12/15/2009 11:19:25 AM]:
[MyContentDB_site].[PortalPermDelta] EXTRA Table
[DatabaseSchema] [ERROR] [12/15/2009 11:19:25 AM]:
[MyContentDB_site].[PortalPermInfo] EXTRA Table
[DatabaseSchema] [ERROR] [12/15/2009 11:19:25 AM]:
[MyContentDB_site].[PortalProperties] EXTRA Table
[DatabaseSchema] [ERROR] [12/15/2009 11:19:25 AM]:
[MyContentDB_site].[PortalSchemaVersion] EXTRA Table
[DatabaseSchema] [ERROR] [12/15/2009 11:19:25 AM]:
[MyContentDB_site].[SearchScopeEntities] EXTRA Table
[DatabaseSchema] [ERROR] [12/15/2009 11:19:25 AM]:
[MyContentDB_site].[SearchScopes] EXTRA Table
[DatabaseSchema] [ERROR] [12/15/2009 11:19:25 AM]: [MyContentDB_site].[Slots]
EXTRA Table

What is unique about this particular content DB was that it was originally
created in SPS 2003 and later upgraded via a content DB attach to MOSS 2007. So
I compared this database schema to some other examples that I've worked with of
the following:

* Existing SPS 2003 content databases

* Other content databases upgraded from SPS 2003 to MOSS 2007

* Content databases created by MOSS 2007

Sure enough, I found that the offending tables existed in the first two
categories (those created by SPS 2003), but not in the last category. It seems
that the upgrade process from 2003 to 2007 simply didn't completely clean up the
older tables.

Microsoft may already be aware of this, and perhaps they will correct it as they
go from beta to RTM, or with a hot fix to Service Pack 2. But for now, my
resolution is to (YIKES) delete the old tables from my content DBs and try
again.

Share: 

 

2 Answers Found

 
Answer #1    Answered By: Katelynn Donovan     Answered On: Mar 15

I agree that you aren't supposed to touch the database normally, but in this
case I think your action is exactly what you want and need to do. I'm
pretty sure that all of those tables are for features that were deprecated
when SharePoint moved from 2003 to 2007. Now that you will be moving from
2007 to 2010 old 2003 tables that 2007 never used should be flagged and
deleted.

 
Answer #2    Answered By: Geraldine Slater     Answered On: Mar 15

I also received the 'InvalidDatabaseSchema' when running the preupgradecheck for
2010. I have a case open with Microsoft.

Here's the options MSFT gave us (I know your case is more unique than ours):

1) Revert your content databases to a point in time where the schema
modifications were not made.
2) Use STSADM to backup your farm, and use STSADM to restore it into a new
content database (which did resolve our issue -- unfortunately, it also took 88
hours).
3) *They would not assist with this, but it was an option*: Use a schema
comparison tool and compare your current schema with a default installed one. If
you go this route, I HIGHLY recommend making a copy of your db and comparing
against that.

We opted for #3, and found that someone had indexed two tables (AllDocs and
AllUserData) which caused the schema check to fail. As we all know, also a huge
no-no. We dropped the two indexes, and were back into a supported configuration.

 
Didn't find what you were looking for? Find more on InvalidDatabaseSchema on PreUpgradeCheck Or get search suggestion and latest updates.