read_only filegroup

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2005 » Data Corruption » read_only filegroup

read_only filegroup

Rate Topic

Display Mode

Topic Options

Author

Message

deepforest

Posted Thursday, February 09, 2012 8:25 AM

Valued Member

Group: General Forum Members
Last Login: Yesterday @ 11:11 AM
Points: 69, Visits: 392

Hi,
I have a filegroup which is set to read-only. I need to set it back to read-write. When I try to modify it, it errors out with: 'An error occurred while processing 'AltFile' metadata for database...'
After looking at sys.master_files, the filegroup has all redo_xxxx_lsn values set. The redo_start_lsn and redo_target_lsn is the same values, so theoretically, the filegroup is ok, but it still prevents me from changing the read-only mode.
Any thoughts?
Thanks.

Post #1249750

GilaMonster

Posted Thursday, February 09, 2012 8:32 AM

SSC-Dedicated

Group: General Forum Members
Last Login: Today @ 2:48 AM
Points: 37,635, Visits: 29,886

Anything in the error log?

Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1249759

deepforest

Posted Thursday, February 09, 2012 9:09 AM

Valued Member

Group: General Forum Members
Last Login: Yesterday @ 11:11 AM
Points: 69, Visits: 392

Nothing suspicious, but obviously it happened during some past restore. I'm trying to find some older full backup and restore the FG and see if it's ok. But still, I'd like to figure out how this happened in first place.

Post #1249780

prettsons

Posted Tuesday, March 06, 2012 3:09 AM

SSC Journeyman

Group: General Forum Members
Last Login: 2 days ago @ 12:17 AM
Points: 99, Visits: 1,023

If you have already check that filegroup is ok then there is one another possibility-
Did you check that read-only filegroup is on a compressed ntfs volume? If the volume is compressed, first you have to decompress it & after that try it again.

SQL Database Recovery Expert Smile

Post #1262024

deepforest

Posted Tuesday, March 06, 2012 6:10 AM

Valued Member

Group: General Forum Members
Last Login: Yesterday @ 11:11 AM
Points: 69, Visits: 392

No it's not compressed. It was completely different issue. The particular FG was pointing to a non-existing file. I talked to MS and the solution they came up with was to keep adding filegroups until the non-existing file record is overwritten. It worked.

Post #1262122

Paul Duffett

Posted Wednesday, May 30, 2012 8:58 AM

SSC Veteran

Group: General Forum Members
Last Login: Wednesday, January 30, 2013 10:39 AM
Points: 244, Visits: 210

Hi,

I just wanted to add something to this topic as I had the same error but the fix was slightly different, although adding files to the database was the key.

The error I received was:

An error occurred while processing 'AltFile' metadata for database id 8, file id 3, and transaction='alterdb'.

Upon reviewing the sys.sysfiles for the database (id=8) it was obvious that there was no fileid=3. There was a 1, 2, 4, 5, 6 but no 3.

There were two filegroups: PRIMARY had 1 file, with a fileid=1, and the SECONDARY had three files, fileid=4,5 & 6.

I suspect there was a second file in the PRIMARY filegroup at some stage with a fileid=3 which was removed, thus leaving a hole in the sequence.

The solution was to add a file to the PRIMARY filegroup, confirm that the file was created with a fileid=3 and re-run the ALTER DATABASE command, this time it worked fine.

Just wanted to share that with the community.

Thanks
Paul

Post #1308416

« Prev Topic | Next Topic »

Permissions