LOAD TRAN with HEADERONLY output changes in ASE 16.0 SP02

[neal_stack2]

Hello,

Prior to ASE 16.0 SP02, our product parsed the output of the "LOAD DATABASE … WITH HEADERONLY" statement for the sequence dates to help order the transaction logs. For example:

sequence dates: (old=Sep 27 2016  8:57:54:580PM, new=Sep 27 2016  8:58:04:540PM);

With ASE 16.0 SP02, the "WITH HEADERONLY" output changed and no longer shows the seconds & milliseconds:

,       Dump date: Sep 27 2016  1:45PM
        Database page size:  2048.
,       Database page size:  2048.
,       First log page: 7668323
        Checkpoint RID: (7668323, 21)
,       Previous begin RID: (7668323, 9)
        Sequence dates:
,               Old date: Sep 27 2016  1:45PM
                New date: Sep 27 2016  1:45PM

We have a customer with a production database that dumps multiple transaction logs in a minute when it is under very heavy load.

Is there a way to change the output for the sequence dates back to include seconds & milliseconds so that we can load the files in the correct order?

Thanks,

Neal

[neal_stack2]

Hi Mark,

Thanks for the suggestion. I think our engineering team chose note to rely on the dump file name because users can override it with their own values:

1> dump database pubs2 to "/export/home/sybase/dump/pubs2.full.9_28:08:53" with file='pubs2666660E100'
2> go

1> load database pubs2 from "/export/home/sybase/dump/pubs2.full.9_28:08:53" with HEADERONLY
2> go
Backup Server session id is: 112. Use this value when executing the 'sp_volchanged' system stored procedure after fulfilling any volume change request from the Backup Server.
Backup Server: 6.28.1.1: Dumpfile name 'pubs2666660E100  ' ...

And I don't think we can entirely rely on the "Create date & time:" to establish a complete timeline of all the transaction logs. For example, if there were three transaction logs and we only knew the creation time for each one, it would be hard to know if we missed the middle one. Having the precise old and new sequence dates allowed us to properly order the transaction logs.

[dan_thrall · Accepted solution]

Hi Neal,

In 16.0 SP02, the headeronly output was modified to have a more user friendly display of data.  With it came the unintentional loss of time precision of seconds and milliseconds.

This will be restored in upcoming 16.0 SP02PL05 via CR 800569.

There's no workaround for headeronly display.

HTH

Dan

[neal_stack2 · Accepted solution]

Thanks Dan! Is there an estimated ship date for ASE 16.0 SP02 PL05?

We will have to adjust our date parsing logic to match the format in the newer version.

[dan_thrall · Accepted solution]

Hi Neal,

Current ETA for SP02PL05 is penciled in for end of year 2016, subject to change.

Dan