ron
Member
I have a package system that sits on 7 databases. (2PC is NOT used. I know the implications of that - and I'm trying to sort it out with the package vendor.)
We're using Progress 8.3E on Solaris - and we're getting ready to move to 9.1D within the next two months.
I'm testing a new AI system to extract AI files from a Production system about hourly - and then apply the AI files to a copy DB on a Disaster Site system.
I tested the new AI system without PROQUIET ... to get all the basics working properly.
Now I've introduced PROQUIET and I'm in trouble.
This is the logic I've used (error checking etc removed for clarity):
for db in $DBLIST
do
$PROQUIET $db -C enable
done
for db in $DBLIST
do
$RFUTIL $db -C aimage extent new
done
for db in $DBLIST
do
$PROQUIET $db -C disable
done
My intention was to get ALL seven databases in a quiet state at the same time -- and then swap AI extents. That way I can be sure that at the time the AI files are swapped ... all seven databases are at the same point (ie, they're synchronised).
But I find that when I do the PROQUIET enable ... it automatically swaps to the next AI file! I've looked at the Progress manuals - and I can not see that annoying behaviour mentioned anywhere.
Furthermore - it is obvious that Progress did not intend proquiet to be used in this way - because when a DB is "quiet" an attempt to swap AI files will "hang" - waiting for "quiet" to be removed.
Of course the problem is immediately solved if the 7 databases are coalesced into one - but I do not have direct control over that.
Can anyone help me?
We're using Progress 8.3E on Solaris - and we're getting ready to move to 9.1D within the next two months.
I'm testing a new AI system to extract AI files from a Production system about hourly - and then apply the AI files to a copy DB on a Disaster Site system.
I tested the new AI system without PROQUIET ... to get all the basics working properly.
Now I've introduced PROQUIET and I'm in trouble.
This is the logic I've used (error checking etc removed for clarity):
for db in $DBLIST
do
$PROQUIET $db -C enable
done
for db in $DBLIST
do
$RFUTIL $db -C aimage extent new
done
for db in $DBLIST
do
$PROQUIET $db -C disable
done
My intention was to get ALL seven databases in a quiet state at the same time -- and then swap AI extents. That way I can be sure that at the time the AI files are swapped ... all seven databases are at the same point (ie, they're synchronised).
But I find that when I do the PROQUIET enable ... it automatically swaps to the next AI file! I've looked at the Progress manuals - and I can not see that annoying behaviour mentioned anywhere.
Furthermore - it is obvious that Progress did not intend proquiet to be used in this way - because when a DB is "quiet" an attempt to swap AI files will "hang" - waiting for "quiet" to be removed.
Of course the problem is immediately solved if the 7 databases are coalesced into one - but I do not have direct control over that.
Can anyone help me?