Start a copy of running sqlanywhere database
up vote
0
down vote
favorite
On our server we have a backup job that takes a backup of the running database and truncates the log-file. (Parameters: dbbackup -c "" -y -t -r -n path)
The backup is then copied off server and validated.
Often we want last nights backup up for checking something. But are unable to start the backup copy on the same server as the running database, because the transaction log-file is in use.
If we try to force it to start it without transaction log-file, it still tries to access the log-file.
dbsrv12 -f -n backup wisweb.db
Error message:
Starting database "backup" (/home/sybase/db_backup/wisweb.db) at Tue Nov 20 2018 13:49
Database recovery in progress
Last checkpoint at Tue Nov 20 2018 01:06
Checkpoint log...
Transaction log: /home/sybase/db/wisweb/wisweb.log...
Direct IO disabled for file '/home/sybase/db/wisweb/wisweb.log' because the file system on which it resides does not support it
Error: Cannot open transaction log file -- Resource temporarily unavailable
Cannot open transaction log file -- Resource temporarily unavailable
Database server shutdown due to startup error
Database server stopped at Tue Nov 20 2018 13:49
What SyBooks states for the -f switch (http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.help.sqlanywhere.12.0.1/dbadmin/da-dbserver.html)
"If there is no transaction log, the database server performs a checkpoint recovery of the database and then shuts down—it doesn't continue to run. You can then restart the database server without the -f option for normal operation.
If there is a transaction log in the same directory as the database, the database server performs a checkpoint recovery, and a recovery using the transaction log, and then shuts down—it doesn't continue to run. You can then restart the database server without the -f option for normal operation.
Specifying a cache size when starting the server can reduce recovery time."
It clearly tries to reach the transaction log on the original location. Tried with an empty file with the same name as the transaction log, but with the same result.
database sybase
asked Nov 20 at 12:59
Ove Halseth
12
add a comment |
up vote
0
down vote
favorite
On our server we have a backup job that takes a backup of the running database and truncates the log-file. (Parameters: dbbackup -c "" -y -t -r -n path)
The backup is then copied off server and validated.
Often we want last nights backup up for checking something. But are unable to start the backup copy on the same server as the running database, because the transaction log-file is in use.
If we try to force it to start it without transaction log-file, it still tries to access the log-file.
dbsrv12 -f -n backup wisweb.db
Error message:
Starting database "backup" (/home/sybase/db_backup/wisweb.db) at Tue Nov 20 2018 13:49
Database recovery in progress
Last checkpoint at Tue Nov 20 2018 01:06
Checkpoint log...
Transaction log: /home/sybase/db/wisweb/wisweb.log...
Direct IO disabled for file '/home/sybase/db/wisweb/wisweb.log' because the file system on which it resides does not support it
Error: Cannot open transaction log file -- Resource temporarily unavailable
Cannot open transaction log file -- Resource temporarily unavailable
Database server shutdown due to startup error
Database server stopped at Tue Nov 20 2018 13:49
What SyBooks states for the -f switch (http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.help.sqlanywhere.12.0.1/dbadmin/da-dbserver.html)
"If there is no transaction log, the database server performs a checkpoint recovery of the database and then shuts down—it doesn't continue to run. You can then restart the database server without the -f option for normal operation.
If there is a transaction log in the same directory as the database, the database server performs a checkpoint recovery, and a recovery using the transaction log, and then shuts down—it doesn't continue to run. You can then restart the database server without the -f option for normal operation.
Specifying a cache size when starting the server can reduce recovery time."
It clearly tries to reach the transaction log on the original location. Tried with an empty file with the same name as the transaction log, but with the same result.
database sybase
asked Nov 20 at 12:59
Ove Halseth
12
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
On our server we have a backup job that takes a backup of the running database and truncates the log-file. (Parameters: dbbackup -c "" -y -t -r -n path)
The backup is then copied off server and validated.
Often we want last nights backup up for checking something. But are unable to start the backup copy on the same server as the running database, because the transaction log-file is in use.
If we try to force it to start it without transaction log-file, it still tries to access the log-file.
dbsrv12 -f -n backup wisweb.db
Error message:
Starting database "backup" (/home/sybase/db_backup/wisweb.db) at Tue Nov 20 2018 13:49
Database recovery in progress
Last checkpoint at Tue Nov 20 2018 01:06
Checkpoint log...
Transaction log: /home/sybase/db/wisweb/wisweb.log...
Direct IO disabled for file '/home/sybase/db/wisweb/wisweb.log' because the file system on which it resides does not support it
Error: Cannot open transaction log file -- Resource temporarily unavailable
Cannot open transaction log file -- Resource temporarily unavailable
Database server shutdown due to startup error
Database server stopped at Tue Nov 20 2018 13:49
What SyBooks states for the -f switch (http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.help.sqlanywhere.12.0.1/dbadmin/da-dbserver.html)
"If there is no transaction log, the database server performs a checkpoint recovery of the database and then shuts down—it doesn't continue to run. You can then restart the database server without the -f option for normal operation.
If there is a transaction log in the same directory as the database, the database server performs a checkpoint recovery, and a recovery using the transaction log, and then shuts down—it doesn't continue to run. You can then restart the database server without the -f option for normal operation.
Specifying a cache size when starting the server can reduce recovery time."
It clearly tries to reach the transaction log on the original location. Tried with an empty file with the same name as the transaction log, but with the same result.
database sybase
asked Nov 20 at 12:59
Ove Halseth
12
On our server we have a backup job that takes a backup of the running database and truncates the log-file. (Parameters: dbbackup -c "" -y -t -r -n path)
The backup is then copied off server and validated.
Often we want last nights backup up for checking something. But are unable to start the backup copy on the same server as the running database, because the transaction log-file is in use.
If we try to force it to start it without transaction log-file, it still tries to access the log-file.
dbsrv12 -f -n backup wisweb.db
Error message:
Starting database "backup" (/home/sybase/db_backup/wisweb.db) at Tue Nov 20 2018 13:49
Database recovery in progress
Last checkpoint at Tue Nov 20 2018 01:06
Checkpoint log...
Transaction log: /home/sybase/db/wisweb/wisweb.log...
Direct IO disabled for file '/home/sybase/db/wisweb/wisweb.log' because the file system on which it resides does not support it
Error: Cannot open transaction log file -- Resource temporarily unavailable
Cannot open transaction log file -- Resource temporarily unavailable
Database server shutdown due to startup error
Database server stopped at Tue Nov 20 2018 13:49
What SyBooks states for the -f switch (http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.help.sqlanywhere.12.0.1/dbadmin/da-dbserver.html)
"If there is no transaction log, the database server performs a checkpoint recovery of the database and then shuts down—it doesn't continue to run. You can then restart the database server without the -f option for normal operation.
If there is a transaction log in the same directory as the database, the database server performs a checkpoint recovery, and a recovery using the transaction log, and then shuts down—it doesn't continue to run. You can then restart the database server without the -f option for normal operation.
Specifying a cache size when starting the server can reduce recovery time."
It clearly tries to reach the transaction log on the original location. Tried with an empty file with the same name as the transaction log, but with the same result.
database sybase
database sybase
asked Nov 20 at 12:59
Ove Halseth
12
asked Nov 20 at 12:59
Ove Halseth
12
asked Nov 20 at 12:59
Ove Halseth
12
asked Nov 20 at 12:59
Ove Halseth
12
asked Nov 20 at 12:59
Ove Halseth
12
12
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1376966%2fstart-a-copy-of-running-sqlanywhere-database%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
