|
Hi As a result of running Schema Analysis > Run in SQL Central, I tried to move the database log file (Hades.log) to another volume as suggested. I use this command /Applications/SQLAnywhere17/System/bin64/dblog -t "/Volumes//SQLAnywhere17Logs/Hades.log" "/Applications/SQLAnywhere17/databases/Hades.db" I get these lines in the terminal: SQL Anywhere Transaction Log Utility Version 17.0.4.2129 "/Applications/SQLAnywhere17/databases/Hades.db" was using log file "Hades.log" "/Applications/SQLAnywhere17/databases/Hades.db" is using no log mirror file But when I start the database, the log file is still created at the place where the db file is located. Any hint why it's not putting the log file to the specified volume? And can I be sure that if the database log file is still at the same location, the database is in he same state as before running the command, i. e. nothing has changed? SQL Anywhere 17.0.4.2129 macOS El Capitan Java 1.8.0_151 TIA, Robert |
Please be aware that the content in SAP SQL Anywhere Forum will be migrated to the SAP Community in June and this forum will be retired.
Follow this question
By Email:Once you sign in you will be able to subscribe for any updates here
By RSS:Markdown Basics
- *italic* or _italic_
- **bold** or __bold__
- link:[text](http://url.com/ "title")
- image?
- numbered list: 1. Foo 2. Bar
- to add a line break simply add two spaces to where you would like the new line to be.
- basic HTML tags are also supported
Question tags:
question asked: 10 Jan '18, 12:57
question was seen: 1,318 times
last updated: 16 Jan '18, 09:39
I would expect the output of dblog to include a line:
"Hades.db" is now using log file "<new log="" file="">"
If it does not, the log location will remain unchanged.
The command line you posted looks correct so I am not sure why it is not changing the log location.
Perhaps the double forward slashes are causing a problem: // in "/Volumes//SQLAnywhere17Logs/Hades.log"
Hi Chris
Thanks for your answer. Good to know there should be a line like "Hades.db" is now using log file <xy>. And no, there is no such line presented when executing the mentioned command. I also can't think of a sensible reason why it is behaving like this. I also could not find a log entry in the console related to this.
Thanks for looking so clearly to my code! This double quotes are accidentally there, the command should of course be with only a single forward slash. I tried it with the correct command:
But the result is the same. No change of the log file.
By the way, going it in SQL Central, I get the quite generic error message as seen in the attached screen shot.
Sorry, I can't upload a file (the screenshot). I get following error:
Strange. I checked on Windows, specifying a non-existing path for the log file issues a warning but does change the log location... So I don't know why you do not get a note about the new log usage here...
I just tested this on a new 17.0.4.2129 install on OS X El Capitan.
I tested with a newly created demo database (newdemo.sh) and
dblog -t "/users/home/newlog.log" "/Applications/SQLAnywhere17/samples/demo.db"
The log was successfully redirected to the supplied location.
This may be another issue that will require additional hands on investigation. Do you have support?
Thanks for testing on Windows, Volker. I also don't know why it does not work, unfortunately. The blog command seems to be correct in the second attempt. But still no change of log location.
Thanks for testing. I have tried it on exact the same SQ Anywhere and macOS version (10.11.6). I have support for Windows, but not macOS yet.
Sorry for the delay but I just saw this now. I will fix the "send_template_email" problem but the only reason it would get called when uploading a file is if the file was found to contain a virus. This could certainly be a false positive, and I just updated the virus scanner file just to be sure.