Dbdefrag runs a long time

[eclidad]

Hi,

I've got some issues I'm curious about. I started a db cleanup process about 30 hours that is still running. It's doing a dbdefrag, dbfix, keybuild on all the databases. It's still in the process of doing a dbdefrag on astpsdat.000. In the meantime the backup ran last night and completed expect for one problem. It was "unable to begin the database backup." The two errors were E4116 and E3511. Is this something I would expect to happen if dbdefrag is running? I would hope that a datbase could handle something like this but I've been let down before. What happens if I interrupt the dbdefrag and restart it later? Is my database corrupt now? We are running R11.5 SP2.

I've done the dbdefrag, dbfix, keybuild before but never looked at the log file so I don't know if my database was included on the backup that night.

Thanks,
- Joel

 

[Cyklops]

Joel,

I guess the database size is over 5GB ? If so, forget the maintenance utilities, they indeed can run for days.

I know this is not much of a help but most of the times I use the 'quick and dirty' way of initializing the database.

In order to get a stable Database use MSSQL instead of the VLDB. Release 12 even comes with a MSSQL 2005 Express Edition.

regards

 

[eclidad]

Thanks for the response.

astpsdat.000 was/is about 1.6G and astpsdat.001 is about 1.1G. The first just finished after about 2 1/2 days. It's chugging away (pass 2) on astpsdat.001. The server is 3.2 GHz with 4Gb of ram. Not a high end machine but not a dog either. We are adding more servers to the network in a few weeks. At that point in time I'll move to MSSQL. We'll need to reinstall, add more windows clients, reconfigure the jobs, etc. I'll save all the work and do it in one shot. For now I'll let it run to completion just to see how long it takes to get there.

- Joel

 

[Cyklops]

Joel,

serverspecs are fine. This is just the way the database is designed. As David Michel states in another issue on these forums the VLDB database doesn't scale well. MSSQL server is much more stable and can grow over 35GB without issues.

regards