Default Database name of sybase SQL Anywhere in SAP BO

Hello team
What is the default database name of sybase SQL Anywhere in SAP BO.Thanks in advance.
Regards
Ankit Jain

Hi Ankit,
The Sybase SQL Anywhere is default CMS and Audit database in BI 4.1. It is called as Sybase SQL Anywhere. Please refer page number 23 from below document for more information.
https://websmp105.sap-ag.de/~sapidb/011000358700000372212014E/sbo41sp4_sp_update_en.pdf
Regards,
Hrishikesh

Similar Messages

Reading data from Sybase SQL Anywhere 7 database to write into a SQL Server database

Hi,
I need to import data from a Sybase SQL Anywhere vers. 7 database. This RDBMS was used more 10-12 years ago. I want to write Sybase data into a SQL Server 2008 R2-2012 database. For testing purposes I'm using SQL Server 2005.
After that I've installed Sybase SQL Anywhere vers. 7 I can use the Adaptive Anywhere 7.0 ODBC. I'd like to use SSIS to import Sybase data, but I cannot create an OLE DB connection in a right manner while I can create and ODBC connection manager and so I
can use an Execute SQL task (and not a data flow task, unfortunately!).
Well, after using this Execute SQL task to read fe a table with thousands of data rows how can I write the entire data collection on a SQL Server table?
Thanks

Below link may be helpful,
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/184c937a-2b2c-4e59-b4d7-e8d3d1b476b3/net-provider-for-oledb-sybase-adaptive-server-anywhere-ole-db-provider-90-cant-be-located-when?forum=sqlintegrationservices
http://supun-biz.blogspot.in/2010/11/extracting-data-from-sybase-sql.html
Regards, RSingh

Support for Sybase SQL Anywhere databases

Is there support for Sybase SQL Anywhere databases available?
Specifically, using an ODBC connection.
Sybase, curiously enough, does not want to develop specific drivers for connection to its databases; instead, it relies on an outside source (ODBC) for its connection.
I am NOT in favour of using ODBC as an connection method; we have bench-marked SQL query performance using both native driver connection vs ODBC connection; you should be easily able to guess which approach won out!!
Hint: Oracle dramatically!!

You can try using JTDS, it should work with Sysbase too and if you take a look at the SQL Developer certifications, you can see it's the certified way of speaking with Sysbase.
I've never used this myself and i'm not even sure if this works with SQL Anywhere but it's worth a try.

ODBC Gateway on Linux error - connects ok with Sybase SQL Anywhere

