|
Which feature in a V12 database file needs OMNI/CIS support to be available? The documentation onyl refers to "Required only if using remote data access", but I don't have a remote server configured in the affected database. And by the way, what is OMNI/CIS? |
|
"OmniConnect is one of several Adaptive Server Enterprise bundles which uses the Component Integration Services feature to provide access to external data sources. OmniConnect allows users to access both Sybase and non-Sybase databases on different servers. These external data sources include host data files and tables, views and RPCs (remote procedure calls) in database systems such as Adaptive Server, Oracle, and DB2 ..." - 1997 http://download.sybase.com/pdfdocs/asg1150e/omnintro.pdf I think OmniConnect existed before Sybase bought Micro Decisionware Inc in 1994 (http://findarticles.com/p/articles/mi_m0SMG/is_n3_v14/ai_15061381/), but soon after the OmniConnect and MDI code bases were integrated (http://members.tripod.com/f_angah/keselamatan.htm) and forever after (at least in my mind) OmniConnect and MDI are one and the same. MDI was a wonderful company, great products like PC/SQL that contained a wizard for creating SQL statements, plus wonderful middleware and gateways when "middleware" was all the rage like "cloud" is today. I also believe that iAnywhere Solutions subsequently created their own version of the code but apparently the "Omni" and "CIS" names will hang around forever. thanks breck for the explanation
(09 Jul '12, 09:20)
Martin
2
Breck: AFAIK iAnywhere's OMNI/CIS code was written from scratch and was not just a copy or rebuild of the pre-existing OmniConnect code. LOAD TABLE and OPENSTRING do not use OMNI/CIS.
(09 Jul '12, 09:29)
Mark Culp
|
|
OMNI, CIS and Remote Data Access are all the same thing as far as SQL Anywhere is concerned. The official term is Remote Data Access, but as Breck pointed out, OMNI and CIS will probably hang around forever. The dbcis12.dll is only needed and loaded if you have Remote Data Access servers configured for remote back ends like SA, Oracle, ASE, DB2, MySQL, ADS, MS Access, MS SQL Server, or any other generic ODBC back end. The dbcis12.dll is also needed if you have any directory access serves configured. Perform a SELECT count(*) FROM SYS.SYSSERVER. If you do not have any remote servers configured, then the count will be 0 and the server will not load dbcis12.dll until you issue a CREATE SERVER statement and actually configure a Remote Data Access server. If the count is non-zero, then the server will load dbcis12.dll at startup and will keep the dll loaded for the lifetime of the server. BTW, Mark is also correct, the OMNI/CIS/Remote Data Access code in SQL Anywhere was written from scratch rather than simply copying the pre-existing OmniConnect code. 1
Good to know, I have a Directory Access Server, so they are counted too as Remote Servers.
(12 Jul '12, 03:09)
Martin
|
A question I have asked for years, too - possibly related to Sybase OmniConnect?
Besides that, I had also thought that dbcisX.dll is only required for CREATE SERVER stuff.
Wild guessing: Are you using HA or read-only scale-out?
Of course, you could simply deploy the dbcis12.dll and set OPTION CIS_OPTION = 7 and check if there are any CIS activities logged in the console...
@Martin: The perils of asking two questions at once... now you have to post another question to get the answer you really need :)
Well, "learning lessons from (company) history" is so much more than getting the real work done:)
Posting here, too:)