The forum will be down for maintenance at some point between Friday, September 25, 2020 at 5pm PDT and Sunday, September 27, 2020 at 11:59 PDT. Downtime is unknown but will be minimized.

This is a question raised by @Sako in a comment on the following FAQ:

Is the option -ft mandatory? Since I am migrating from SQL10 to SQL17, and since DBLOG.EXE in SQL10 didnt support -ft option, then I don't know which value to assign this option.

Background: The description to Rebuilding databases involved in synchronization or replication (manual) tells that in step 3, the output of DBTRAN on the "old" database has to be noted, including the "timeline" value, to apply those values to the new database in step 8.

AFAIK, that value is only listed for v17 databases, both with DBTRAN and DBLOG, such as:

SQL Anywhere Log Translation Utility Version 17.0.10.6057
Transaction log "demo.log" starts at offset 0005206932
Current timeline GUID: 3d08c867-4f32-4113-886c-b232fb0280f5
Current timeline UTC creation time: 2018-09-03 07:23:53.210000+00:00
Current transaction log GUID: 00000000-0000-0000-0000-000000000000
 100% complete
Transaction log ends at offset 0005219754

However, DBTRAN and DBLOG (even the v17 utilities) do not list a timeline for v16 and older databases.

Does it mean specifying the "timeline" value can be omitted in step 8 when rebuilding pre-v17 databases?

asked 08 Jun, 05:41

Volker%20Barth's gravatar image

Volker Barth
36.7k343505761
accept rate: 34%

edited 08 Jun, 05:43


If a log supports timelines, v17 dblog/dbtran software will show the timeline info; otherwise, it will not. If the log format does not support timelines, you do not need to specify -ft.

Note that v16 also supported timelines (although it might only have been introduced in later version of v16).

permanent link

answered 08 Jun, 07:01

John%20Smirnios's gravatar image

John Smirnios
10.6k390138
accept rate: 38%

Hm, my 16.0.0.2798 databases don't show timelines...and those are using the latest build (and were created with 16.0.0.2546). But of course, your answer helps: If they don't show timelines, I do not need to specify those:)

(08 Jun, 09:04) Volker Barth
Replies hidden
1

Sorry. I looked deeper and timeline support was only enabled for IQ in the v16 code line, not SQLAnywhere.

(08 Jun, 09:51) John Smirnios
1

In my last test I ignored -ft while overtaking offsets from SQL10 in SQL17, and I have so far no problems

(09 Jun, 15:29) Baron
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • 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:

×173
×95
×48
×4

question asked: 08 Jun, 05:41

question was seen: 132 times

last updated: 09 Jun, 15:29