OS: CentOS 5.8 64-bit
DB: Oracle XE 11gR1 64-bit
Gateway: Oracle Gateway for ODBC 64-bit
Database and gateway reside on same Linux Server.
Connecting to remote Sybase SQL Anywhere 10 server on WindowsXP.
Using SQL Anywhere 11 odbc driver and unixODBC driver manager on Linux server.
isql tool connects without any problems.
One LISTENER, service for db and gateway on same port.
===================================
Via SQL*Plus, the following error occurs....
SQL> select * from dual@dblink;
select * from dual@dblink
ERROR at line 1:
ORA-28513: internal error in heterogeneous remote agent
ORA-02063: preceding line from dblink
===================================
sqlnet.ora
# sqlnet.ora Network Configuration File: /u01/app/oracle/product/11.2.0/xe/network/admin/sqlnet.ora
# Generated by Oracle configuration tools.
NAMES.DIRECTORY_PATH=(TNSNAMES)
ADR_BASE = /u01/app/oracle/product/11.2.0/xe
==================================
tnsnames.ora
# tnsnames.ora Network Configuration File:
XE =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = mysystem)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = XE)
dblink =
(DESCRIPTION =
(ADDRESS =
(PROTOCOL = TCP)(HOST = mysystem)(PORT = 1521)
(CONNECT_DATA =
(SID = dblink))
(HS=OK))
EXTPROC_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC_FOR_XE))
(CONNECT_DATA =
(SID = PLSExtProc)
(PRESENTATION = RO)
=======================
listener.ora
# listener.ora Network Configuration File:
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = /u01/app/oracle/product/11.2.0/xe)
(PROGRAM = extproc)
(SID_DESC =
(SID_NAME = dblink)
(ORACLE_HOME = /u01/app/oracle/product/11.2.0/gtw)
(PROGRAM = dg4odbc)
(ENVS=LD_LIBRARY_PATH=/opt/sqlanywhere11/lib64:/u01/app/oracle/product/11.2.0/gtw/lib)
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC_FOR_XE))
(ADDRESS = (PROTOCOL = TCP)(HOST = mysystem)(PORT = 1521))
DEFAULT_SERVICE_LISTENER = (XE)
========================
initdblink.ora
# This is a sample agent init file that contains the HS parameters that are
# needed for the Database Gateway for ODBC
# HS init parameters
HS_FDS_CONNECT_INFO=dblink
HS_FDS_SHAREABLE_NAME=/usr/lib64/libodbc.so
HS_FDS_TRACE_LEVEL=255
HS_LANGUAGE=american_america.we8iso8859p1
HS_NLS_NCHAR=UTF-8
# ODBC specific environment variables
set ODBCINI=/etc/odbc.ini
========================
Oracle Corporation --- MONDAY OCT 15 2012 17:23:39.915
Heterogeneous Agent Release
11.2.0.1.0
Oracle Corporation --- MONDAY OCT 15 2012 17:23:39.914
Version 11.2.0.1.0
Entered hgogprd
HOSGIP for "HS_FDS_TRACE_LEVEL" returned "255"
Entered hgosdip
setting HS_OPEN_CURSORS to default of 50
setting HS_FDS_RECOVERY_ACCOUNT to default of "RECOVER"
setting HS_FDS_RECOVERY_PWD to default value
setting HS_FDS_TRANSACTION_LOG to default of HS_TRANSACTION_LOG
setting HS_IDLE_TIMEOUT to default of 0
setting HS_FDS_TRANSACTION_ISOLATION to default of "READ_COMMITTED"
HOSGIP returned value of "UTF-8" for HS_NLS_NCHAR
setting HS_FDS_TIMESTAMP_MAPPING to default of "DATE"
setting HS_FDS_DATE_MAPPING to default of "DATE"
setting HS_RPC_FETCH_REBLOCKING to default of "ON"
setting HS_FDS_FETCH_ROWS to default of "100"
setting HS_FDS_RESULTSET_SUPPORT to default of "FALSE"
setting HS_FDS_RSET_RETURN_ROWCOUNT to default of "FALSE"
setting HS_FDS_PROC_IS_FUNC to default of "FALSE"
setting HS_FDS_CHARACTER_SEMANTICS to default of "FALSE"
setting HS_FDS_MAP_NCHAR to default of "TRUE"
setting HS_NLS_DATE_FORMAT to default of "YYYY-MM-DD HH24:MI:SS"
setting HS_FDS_REPORT_REAL_AS_DOUBLE to default of "FALSE"
setting HS_LONG_PIECE_TRANSFER_SIZE to default of "65536"
setting HS_SQL_HANDLE_STMT_REUSE to default of "FALSE"
setting HS_FDS_QUERY_DRIVER to default of "TRUE"
setting HS_FDS_SUPPORT_STATISTICS to default of "FALSE"
Parameter HS_FDS_QUOTE_IDENTIFIER is not set
setting HS_KEEP_REMOTE_COLUMN_SIZE to default of "OFF"
setting HS_FDS_GRAPHIC_TO_MBCS to default of "FALSE"
setting HS_FDS_MBCS_TO_GRAPHIC to default of "FALSE"
Default value of 64 assumed for HS_FDS_SQLLEN_INTERPRETATION
setting HS_CALL_NAME_ISP to "gtw$:SQLTables;gtw$:SQLColumns;gtw$:SQLPrimaryKeys;gtw$:SQLForeignKeys;gtw$:SQLProcedures;gtw$:SQLStatistics;gtw$:SQLGetInfo"
setting HS_FDS_DELAYED_OPEN to default of "TRUE"
setting HS_FDS_WORKAROUNDS to default of "0"
Exiting hgosdip, rc=0
ORACLE_SID is "dblink"
Product-Info:
Port Rls/Upd:1/0 PrdStat:0
Agent:Oracle Database Gateway for ODBC
Facility:hsa
Class:ODBC, ClassVsn:11.2.0.1.0_0008, Instance:dblink
Exiting hgogprd, rc=0
hostmstr: 0: HOA After hoagprd
Invalid HS_NLS_NCHAR value UTF-8 specified
Setting HS_NLS_NCHAR to Server Default 2000
Invalid HS_NLS_NCHAR value UTF-8 specified
Setting HS_NLS_NCHAR to Server Default 2000
hostmstr: 0: HOA Before hoainit
Entered hgoinit
HOCXU_COMP_CSET=1
HOCXU_DRV_CSET=31
HOCXU_DRV_NCHAR=2000
HOCXU_DB_CSET=873
HOCXU_SEM_VER=112000
Exiting hgoinit, rc=28513
hostmstr: 0: HOA After hoainit
RPC Calling nscontrol(0), rc=0
hostmstr: 0: RPC Before Exit Agent
hostmstr: 0: HOA Before hoaexit
Entered hgoexit
HS Gateway: NULL connection context at exit
Exiting hgoexit, rc=0 with error ptr FILE:hgoexit.c LINE:108 FUNCTION:hgoexit() ID:Connection context
hostmstr: 0: HOA After hoaexit
hostmstr: 0: RPC After Exit Agent
=============================
Also, does anyone know how to determine the location (full path) of the unixODBC driver manager ?
Please assist if you can...thx.
Edited by: user601798 on Oct 15, 2012 3:37 PM

