Hi there,
We run some scripts every 15 minutes to perform after imaging on our main database and roll forward on a hot standby on another server in a seperate location.
We use Progress 9.1D (soon to be upgraded) on a Windows Server 2003 platform. The databases are auto started by a batch file every morning at 4am and the script that performs ai runs straight after.
Yesterday we had a situation whereby the script atempted to perform the extent list at exactly 04:00:13 which was the same time to the second that the db started. As such the extent list failed and subsequently our script errrored.
Is it likely that doing this at the time the DB started would cause a conflict and not allow the extent list? We have been able to run an extent list when the DB has not started before i.e. extent list at 04:00:05 and db started at 04:00:13 and this works fine.
Any thoughts would be much appreciated.
Thanks,
Matt
We run some scripts every 15 minutes to perform after imaging on our main database and roll forward on a hot standby on another server in a seperate location.
We use Progress 9.1D (soon to be upgraded) on a Windows Server 2003 platform. The databases are auto started by a batch file every morning at 4am and the script that performs ai runs straight after.
Yesterday we had a situation whereby the script atempted to perform the extent list at exactly 04:00:13 which was the same time to the second that the db started. As such the extent list failed and subsequently our script errrored.
Is it likely that doing this at the time the DB started would cause a conflict and not allow the extent list? We have been able to run an extent list when the DB has not started before i.e. extent list at 04:00:05 and db started at 04:00:13 and this works fine.
Any thoughts would be much appreciated.
Thanks,
Matt