HI I am trying to create DB using dbinit command and getting SQL error (-85) -- Communication error. what could be the cause of this error. below is the output from the dbinit command SQL Anywhere Initialization Utility Version 12.0.1.3740 CHAR collation sequence: UTF8BIN(CaseSensitivity=Respect) CHAR character set encoding: UTF-8 NCHAR collation sequence: UCA(CaseSensitivity=UpperFirst;AccentSensitivity=Ignore;PunctuationSensitivity=Primary) NCHAR character set encoding: UTF-8 Creating system tables Creating system views Setting option values SQL error (-85) -- Communication error Regards |
What is you DBINIT command line?
AFAIK, the next (and only) message after "Setting option values" should be
so the communication error seems to appear rather late in the process.
Are you using a particular edition of SQL Anywhere (OEM)?
FWIW: In order to understand DBINIT's action - and possibly to check if DBINIT may interfere with some other database engine currently running on your box (which I don't expect) - confine John's answer from this FAQ.
This appears to be a result of the engine stopping during the creation of the database. It's not entirely clear why that would happen, of course. You can start an engine with
-n dbinit_engine
and then rundbinit
. It should use the engine you just started and you can watch for any assertion failures or other problems....and possibly add -o Console.log to the dbeng12 start line to store log messages in a file...
thanks all for your quick response.would like to add few more details as follows
version 12.0.1.3740 OS AIX 6
I started the server with dbsrv12 and run the following command to create a new DB
dbinit -b -dbs 1024m -c -k -t /log01/test.log -z UTF8BIN -zn UCA /data01/test.db
getting database not created message at the end of the execution
Have you tried to start the server with -o (and possibly with -z to log diagnostic communication messages)? What does that output reveal?
(I assume you have followed Phil's advice to expplicitly start a dbeng12/dbsrv12 local engine with the name dbinit_engine, and have checked that this engine is used by DBINIT...)
Another approach would be to
As John has stated in the cited FAQ, DBINIT inernally does just that (however tied to a database engine called dbinit_engine).