Let me start with the unixODBC driver:
There's no generic location as it depends which package you've used to install the UnixODBC driver manager or how you compiled it from scratch. I commonly prefer to compile it from scratch as this offers me to install it to any location I like.
If you're not sure where it is located, you could perform a search on your machine looking for libodbc.so. Then cross check it with "file <location>/libodbc.so" to see the lib is a 64bit library.
So let's assume in the /usr/lib64 you found the libodbc.so library, then the setting
HS_FDS_SHAREABLE_NAME=/usr/lib64/libodbc.so
is correct. Else you need to adopt the parameter.
Next step is to check out which unixODBC version is installed. That's commonly done by calling "odbcinst -j".
Looking now ta the gateway init file there's a parameter HS_NLS_NCHAR set to UTF-8. UnixODBC is commonly compiled with UCS2 support, so please change it to HS_NLS_NCHAR=UCS2
Could you also please post the content of the odbc.ini file "more /etc/odbc.ini"?
Thanks,
Klaus

Problems with JConnect, Sybase SQL Anywhere 5.x

Hi
I use Sybase SQL Anywhere 5.x, Apache Server, Apache Jserver.(WINNT)
I must to write servlet, which connects to Sybase database using JConnect.
When database is on the same host as Apache server, and my servlet i run services:
Open Server Gateway (dbos50.exe <server_name>), where server_name in sql.ini is
"master=NLWNSCK,x.x.x.x,8001" (x.x.x.x is my IP)
Standalone Engine (dbeng50.exe <path to the database>)
And all is ok
But I don't known, what to do, when my database is on other host, neither my servlet(aplication and JConnect)
Which services I must run on Host, where database is?
Which services I must run on Host, where JConnect and servlet(aplication) are?
Must I use Cascade Gateway or TDS tunneling?
Can you help me?
Thanks.

Hi,
I need to connect to Sybase SQL Anywhere version 5.5.05, too, but I can't find the driver to connect to the server, could u tell me about this? Please share it with if available.
thanks.

How to db connect from SAP to SYBASE SQL anywhere 16 remotely

Hi All,
May i know can i connect to SYBASE SQL Anywhere16 from SAP running on kernel 7.42 via dbacockpit (dbco)?
I've followed note 1737415 - Sybase IQ: Enable remote/secondary connect to SAP Sybase IQ & 1532253 - SYB: Remote DB Monitoring for SAP Sybase ASE
but failed.
Where can i find the dbsl and its client for sybase sql anywhere? I only can find SAP ASE and SAP IQ on SMP. Is those compatible with SQL anywhere 16?
Thanks.
Nicholas

Hi Jason,
the error message is it complains minimun version for SAP IQ is 15.6, however our SQL anywhere is on version 16, above the support version as per note1737415 - Sybase IQ: Enable remote/secondary connect to SAP Sybase IQ
fyi, i'm using the latest sybase dbsl and SAPIQ 16 client.
Any idea or will it works to remotely connect SQL anywhere via dbacockpit?
Thanks,
Nicholas.

Sybase SQL Anywhere 12 and SAP Sybase SQL Anywhere 16

