|
Standart installation of buisness objects.(Win2012) My sql.ini file is: [BI4] master=TCP,localhost,2638 query=TCP,localhost,2638 connection string: isql -U dba -P password -S BI4 -D BI4_CMS And error: Msg 911, Level 16, State 0:
SQL Anywhere Error -83: Specified database not found
CT-LIBRARY error:
ct_connect(): protocol specific layer: external error: The attempt to connect to the server failed.
what's my mistake? |
|
The following test worked OK when BI4_CMS was used as the -S server name for the ASE isql connection, instead of BI4, when using SQL Anywhere 16. C:\Sybase\ini\sql.ini [BI4_CMS] master=TCP,localhost,2638 query=TCP,localhost,2638 Start dbsrv16 and run ASE isql "%SQLANY16%\bin64\dbspawn.exe"^ -f "%SQLANY16%\bin64\dbsrv16.exe"^ -n BI4^ -o dbsrv16_log_BI4_CMS_Audit.txt^ -x tcpip(PORT=2638)^ BI4_CMS.db BI4_Audit.db "C:\Sybase\OCS-15_0\bin\isql.exe" -U dba -P sql -S BI4_CMS -D BI4_CMS Test worked OK... C:\projects\$templates\$SA_templates\run\isql_ASE>"C:\Sybase\OCS-15_0\bin\isql.e xe" -U dba -P sql -S BI4_CMS -D BI4_CMS 1> select @@version 2> go @@version ------------------------------------------------------------------------------- ------------------------------------------------- 16.0.0.2344 (1 row affected) 1> |
|
Please check the SQL Anywhere server to make sure the running server name is BI4 and the running database name is BI4_CMS. The following test worked OK for me: Using ASE isql.exe with SQL Anywhere via Open Connect / Open ServerStart SQL Anywhere 12 database with -x tcpip... "%SQLANY12%\bin64\dbspawn.exe"^ -f "%SQLANY12%\bin64\dbsrv12.exe"^ -n BI4^ -o dbsrv12_log_BI4_CMS.txt^ -x tcpip^ BI4_CMS.db Add section to C:\Sybase\ini\sql.ini... [BI4] master=TCP,localhost,2638 query=TCP,localhost,2638 Run ASE isql utility... "C:\Sybase\OCS-15_0\bin\isql.exe" -U dba -P sql -S BI4 -D BI4_CMS Result... C:\projects\$templates\$SA_templates\run\isql_ASE>"C:\Sybase\OCS-15_0\bin\isql.e xe" -U dba -P sql -S BI4 -D BI4_CMS 1> select @@version 2> go @@version ------------------------------------------------------------------------------- ------------------------------------------------- 12.0.1.4231 (1 row affected) 1> Common mistakes Spelling mistake in the server and/or database name, when starting the server, or connecting from isql, or in the sql.ini file; e.g., B14 instead of BI4. Coding error; e.g., colon instead of comma ahead of the port number in the sql.ini file. Thanx you! But this is my startup string: D:\Program Files (x86)\SAP BusinessObjects\sqlanywhere\bin64\dbsrv16.exe -n BI4 -x tcpip(PORT=2638;DoBroadcast=NO;BroadcastListener=NO) "D:\Program Files (x86)\SAP BusinessObjects\sqlanywhere\database\BI4_CMS.db" "D:\Program Files (x86)\SAP BusinessObjects\sqlanywhere\database\BI4_Audit.db" I tried other variants... and same errror.
(11 Aug '17, 10:11)
vantela
Replies hidden
1
I'd suggest that you remove the "DoBroadcast=NO;BroadcastListener=NO" from your -x tcpip option since this will cause the connection failure if the connection string (from isql) does not contain the "LINKS=TCPIP(BROADCAST=NO)" option and I suspect it does not do this!)
(15 Aug '17, 11:54)
Mark Culp
I tried -n BI4 -x tcpip(PORT=2638;DoBroadcast=YES;BroadcastListener=YES) "D:\Program Files (x86)\SAP BusinessObjects\sqlanywhere\database\BI4_CMS.db" "D:\Program Files (x86)\SAP BusinessObjects\sqlanywhere\database\BI4_Audit.db" -n BI4 -x tcpip "D:\Program Files (x86)\SAP BusinessObjects\sqlanywhere\database\BI4_CMS.db" "D:\Program Files (x86)\SAP BusinessObjects\sqlanywhere\database\BI4_Audit.db" -n BI4 -x tcpip(PORT=2638) "D:\Program Files (x86)\SAP BusinessObjects\sqlanywhere\database\BI4_CMS.db" "D:\Program Files (x86)\SAP BusinessObjects\sqlanywhere\database\BI4_Audit.db" And same error.
(16 Aug '17, 06:47)
vantela
1
Show us the entire command line for starting the server. Add the following option to the command line, and post the entire file showing the server startup: -o c:\temp\server_diagnostic.txt
(16 Aug '17, 08:55)
Breck Carter
I. 08/16 17:43:57. SQL Anywhere Network Server Version 16.0.0.2213 I. 08/16 17:43:57. OEM Edition, licensed only for use with OEM applications. I. 08/16 17:43:57. I. 08/16 17:43:57. Copyright © 2015 SAP SE or an SAP affiliate company. I. 08/16 17:43:57. All rights reserved. I. 08/16 17:43:57. Use of this software is governed by the Sybase License Agreement. I. 08/16 17:43:57. Refer to http://www.sybase.com/softwarelicenses. I. 08/16 17:43:57. I. 08/16 17:43:57. Connection limit (licensed seats): 100 I. 08/16 17:43:57. Processors detected: 4 I. 08/16 17:43:57. Maximum number of processors the server will use: 4 physical processor(s), 4 core(s) I. 08/16 17:43:57. This server is licensed to: I. 08/16 17:43:57. SAP I. 08/16 17:43:57. SAP IT I. 08/16 17:43:57. Running Windows 2012R2 Build 9600 on X86_64 I. 08/16 17:43:57. Server built for X86_64 processor architecture I. 08/16 17:43:57. 1343640K of memory used for caching I. 08/16 17:43:57. Minimum cache size: 18024K, maximum cache size: 60393880K I. 08/16 17:43:57. Using a maximum page size of 8192 bytes I. 08/16 17:43:57. Multiprogramming level: minimum:4, current:20, maximum:80 I. 08/16 17:43:57. Automatic tuning of multiprogramming level is enabled I. 08/16 17:43:57. Starting database "BI4_CMS" (D:\Program Files (x86)\SAP BusinessObjects\sqlanywhere\database\BI4_CMS.db) at Wed Aug 16 2017 17:43 I. 08/16 17:43:57. Starting database "BI4_Audit" (D:\Program Files (x86)\SAP BusinessObjects\sqlanywhere\database\BI4_Audit.db) at Wed Aug 16 2017 17:43 I. 08/16 17:43:57. Performance warning: Database file "D:\Program Files (x86)\SAP BusinessObjects\sqlanywhere\database\BI4_CMS.db" consists of 6 disk fragments I. 08/16 17:43:57. Performance warning: Database file "D:\Program Files (x86)\SAP BusinessObjects\sqlanywhere\database\BI4_Audit.db" consists of 4 disk fragments I. 08/16 17:43:57. Transaction log: BI4_Audit.log I. 08/16 17:43:57. Transaction log: BI4_CMS.log I. 08/16 17:43:58. Starting checkpoint of "BI4_CMS" (BI4_CMS.db) at Wed Aug 16 2017 17:43 I. 08/16 17:43:58. Starting checkpoint of "BI4_Audit" (BI4_Audit.db) at Wed Aug 16 2017 17:43 I. 08/16 17:43:58. Finished checkpoint of "BI4_CMS" (BI4_CMS.db) at Wed Aug 16 2017 17:43 I. 08/16 17:43:58. Finished checkpoint of "BI4_Audit" (BI4_Audit.db) at Wed Aug 16 2017 17:43 I. 08/16 17:43:58. Database "BI4_CMS" (BI4_CMS.db) started at Wed Aug 16 2017 17:43 I. 08/16 17:43:58. Database "BI4_Audit" (BI4_Audit.db) started at Wed Aug 16 2017 17:43 I. 08/16 17:43:58. Database server started at Wed Aug 16 2017 17:43 I. 08/16 17:43:58. Trying to start SharedMemory link ... I. 08/16 17:43:58. SharedMemory link started successfully I. 08/16 17:43:58. Trying to start TCPIP link ... I. 08/16 17:43:58. Starting on port 2638 I. 08/16 17:44:03. TCPIP link started successfully I. 08/16 17:44:03. Now accepting requests I. 08/16 17:45:00. Starting checkpoint of "BI4_Audit" (BI4_Audit.db) at Wed Aug 16 2017 17:45 I. 08/16 17:45:00. Starting checkpoint of "BI4_CMS" (BI4_CMS.db) at Wed Aug 16 2017 17:45 I. 08/16 17:45:00. Finished checkpoint of "BI4_Audit" (BI4_Audit.db) at Wed Aug 16 2017 17:45 E. 08/16 17:45:00. Handler for event 'ScheduledLogBackup' caused SQLSTATE '08W46' E. 08/16 17:45:00. Error during backup/restore: Could not create directory "F:\Backup\incremental\BI4_Audit"-- No such file or directory I. 08/16 17:45:00. Finished checkpoint of "BI4_CMS" (BI4_CMS.db) at Wed Aug 16 2017 17:45 E. 08/16 17:45:00. Handler for event 'ScheduledLogBackup' caused SQLSTATE '08W46' E. 08/16 17:45:00. Error during backup/restore: Could not create directory "F:\Backup\incremental\BI4_CMS"-- No such file or directory
(16 Aug '17, 10:52)
vantela
Replies hidden
Comment Text Removed
Comment Text Removed
Note that you have two failing backup events... E. 08/16 17:45:00. Handler for event 'ScheduledLogBackup' caused SQLSTATE '08W46' E. 08/16 17:45:00. Error during backup/restore: Could not create directory "F:\Backup\incremental\BI4_Audit"-- No such file or directory E. 08/16 17:45:00. Handler for event 'ScheduledLogBackup' caused SQLSTATE '08W46' E. 08/16 17:45:00. Error during backup/restore: Could not create directory "F:\Backup\incremental\BI4_CMS"-- No such file or directory
(17 Aug '17, 05:30)
Breck Carter
|
Try using the dbisql utility that ships with SQL Anywhere. For example:
No... I have worked dbisql.exe.
I need isql. For integration with DataProtector
AFAIK, there's no isql utility to connect with SQL Anywhere.
I don't use BI but here's a howto setup SQL Anywhere 12.0 with BI 4.1:
Using SQL Anywhere for a CMS and Auditing Database with BI 4.1
You should be able to use the isql utility from ASE to connect to a SQL Anywhere 12 database... I've seen it done, and I've done it myself, but I just can't remember how :)
I believe it has to do with using Open Client (ct_connect etcetera), and there is a whole chapter in the Help: Using SQL Anywhere as an Open Server
I am guessing (hoping) it is a simple problem with the -S -D parameters, but maybe it is deeper; e.g., maybe dbsrv12.exe wasn't started with -x tcpip since Open Client requires TCPIP.
Update: I got this message when the port number was missing:
C:\projects\$templates\$SA_templates\run\isql_ASE>"C:\Sybase\OCS-15_0\bin\isql.e xe" -U dba -P sql -S ddd12 -D ddd12 CT-LIBRARY error: ct_connect(): directory service layer: internal directory control layer error: Requested server name not found.With the port number (49158 in the case of my running copy of dbsrv12.exe), I got a different message, indicating that the connection process actually found the server:
C:\projects\$templates\$SA_templates\run\isql_ASE>"C:\Sybase\OCS-15_0\bin\isql.e xe" -U dba -P sql -S ddd12:49158 -D ddd12 CT-LIBRARY error: ct_connect(): network packet layer: internal net library error: Protocol driver call to parse connection information failed C:\projects\$templates\$SA_templates\run\isql_ASE>PAUSE Press any key to continue . . .I then fiddled around with dsedit, but the dsedit ping gave the same parse error, plus "information has invalid syntax".
Maybe you will have better luck.