Unable to start database server on Intel Imac

#11

Quote:

If you've generated a reload.sql file on the PowerPC Mac,
you can apply it to the new database from the command
line using something like 'dbisqlc -c "uid=<uid
;pwd=<pwd>" reload.sql', assuming the database is already
running.

I tried to reproduce your problem with running dbinit from
the command line on a Mac OS X 10.4.10 machine, and I
couldn't. I wonder if dbspawn works for you (e.g.,
"dbspawn dbeng10 mydb.db"). If this fails but you can
start the database directly and connect to it, it would
suggest something in the auto-starting gear is
malfunctioning.

Judging from the hostname in the trace you've posted, am I
correct in assuming that you are running SQL Anywhere on
one of the machines in the Mac labs at UW? Are those
machines locked down in any way, or do you have full
access to everything?

It might be worthwhile to check the system log to see if
anything interesting was logged at the time of the
failure. You can do this by running Console.app (in
/Applications/Utilities), clicking on the "Logs" button
in the toolbar, and checking in the system.log and
console.log files.

Ray

Thanks for your help Ray. I actually stopped into iAnywhere
in Waterloo and got
a server copy (non developers) of SQLAnywhere10.0.1 and
installed it on my machine and everything works. Naturally
I removed all occurances of the developers version of
SQLAynwhere10 before rebuilding the database. Managed
to build a database, got into interactiveSQL and rebuilt
with the old commands and
data.
Again thank you very much for all your assistance.

Quote:

wasabi wrote:
Your being unable to run dbinit from the command line
is >> definitely curious.

Could you provide me with some information about your
configuration? What version of Mac OS X are you
running?
We are running Mac OS X 10.4.1

Are you running the Developer Edition of SQL Anywhere,
the >> Evaluation Edition, or the full version?

We are running the Developer Edition

Did you use the GUI installer ("Install SQL
Anywhere.app") >> or the command line installer (the
setup script) to >> install SQL Anywhere? If you used the
command line >> installer, what installation directory did
you choose?
I used the Gui Installer and it installed SQLAnywhere10
in the /Applications directory

One thing to try is to start an engine with the command
line options "-z -n dbinit_engine" in one terminal
window >> and then try running dbinit from another
terminal window. >> Does the engine's console show
connection attempts from >> dbinit?

Wow. I just tried this and got the following:
from the dbeng10 screen:
Starting database "utility_db" (utility_db) at Thu Oct
25 2007 10:29
Database "utility_db" (utility_db) started at Thu Oct 25
2007 10:29
Connection ID 1: "DBA" connected to database
"utility_db" from SQL Anywhere 10.0.1 (3419) client over
SharedMemory Connection ID 1: AppInfo is
IP=129.97.51.165;HOST=imac001.student.cs.uwaterloo .ca
;OS='Darwin 8.10.1
i386';PID=0x348;THREAD=0xa000d000;VERSION=10.0.1.3 419
;API=DBLIB; TIMEZONEADJUSTMENT=-240
Connection ID 1: Server character set conversion is
enabled, but not required
using character set "ISO_8859-1:1987"
Starting database "a_dbinit" (/tmp/mydb.db) at Thu Oct
25 2007 10:29
Transaction log: mydb.log
Starting checkpoint of "a_dbinit" (mydb.db) at Thu Oct
25 2007 10:29
Finished checkpoint of "a_dbinit" (mydb.db) at Thu Oct
25 2007 10:29
Database "a_dbinit" (mydb.db) started at Thu Oct 25 2007
10:29
Starting checkpoint of "a_dbinit" (mydb.db) at Thu Oct
25 2007 10:29
Finished checkpoint of "a_dbinit" (mydb.db) at Thu Oct
25 2007 10:29
Database "a_dbinit" (mydb.db) stopped at Thu Oct 25 2007
10:29
Connection ID 1: "DBA" disconnected from database
"utility_db"
Database "utility_db" (utility_db) stopped at Thu Oct 25
2007 10:29

From the dbinit screen:
SQL Anywhere Initialization Utility Version 10.0.1.3419
CHAR collation sequence:
ISO1LATIN1(CaseSensitivity=Ignore) CHAR character set
encoding: ISO_8859-1:1987 NCHAR collation sequence:
UCA(CaseSensitivity=Ignore;AccentSensitivity=Ignor e
;PunctuationSensitivity=Primary) NCHAR character set
encoding: UTF-8 Creating system tables
Creating system views
Setting option values
Database "/tmp/mydb.db" created successfully

and we see:
-r--r--r-- 1 root wheel 2076672 Oct 25 10:29
/tmp/mydb.db

So it created mydb.db
And in dblauncher I get:
2 logical processor(s) on 1 physical processor(s)
detected. This server is licensed to:
Developer Edition
Restricted Use
Running Darwin 8.10.1 Darwin Kernel Version 8.10.1: Wed
May 23 16:33:00 PDT 2007;
root:xnu-792.22.5~1/RELEASE_I386 on X86
Server built for X86 processor architecture
8192K of memory used for caching
Minimum cache size: 8192K, maximum cache size: 940032K
Using a maximum page size of 4096 bytes
Starting database "mydb"
(/Applications/SQLAnywhere10/mydb.db) at Thu Oct 25 2007
10:52
Transaction log: mydb.log
Starting checkpoint of "mydb" (mydb.db) at Thu Oct 25
2007 10:52
Finished checkpoint of "mydb" (mydb.db) at Thu Oct 25
2007 10:52
Database "mydb" (mydb.db) started at Thu Oct 25 2007
10:52 Database server started at Thu Oct 25 2007 10:52
Trying to start SharedMemory link ...
SharedMemory link started successfully
Trying to start TDS (TCPIP) link ...
Unable to start on default port; starting on port 49152
instead
TDS (TCPIP) link started successfully
Now accepting requests

So which command line interface do I use to rebuild the
database. I have the
unloaded data directory from the SQLAnywhere 9 database?

wasabi wrote:
Are you running the Developer Edition? Currently, a
limitation of the Developer Edition on Mac OS X is
that >> it is impossible to auto-start an engine from
the >>>> Administration Tools, which is what Sybase
Central will >>>> attempt to do when you try to create an
engine. You can >>>> get around this by pre-starting an
engine from the >>>> command line or from DBLauncher and
giving it the >> engine >> name 'dbinit_engine' (e.g.,
'dbeng10 -n >> dbinit_engine'). >> Sybase Central will
then connect to >> this engine and will >> be able to
create a new database. >>>> Alternatively, you can create
a database from the >> command >> line by dbinit, e.g.,
'dbinit mydb.db'. >> Running 'dbinit >> -?' will display
the command line >> options dbinit accepts. >> These
options are also >>> documented in our documentation.
Thank you Ray for the suggestion. Just a note - in
order to get a list of the
available options the command is 'dbinit -h' and not
'dbinit -?' Unfortunately
I just tried 'dbinit mydb.db' to see if it would work
and I still could not start
the server. This is what I got:
dbinit /tmp/mydb.db
SQL Anywhere Inistialization Utility Version
10.0.1.3419 SQL error (-80) -- Unable to start
database server Database "/tmp/mydb.db" not created

I also tried the 'dbeng10 -n dbinit_engine' . This
started fine. However, your
suggestion that Sybase Central will connect to this
server made no difference.
I still got the SQL error (-80).

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Unable to start database server on Intel Imac

sybase.public.sqlanywhere.general sybase.public.sqlanywhere.general

Re: Unable to start database server on Intel Imac - 10-29-2007 , 10:14 AM