Siebel Remote : Data Extract parameter ClientDbTxnLog=True, can cause Database Initialization to fail.
Last updated on JULY 11, 2017
Applies to:Siebel Client Sync - Version 8.0  and later
Information in this document applies to any platform.
Customer reported an issue while initializing a local DB after a Database extract.
In this case, customer has an existing local Database on the client machine, but when they perform a synchronization after the new Database Extract for the same user, the Database Initialization starts and it fails.
On reviewing the upgwiz.log file, Initialization failed with Error message
"[Sybase][ODBC Driver][Adaptive Server Anywhere]Unable to start specified database: Can't use log file "C:\Siebel\8.1\Client_2\Local\sse_data_txn.log" since it has been used more recently than the database file"
Customer had inadvertently set the Database Extract Component definition parameter 'Client Database Transaction Log' (Alias : ClientDbTxnLog) = True
This influences the value of this parameter when it comes to running Database Extract jobs, even if the parameter ClientDbTxnLog = True is not explicitly set on the list of Database Extract job parameters. (The value will be taken from the Component definition)
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms