Hi,
My clients progress (10.2B) database has a bi image approaching 1.5GB. The limit is 2GB. The database extent that has grown is It is a before image file [database name].b2. I am debating whether I should just prostrct add a few new extents or just truncate the bi file. The problem I have is Access to the live system is limited, because the company work until late and start early. They are not quiet 24 hour, but they are close . So if I brought the database down, I'd have to force all the users out of the system for a spell.
I had considered just adding extra bi extents. Looking at the progress knowledge base, they recommend backing up the database first. This makes sense, because you are changing the database. The problem with this is, this would probably take 1 hour to do, so I'd rather avoid if I can.
I know I can truncate the bi file. If I can do this without having to backup the database this might be a faster option. If I could stop the database truncate the bi file this would give me enough time to add more extents at a more opportune time, e.g. the weekend .
I am just wondering if I do need to backup the database before truncating, would anyone know? I have had a look online and I don't see any mention this should be done first. I would assume given I'm not changing the database structure that this is not necessary. Does anyone know if this assumption is correct. Any advice would be appreciated.
My clients progress (10.2B) database has a bi image approaching 1.5GB. The limit is 2GB. The database extent that has grown is It is a before image file [database name].b2. I am debating whether I should just prostrct add a few new extents or just truncate the bi file. The problem I have is Access to the live system is limited, because the company work until late and start early. They are not quiet 24 hour, but they are close . So if I brought the database down, I'd have to force all the users out of the system for a spell.
I had considered just adding extra bi extents. Looking at the progress knowledge base, they recommend backing up the database first. This makes sense, because you are changing the database. The problem with this is, this would probably take 1 hour to do, so I'd rather avoid if I can.
I know I can truncate the bi file. If I can do this without having to backup the database this might be a faster option. If I could stop the database truncate the bi file this would give me enough time to add more extents at a more opportune time, e.g. the weekend .
I am just wondering if I do need to backup the database before truncating, would anyone know? I have had a look online and I don't see any mention this should be done first. I would assume given I'm not changing the database structure that this is not necessary. Does anyone know if this assumption is correct. Any advice would be appreciated.