Hello,
Is there a difference between Sybase SQL Anywhere 12 and SAP Sybase SQL Anywhere 16?
If there is, could you please list out the general information. i.e. is v12 (i.e. pre SAP purchase of Sybase) just older than v16 (i.e. post SAP purchase of Sybase) ?
I know that Hyland's OnBase 14 supports both of these versions. Just having a difficult time trying to find information about Sybase SQLA v12 - if it is even still available for purchase, etc.
Any information would be appreciated.
Thank you,
Christian Jones

SAP Sybase SQL Anywhere 16 is the next major version of SQL Anywhere after SQL Anywhere 12.
The following documentation link DocCommentXchange will include information about the changes made for v16. For information specific to v12, see DocCommentXchange which has links for both v12.0.0 and v12.0.1 documentation as I suspect that most of the marketing materials would be focused on v16.
Both v12 and v16 are available for sale. Here is a link SAP SQL Anywhere v16.0 | SAP Online Store
where you will purchase v12 and v16 software (look at the sidebar for the v12 links).

Inconsistent behaviour of Sybase SQL anywhere update column trigger

Hi, all
I am not sure where to post this issue, since I could not find a forum for Sybase SQL anywhere.
The problem is as follows:
The definition of the update column trigger in help is this:
UPDATE OF column-list
Invokes the trigger whenever a row of the associated table is updated such
that a column in the column-list is
modified.
However, there are cases when the triggers are launched even when the columns are not modified (ie the same exact value is in the both OLD and NEW row)
This happens on BEFORE triggers, never saw it happening on AFTER.
Ways to replicate the problem:
1. Define a before trigger, which fires on update of a specific column in any table.
2. Run an sql which says "update table1 set column1 = column1 where ... "
3. You will see that trigger fires, even though it is not supposed to.
Is this an expected behaviour on "BEFORE" triggers?
Arcady

If this were a sql server question, then I could tell you that this is by design. A trigger will be executed regardless of the number of rows affected (including zero) and regardless of whether any column in any of the affected rows was changed. I will also point out that PB was designed to work within this design by the inclusion of the [where clause for update/delete] option in the update properties of the datawindow. The idea is that you avoid actual row updates (in the table) where nothing has actually changed (and it also supports collision avoidance).
Based on the history, I would assume that Sybase works exactly the same.

Installing Sybase SQL Anywhere license keys after initial installation.

Hi,
I installed Sybase SQL Anywhere 16 before I actually received the valid License Key. So during the installation I've used the license key provided by the instructions. Afterwards, I've received the purchase license key. Do i need to reinstall SQL Anywhere all over? Or can it just continue to function on that license key? From what i understand, I can not change the license key after the installation was complete. I would have to completely uninstall and re-install SQL Anywhere 16. Is that correct?
Thanks
Aron

Hi Aron,
I would have to completely uninstall and re-install SQL Anywhere 16. Is that correct?
No, you don't have to do this in SQL Anywhere 16 - you can change SQL Anywhere editions by changing the license key on the accompanying server executable license file (e.g. dbsrv16.lic) with the Server Licensing Utility (dblic). You can use the "-k" switch in order to specify a new key:
dblic -k <reg_key> dbsrv16.lic
Regards,
Jeff Albion
SAP Active Global Support

Sybase SQL Anywhere migration

Hi all
I'm migrating a little db (10 tables) from Sybase ASA 7/8 to Oracle 8. How could I do this the better way?
Thank you

Sebastian,
We currently support migration from Sybase Adaptive Server 11.9.2 to Oracle 8i. Sybase SQL Anywhere migration support is under development.
Turloch
Oracle Migration Workbench Team

Update Sybase SQL Anywhere

BH
Hi,
I'm trying to update Sybase SQL Anywhere, and I'm taken to a website which says "You have selected a download which requires a Technical Support Contact registered with MySybase. Please register your Technical Support Contact at: Edit Roles." This seems new. I always was able to download the updates before. What should i do?
Thanks
Aron

Hi Aron,
As of July 7th, 2014, updates/EBFs for SQL Anywhere are no longer available for anonymous public download on sybase.com unless you had a prior Sybase Technical Support contract that you are continuing to use. Even with a contract, this resource is scheduled to be decomissioned on December 15th.
Updates/Patches ("Support Packs") for SQL Anywhere are now supplied through your SAP Support Contract and are available through the SAP Support Portal. You can find SQL Anywhere 12 patches here and SQL Anywhere 16 patches here.
Regards,
Jeff Albion
SAP Active Global Support

Connect to Sybase SQL Anywhere from a remote location.

