|
I'm trying to connect to a database and run a script using For example: dbisql -nogui -c "uid=dba;pwd=sql" results in: ((not connected) whereas if I write: dbisql -c "uid=dba;pwd=sql" an Interactive SQL window opens as connected. What I'd really like to is call Notes:
Update: According to the docs, the following command should work against the default database although Links property is missing: dbisql -c "UID=DBA;PWD=sql" -onerror exit mycom.sql However, I get the message "You are not connected to a database". On the other hand, I can connect to the same database smoothly via Interactive SQL window (choosing 'connect to a running database on this computer'). Is there anything else I'm missing? Screenshots: Dbsrv12:
Dbping & Dbisql:
Dbisql window (works ok):
|
|
-c Should be a complete connections string. Probably you should add links=shmem to. In my batch files i don't use the -nogui paramater. And I'm not getting a normal window when I run the batchfile Changed Thomas's comment to answer so henginy may accept it.
(24 Sep '12, 08:08)
Reimer Pods
Thank you for the answer. First time I tried, it worked with links attribute added. But later, I don't have a single idea how, it didn't work. I keep getting 'You are not connected to a database' message even if I add links (and also server attribute). Please see the update.
(24 Sep '12, 08:11)
henginy
Replies hidden
I would certainly add the path to the DBSIQL call in order to prevent to call the wrong version. The environment variables are handy here, such as
Are you having a SQLCONNECT environment variable that might "secretly" add stuff to your connection string? FWIW I still usually use the dbisqlc tool for batch stuff...
(24 Sep '12, 08:25)
Volker Barth
@Volker Barth: Yes, I'm also setting another variable to shorten the script: I like dbisqlc too, but am afraid to use it in case it is discontinued..(don't know if there's really such a risk, but..)
(24 Sep '12, 08:34)
henginy
Replies hidden
Have you tried if using dbisqlc raises the same problem?
(24 Sep '12, 09:51)
Volker Barth
I've tried it now and it works OK, no problem connecting to database. Only a few trivial warnings about spatial data options. It does the job and I might stick to it all right, but I wonder why
(24 Sep '12, 09:55)
henginy
Replies hidden
I'd try to use the LOG connection parameter within the connection string to get more debug output on the connection attempts...
(24 Sep '12, 10:00)
Volker Barth
Good pointer. The command
(24 Sep '12, 10:17)
henginy
Replies hidden
Btw,
(24 Sep '12, 10:22)
henginy
Does the server console contain any info that a connect attempt is tried (dbeng12 -z ...)?
(24 Sep '12, 11:08)
Volker Barth
Sorry, reformatted the output - (done now): Command: C:\Program Files\SQL Anywhere 12\Bin32>dbisql -c "uid=dba;pwd=sql;LINKS=SharedMemory;Log=C:\salog.txt" Server console: Connection ID 1: "dba" connected to database "asusys" from SQL Anywhere 12.0.1 (3769) client over SharedMemory Connection ID 1: AppInfo is IP=x.x.x.x;HOST=xxx;OSUSER=xxx;OS='Windows XP Build 2600 Service Pack 3';EXE='C:\Program Files\SQL Anywhere 12\Bin32\dbisql.exe';PID=0xdb0;THREAD=0xed8;VERSION=12.0.1.3769;API=iAnywhereJDBC;TIMEZONEADJUS Connection ID 1: Server character set conversion is enabled, but not required using character set "windows-1254" Command: C:\Program Files\SQL Anywhere 12\Bin32>dbisql -c "uid=dba;pwd=sql;LINKS=SharedMemory;Log=C:\salog.txt" test.sql You are not connected to a database. Server console: => No new lines appended to console.
(24 Sep '12, 11:22)
henginy
Other info: Workgroup Edition, Turkish OS.
(24 Sep '12, 11:28)
henginy
Still strange. May this be an encoding problem (I-dot etc.)? - If so, I'm no expert anyway:(
(24 Sep '12, 11:49)
Volker Barth
If you want to test if the behaviour is caused by an encoding problem, you can switch the encoding of your command prompt using the chcp command. Example: chcp 850 chcp 1252
(24 Sep '12, 11:54)
Dan Cummins
Thank you Volker, you've been very helpful and shown good ways to debug.
(25 Sep '12, 03:23)
henginy
Unfortunately no progress with codepages 850 and 1252 either.
(25 Sep '12, 03:23)
henginy
How can I open a technical case for this issue?
(25 Sep '12, 03:24)
henginy
AFAIK, you can use "Case Express" to report a bug or open a case: http://case-express.sybase.com/cx/ (Your current support plan may play a role here, apparently...)
(25 Sep '12, 06:07)
Volker Barth
Thanks. I'll check our plan.
(25 Sep '12, 06:41)
henginy
More comments hidden
|
|
This is a long shot, but from your screen snap it looks as though you may have endashes (long dashes) on the command line instead of ASCII dashes. I can see how you could get the non-ASCII dash if you cut-and-paste the command line from the docs on Windows. You might want to try typing it in with regular dashes and see if you still have a problem? I actually typed in the commands every time, no copy-paste. The dashes on the screen must the same as this: '-' (next to Backspace on my keyboard:). Thank you.
(24 Sep '12, 09:42)
henginy
|
|
You will see this behaviour when running dbisql.exe from a Windows command prompt. For .bat file you should run with dbisql.com which is created for that purpose. Reference: http://dcx.sybase.com/index.html#1201/en/dbadmin/dbisql-interactive-dbutilities.html HTH . . . "For Windows, there are two executables:" "1.Batch scripts should call dbisql or dbisql.com, not dbisql.exe. The dbisql.com executable is linked as a console application. " "2.The dbisql.exe executable is linked as a windowed application and does not block the command shell from which it was started. If dbisql.exe is run from a batch file, you won't see any output sent to the standard output or standard error files. " Well, AFAIK, if you don't specify a file extension, .com will have higher precedence than .exe (and the doc seem to cope with that), so Henginy - who does not use an extension - should already use dbisql.com, right?
(02 Jan '13, 15:48)
Volker Barth
|
Thank you, you're correct in both cases. Most of the time I used the Server property but forgot about Links. Also no need for nogui parameters. I suppose I accidentally used SA9 exes in some tests. Anyway, please post your comment as answer so I can accept it.
Hm, it might not be over yet, updating the question.