Kbase P90415: How to stop a probkup online process ?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
05/06/2006 |
|
Status: Verified
GOAL:
How to stop a probkup online from running ?
GOAL:
An on-line backup is already active. (1550)
GOAL:
Why is my online probkup taking longer than usual ?
FIX:
There are times when an online probkup needs to be stopped. These include (although not exclusively) times when a cron or batch job is running every so often to perform an online backup, and the previous instance of the online probkup has not completed. In these cases, the following error message will appear because only one on-line backup can be made at a time.
"An on-line backup is already active. (1550)"
If you can't stop the cron job and wait until the previous instance has finished, the following steps will interrupt the existing online probkup process:
1.) IF the probkup online (from the previous start) is still running, it will be listed in the usrctrl table:
$ promon dbname
Option 1. User Control
Option 1. Display all entries
then look for the "Usr" number that has a "BKUP" entry in the "Type" column.
2.) IF one exists, then you can stop the process by:
$ promon dbname
Option 8. Shut Down Database
Option 1. Disconnect a User
then enter the Usr number that you found with the "BKUP" entry in the "Type" column.
The log file will then show:
User (number) disconnect initiated
Backup cancelled disconnected by server (1726)
All subsequent proserve of the database will warn with the following error message until the next probkup session completes.
"The last backup was not completed successfully. (1553)"
3.) After this, investigations into why the online probkup is taking longer than it normally would. These include:
a) A large bi file - during online probkup, the bi file is included as well, it is time to truncate the bi file.
b) -aistall or -bistall parameters in the database startup script - resulting in a quiet point being raised by the Database Manager waiting for manual intervention by the Database Administrator.
c) Rapid Database growth - consider running incremental online probkups or increasing the interval between these instances.
d) Resource contention on the server.