Can you clarify which logs? I do not see a pronto.log under the BPPM directory structure, can you confirm which BPPM version you are using? The storm_hostname.log is the default name for the database log for BPPM. Can you provide more specifics regarding the files and the changes?
So, you're saying that pronto.log which is located in the sybase subdirectory (e.g. /usr/pw/sybase) has been renamed to storm_hostname.log?
Just want to clarify the above, since there is a legitimately named storm_hostname.log file located in /usr/pw/asatmp.
If the first sentence is true, you might start the investigation by looking in /usr/pw/pronto/bin/pw.pl
These lines look like they are involved
(line 5175 for my installation)
I'd also like to know:
2) TSIM version (pw viewhistory)
Apologies for the delay, and the lack of info in the original post.
BPPM 9.6 on Windows 2008.
Both systems have 'pronto' in the pw.pl file.
Working system has:
Non-working system has:
It's a weird one.
I spoke to one our DBAs regarding this issue - are the file sizes 0, or blank files? There is a way to customize the file name in Sybase, but it should not affect the dbarchive. We would recommend opening a Support ticket to work with us directory to attempt to rename the files and check on the archive failure.
Sorry for the delay in responding.
The file size ends up as zero but I seem to remember seeing it increase in size .
In the interim, I found an old Knowledge Article (I actually found a print out of it with my handwriting in the back of a folder at the back of a cupboard!):
According to point 6:
6. Replace the ProactiveNet Server Database data file, "storm_HOSTNAME.db" (\pw\sybase\), and transaction log, "pronto.log" (\pw\sybase\), with the Unloaded/Rebuilt copies (\pw\dbrebuild\).
NOTE: The Unloaded/Rebuilt transaction log, "storm_HOSTNAME.log" (\pw\sybase\), will have the same base-named as the ProactiveNet Server Database data file, "storm_HOSTNAME.db" (\pw\sybase\).
I think my problem may be that the database has been rebuilt in the past and it has retained the storm_HOSTNAME.log name.
I'll get a case logged and see what we can find out.
2 of 2 people found this helpful
I received your case today. I've tested here, and the procedure in the KB Article is indeed the cause of the Sybase db not using the correct transaction log (pronto.log) afterwards. I've submitted a correction to the KB article so that it includes the dblog.exe syntax for changing the newly created database file to use the correct transaction log (it is set within the DB itself, not within a BPPM script/config file):
8. After the rebuild, the new storm_HOSTNAME.db file will not be using the correct transaction log file name (pronto.log), it will instead be set to use a transaction log named "storm_HOSTNAME.log". This needs to be changed back to "pronto.log", otherwise the scheduled database archives will not properly backup the correct transaction log file name. To correct this, use the dblog(.exe) CLI to set the transaction log for the database:
>dblog.exe ..\storm_HOSTNAME.db -t pronto.log
SQL Anywhere Transaction Log Utility Version 220.127.116.112
"..\storm_HOSTNAME.db" was using log file "storm_HOSTNAME.log"
"..\storm_HOSTNAME.db" is using no log mirror file
"..\storm_HOSTNAME.db" is now using log file "pronto.log"
Transaction log starting offset is 0140198054
Transaction log current relative offset is 0000348047