Problem: GBAK is taking too long and I need to have access to my database. Solution: REMEMBER: GBAK does not need exclusive access to a database to run but, you must realize that the backup created will only contain the records or the state of the database (a snapshot) at the time the GBAK was started. As well, remember that when running GBAK on a live database you may see some performance loss. If you want GBAK to run as fast as possible you might want to consider using the switches -g(arbage collection), -ig(nore checksums), -l(imbo transactions). You should understand the consequences of using these options before doing so. If you want to try to clean up the database as much as you can without running a GBAK and restore you can take the following steps. 1) gfix -sweep (uncommitted transactions will not be swept) 2) alter indexinactive repeat for each index understanding that you must have exclusive access to the index. 3) alter index active repeat this process for each index that you want to rebuild. NOTE: GBAK is the best way to clean up a database. It is the only way to garbage collect all the back record versions and restore it to disk in an unfragmented fashion. Provided you do not use the -i(nactive) switch upon restore, GBAK will re-create all of your indexes as well.
Last Modified: 02-OCT-00