on 03-16-2011 12:39 AM
Good night, I would ask if it is normal that the process of check data structure in a MaxDB database of 220 GB more than 12 hours later to finish?
what function does this job?
Thank you very much
> Good night, I would ask if it is normal that the process of check data structure in a MaxDB database of 220 GB more than 12 hours later to finish?
This heavily depends
- on the number of volumes you have (parallelism)
- on the speed of the I/O subsystem
> what function does this job?
it's like doing
dbmcli -U c db_execute check data
see also
Note 940420 - FAQ: Database structure check (VERIFY)
Markus
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
> I'm running too in a 20GB database, its at 30 minutes, there is a way to estimate this time? having the number of volumes and the speed of the I/O subsystem?
You could probably estimate by having
- the maximum number of 8 kB random I/O throughput (contact your storage system vendor)
- latencies (in ms)
- number of disks and distribution of them
We have a 3 TB+ database and we're unable to run a verify on the production system due to the time it takes and the load it puts on the system (it takes up to 8 days). We do those checks on a copy of the production system once in a while.
Markus
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.