Last weekend my HFF failed and no Micros.
I determined my Micros partition had failed so had to depend on a backup "Consolidated Database Base" file (CDB).
As luck would have it, my Sybase would not uncompress this consolidate/compressed file because Micros updates and hotfixes left the Sybase utilities out of sync. My local POS provider was able to uncompress my CDB file to a DB file and I have recovered my database data and I brought my system back online.
Now my new problem.....I can not run the file RUNBACKUP.EXE anymore without errors. I have traced this to a problem with my new uncompress DB (previously the CDB file). As I scope this new database file I notice it is pointing to a log file from my old CDB file (example: D:\Micros\Database\Data\Backup\micros_2010_06_03_02_31.log as opposed to D:\Micros\Database\Data\micros.log.
So...if this makes sense to anybody.....how do I get my DB file to stop using the wrong log file and go back to the default log file in the D:\Micros\Database\Data directory.
Thank you.
I determined my Micros partition had failed so had to depend on a backup "Consolidated Database Base" file (CDB).
As luck would have it, my Sybase would not uncompress this consolidate/compressed file because Micros updates and hotfixes left the Sybase utilities out of sync. My local POS provider was able to uncompress my CDB file to a DB file and I have recovered my database data and I brought my system back online.
Now my new problem.....I can not run the file RUNBACKUP.EXE anymore without errors. I have traced this to a problem with my new uncompress DB (previously the CDB file). As I scope this new database file I notice it is pointing to a log file from my old CDB file (example: D:\Micros\Database\Data\Backup\micros_2010_06_03_02_31.log as opposed to D:\Micros\Database\Data\micros.log.
So...if this makes sense to anybody.....how do I get my DB file to stop using the wrong log file and go back to the default log file in the D:\Micros\Database\Data directory.
Thank you.