version 11.0.1.2440. Need approach that retains contents (several schemas with tables/views), db has checkpoint events. Current approach produced dbname.db file in backup directory, but when recovered from it the sybase central folder for tables and views were empty (very bad). Current cron/bkup solution uses following, what is it missing please (I also welcome links to 'detailed' documentation, exhausted sybase doc).
The In-memory config follows:
|
This solution does work as a backup to an -im c (checkpoint) database, the problem was simple, the full path to the encrypted_conn.txt was missing which produced a mytxn.db result that had a large byte size but was empty of schema data. For anyone who needs a in-memory db backup solution, the contents in original thread will work for you, just remember to fully qualify paths. Thank you to those that took the time to review. The reason you see an 'unload' solution to backup the database, it is because in-memory databases cannot use standard backup commands/solutions, as documented here:
In dev environment the unload produces a mydb.db that can recover db by copying the file to the database directory. But when unload is used in the prod envir and the resulting mydb.db file produced by the unload is copied to a failover server it is empty of the tables and views, etc. Can an unload be used on a database with connections be empty, and an unload used on a database not being used produce desired mydb.db with all the contents? Trying to figure out why unload works in dev IM but not in Prod IM. servers/db's are twins as well as the commands used for the unload. bkup sol needed. Maybe better to say a restore of prod IM db is needed. It can never be shutdown or connections stopped. A checkpoint event runs every 20 min. |
Can you elaborate more what you are trying to achieve, and what the problem is? As to your question's text, you seem to do a backup (which seems to give errors when started) whereas the script seems to do a database unload. That leaves me somewhat puzzled...
@Cindy: From your answer, I've learnt about the usage of UNLOAD as backup means for in-memory mode databases. Thanks for un-puzzling...:)