cancel
Showing results for 
Search instead for 
Did you mean: 

I'm trying to remove an existing database from BI4_CMS.db. Any thoughts about this error?

Former Member
0 Kudos

I'm trying to remove an existing database from BI4_CMS.db. Any thoughts about this error?

former_member182948
Active Participant
0 Kudos

Transaction Log utility(dblog) is a command line tool.
At a command prompt, using the dblog command.

Please see below.
http://dcx.sap.com/index.html#1201/en/dbadmin/dblog.html

Accepted Solutions (0)

Answers (3)

Answers (3)

denis_konovalov
Active Contributor
0 Kudos

What are you trying to achieve exactly ?

"trying to remove an existing database from BI4_CMS.db" - what does that mean ?

chris_keating
Advisor
Advisor
0 Kudos

He meant to say that he wants to stop using the transaction log.

denis_konovalov
Active Contributor
0 Kudos

but why ?
SQL Anywhere DB that comes with BOE install is provided as is. For the single purpose to be CMS DB holder.
There shouldn't be any mods to it.

former_member186998
Contributor
0 Kudos

Hi Vin,

I have something I'd like you to try.
You can copy a command with "Copy to Clipboard" button of the Wizard.

dblog "D:\Program Files (x86)\SAP BusinessObjects\sqlanywhere\database\BI4_CMS.db"

You can execute this command that you copied on Command Prompt.
Do you get the same error message?

Thanks,
Atsushi

Former Member
0 Kudos

Hi again.

I have recreated the same issue using a different environment. someone know where is the sybase log file to see this issue.

Thanks.

chris_keating
Advisor
Advisor
0 Kudos

As Atsushi noted, try running the command from a command prompt. This should give you a better description of the reason for the error.

I reproduced the behavior and when I ran the command, this is what was reported:

SQL Anywhere Transaction Log Utility Version 16.0.0.2546
Database quit abnormally last time it was used. Database recovery must be performed before proceeding.

Please post the error that you encounter if you are not sure what it means or what is needed to correct it. In my case, I simply needed to start the database to allow for the automatic recovery at start up.