BH
Hi, we are running SQL Anywhere 16. Currently our client computers are connecting through ODBC. Is there a way to connect to our server from a Remote Location (over the internet)? If yes, how?
Thanks
Aron

Hi Aron,
Is there a way to connect to our server from a Remote Location (over the internet)?
Yes, there is.
If yes, how?
You will need to supply a HOSTNAME (or direct IP) and PORT to the server running the network database server, communicating over TCP (Note: This may involve opening a TCP port on your firewall to provide a direct TCP route). For the SQL Anywhere client, this information can be set in the ODBC DSN entry as the following screenshot shows:
Note that this is unencrypted traffic across TCP/IP, by default.
If this communication is over the Internet, using an unencrypted channel directly to the database is not recommended. Instead, we would recommend that you also configure Transport Layer Security (TLS) with strong encryption enabled using a certificate (either self-signed or provided by a Certificate Authority (CA)). To do this, you need to create the certificates and then start the SQL Anywhere database server with the (private) server-side identity certificate.
Once the database server is started, you will then need to configure the client for secure communication with the public certificate. When configuring Transport Layer Security on the ODBC client, the security settings (e.g. trusted_certificates, certificate_unit, certificate_company, certificate_name) can be entered on the "Network" tab:
Regards,
Jeff Albion
SAP Active Global Support

Default database name,username & password set-up in CMS!

Hi All,
Is there any way to configure the database name, database username and password as default in CMS, so that when ever we deploy the report we doesn't need to give the database configuration details everytime to each and every individual reports. we have almost 400 reports running in the server and for every month there will be atleast 5 new or modified reports adds up to the list. I tried but couldn't find any solution.
thankz,
kalyan.

Hi,
I would recommend to build a generic report with the database connection and the username you want
You can then make this report available to the developers, who can use it as template for building the "real" reports.
Regards,
Stratos

Sybase SQL Anywhere Plugin Beta Program

The Beta Program for the Sybase SQL Anywere Plugin to the
Migration Workbench will be commencing soon and we are presently
looking for beta customers.
If you are interested in getting early access to the SQL Anywhere
Plugin then please send an email to :
[email protected]
Regards,
Marie
Oracle Technology Network
http://technet.oracle.com
null

Let me start with the unixODBC driver:
There's no generic location as it depends which package you've used to install the UnixODBC driver manager or how you compiled it from scratch. I commonly prefer to compile it from scratch as this offers me to install it to any location I like.
If you're not sure where it is located, you could perform a search on your machine looking for libodbc.so. Then cross check it with "file <location>/libodbc.so" to see the lib is a 64bit library.
So let's assume in the /usr/lib64 you found the libodbc.so library, then the setting
HS_FDS_SHAREABLE_NAME=/usr/lib64/libodbc.so
is correct. Else you need to adopt the parameter.
Next step is to check out which unixODBC version is installed. That's commonly done by calling "odbcinst -j".
Looking now ta the gateway init file there's a parameter HS_NLS_NCHAR set to UTF-8. UnixODBC is commonly compiled with UCS2 support, so please change it to HS_NLS_NCHAR=UCS2
Could you also please post the content of the odbc.ini file "more /etc/odbc.ini"?
Thanks,
Klaus

Database name in MS SQL server 7/2000

Hi, Folks!!
I have a (basic) question regarding connecting up to an MS SQL server. I know the basic syntax of connecting to the server, however, I have not seen any examples on the java.sun.com site that show where you can insert the database name in the connection statements. I have search (some) of the discussions here but have not found anything anything conclusive.
Could someone point me in the right direction, at least?
TIA,
Signed: Frustrated!
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAUGH!!!

Okay,
I think I got it!
instead of using:
Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver");
Connection con = DriverManager.getConnection("jdbc:microsoft:sqlserver://<srvrName>:<portNumber>;DatabaseName=<dbName>", UID, PWD);I used the following:
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
Connection con = DriverManager.getConnection("jdbc:odbc:<srvrName>;DatabaseName=<dbName>", UID, PWD);I don't have any of the extra Microsoft drivers installed on my computer so I had to use what was available with Java and that is the JDBC-ODBC bridge. It was just a simple matter of adding ";DatabaseName=<dbName>" to what I already had. It makes sense now that I think about it. I hope somebody stumbles accross this message someday and avoids the grief I went through.

Default Database name of sybase SQL Anywhere in SAP BO

Similar Messages

Maybe you are looking for