Database restoration error in sql2k: Use the with move option to identify the valid location of the file and internal consistency error. Contact the technical support staff for assistance.

Sql2k was successfully installed, and an error occurred during restoration. It was preliminarily determined that it was a path problem and the solution was found online. an error is reported during the backup process. If an internal consistency error occurs, contact the technical support staff for assistance.

The following are the search results to solve the problem.

 

An error occurred while restoring the database in MySQL 2 K: Use the with move option to identify the valid location of the file.

The error is as follows:
Device activation error. The physical file name c: \ Program Files \ st2008 \ sxt. MDF may be incorrect.
The sxt_dat file cannot be restored to c: \ Program Files \ st2008 \ sxt. MDF. Use the with move option to indicate the valid location of the file.
Device activation error. The physical file name c: \ Program Files \ st2008 \ sxt. LDF may be incorrect.
The sxt_log file cannot be restored to c: \ Program Files \ st2008 \ sxt. LDF. Use the with move option to indicate the valid location of the file.

Solution:
-- View database file names

-Execute the following statement in the query analyzer to solve the problem.
Restore database name
From disk = 'C: \ A. Bak' -- c: \ A. Bak is the backup file name
With move 'sxt _ dat 'to 'C: \ sxt. MDF' -- Restore sxt_dat to the file c: \ sxt. MDF.
, Move 'sxt _ log' to 'C: \ sxt. ldf' -- Restore sxt_log to the file c: \ sxt. LDF.

Force restore with "with Replace ".

 

 

2. If an internal consistency error occurs, contact the technical support staff for assistance.

 

Problems found on the Internet may be:

1. No patch is installed. (For example, SQL Server 2000 SP4 ).
2. Insufficient disk space.
3. the backup file is not a full backup.
4. Try to use forced restoration.
5. The database logic name is incorrect.

 

Install patches and check disk space,

Some Historical SQL databases occupy a large disk space, so the logs are cleared first:Dump transaction database name with no_log
Again: Enterprise Manager -- Right-click the database you want to compress -- all tasks -- contract database -- contract file -- Select log file -- select to contract to xxm in the contract mode, here we will provide a minimum number of M that can be reduced. Enter this number directly and click OK.
Times: If you want to prevent it from increasing in the future, choose Enterprise Manager> Server> database> Properties> transaction log> Restrict File growth to 2 MB.

The statement is still incorrect.Restore verifyonly from disk = 'f: \ soft \ jd_pat'

Error:

Server: Message 3242, level 16, status 2, Row 1
The file of the device 'f: \ soft \ jd_pat 'is not a valid Microsoft tape format backup set.
Server: Message 3013, level 16, status 1, Row 1
The Verify database operation is terminated abnormally.

It turns out that the backup file is incorrect. It's depressing for a long time.

 

Summary

 

Database learning is divided into development and management.

All the problems encountered today belong to the management aspect. These problems are mainly caused by experience. I will take notes frequently in the future.