Jaguar help!

From: David Spaisman <davedba_at_intercall.net>
Date: Fri, 13 Aug 1999 21:15:35 -0700
Message-ID: <37B4ED67.68181D75@intercall.net>

Hello:

I am the dba for an oracle and an mssql application. One of the developers with whom I work has been using Jaguar 3.0 with limited success. He has encountered several odbc errrors based upon msdtc(microsoft distributed transaction manager) in some past runs of Jaguar. The developer only talks to sybase when there are definite Jaguar messages but begs off of course when tere any other issues.

Yesterday, he tried running a Jaguar session which was suppose to read some records from oracle tables(on one server) and write them to Mssql 6.5 tables(in a database on another server). Jaguar is sitting on a third separate server.

A number of errors were encountered in the session. Errors apparently related to netlib, msdtc, odbc errors in oracle and in mssql(really msdtc) and then an error saying that Jaguar couldn't insert rows into a specific table. Of course this was immediately taking to be a database locking problem when the message in the error log do not state anything like that. Since it was interpreted as a database locking issue, the log was referred to me to reolve the 'locking' problem.

This is fairly new technology. I am baffled as to where to get a reply since all of this prolem insolves sybase software talking to oracle and then msdtc. So my questions are:

Is there a newsgroup or other forum where I can get information and help on Jaguar.
The log in question is attached below. Can any one give me some help as to what is going on here?

Thanks for any information you can provide here.

David Spaisman

Aug 13 10:09:28 1999: SRVLIB Message: 16240/10/0: Net-Library routine net_listen(CPQCAP-DEV02 9000) failed in srv__start_listeners Network error: status = 23 - Net-Lib protocol driver call to register a listener failed

Aug 13 10:09:28 1999: Listener # 1: Jaguar_tds: Active: yes Protocol: 'TDS': 'localhost',7878 Security Profile: '*NONE*' Aug 13 10:09:28 1999: Listener # 2: Jaguar_OpenServer: Active: yes Protocol: 'TDS': 'localhost',7979 Security Profile: '*NONE*' Aug 13 10:09:28 1999: Listener # 3: Jaguar_http: Active: yes Protocol: 'HTTP': 'localhost',8080 Security Profile: '*NONE*' Aug 13 10:09:28 1999: Listener # 4: Jaguar_https1: Active: yes Protocol: 'HTTPS': 'localhost',8081 Security Profile: 'sybpks_intl' Subject DN: CN = Sample1, O = Some Organization, L = Some Locality, ST = Some State, C = US
Aug 13 10:09:28 1999: Listener # 5: Jaguar_https2: Active: yes Protocol: 'HTTPS': 'localhost',8082 Security Profile: 'sybpks_intl_mutual_auth'
Subject DN: CN = Sample2, O = Some Organization, L = Some Locality, ST = Some State, C = US
Aug 13 10:09:28 1999: Listener # 6: Jaguar_iiop: Active: yes Protocol: 'IIOP': 'CPQCAP-DEV02',9000 Security Profile: '*NONE*' Aug 13 10:09:28 1999: Listener # 7: Jaguar_iiops1: Active: yes Protocol: 'IIOPS': 'localhost',9001 Security Profile: 'sybpks_intl' Subject DN: CN = Sample1, O = Some Organization, L = Some Locality, ST = Some State, C = US
Aug 13 10:09:28 1999: Listener # 8: Jaguar_iiops2: Active: yes Protocol: 'IIOPS': 'localhost',9002 Security Profile: 'sybpks_intl_mutual_auth'
Subject DN: CN = Sample2, O = Some Organization, L = Some Locality, ST = Some State, C = US
Aug 13 10:09:28 1999: Listener # 9: Jaguar_iiop1: Active: no Protocol: 'IIOP': 'CPQCAP-DEV02',9000 Security Profile: '*NONE*' Aug 13 10:09:28 1999: Warning: DLL name is different, using previous name

Aug 13 10:09:28 1999: Starting Jaguar CTS 3.0
Aug 13 10:09:28 1999: Java JIT Compiler disabled
Aug 13 10:09:28 1999: Java component debugging disabled
Aug 13 10:09:29 1999: Java virtual machine initialized (version 10001)
Aug 13 10:09:29 1999: Repository: E:\Apps\Sybase\Jaguar CTS

3.0\Repository

Aug 13 10:09:29 1999: Server's native codeset is utf8
Aug 13 10:09:29 1999: NameServiceURL: iiop://0:0
Aug 13 10:09:29 1999: Starting services...
Aug 13 10:09:29 1999: Authentication timeout period is 3600 seconds.
Aug 13 10:09:29 1999: Note: authentication timeout can be disabled.
Aug 13 10:09:29 1999: Authentication lockout period is 600 seconds.
Aug 13 10:09:29 1999: Note: authentication lockout can be disabled.
Aug 13 10:09:30 1999: Started: Jaguar/Repository
Aug 13 10:09:30 1999: Started: Jaguar/GarbageCollector
Aug 13 10:09:31 1999: WARNING - cache is not defined in the repository.
Aug 13 10:09:31 1999: Started: Jaguar/JCM
Aug 13 10:09:31 1999: Starting Jaguar Naming Services...
Aug 13 10:09:31 1999: Started: CosNaming/NamingContext
Aug 13 10:09:31 1999: Started: CtsServlet/ServletService
Aug 13 10:09:31 1999: Package 'SurfSideVideoPJ' is not installed in this

server
Aug 13 10:09:32 1999: Exception 'CosNaming::NamingContext::NotFound' in Session::create for component 'SurfSideVideoPJ/CleanupService' Aug 13 10:09:32 1999: startService: failed to start 'SurfSideVideoPJ/CleanupService'

Aug 13 10:09:32 1999: Running services...
Aug 13 10:09:32 1999: Running: CosNaming/NamingContext
Aug 13 10:09:32 1999: Running: Jaguar/GarbageCollector
Aug 13 10:09:32 1999: Running: CtsServlet/ServletService
Aug 13 10:09:33 1999: Stopped: CosNaming/NamingContext
Aug 13 10:18:18 1999: ACTIVATE OF n_cst_bookingupdate
Aug 13 10:18:21 1999: AFLIB Message: 18231/11/0:

DTCTransaction::_Enlist(): The DTC call SQLSetConnectOpt(ENLIST_IN_DTC)() failed!

Aug 13 10:18:26 1999: DEACTIVATE OF n_cst_bookingupdate
Aug 13 10:21:01 1999: ACTIVATE OF n_cst_bookingupdate
Aug 13 10:21:01 1999: cm__odbc_error: SQLError: 923, SQLState: S1000,

[Oracle][ODBC][Ora]ORA-00923: FROM keyword not found where expected
.
Aug 13 10:21:02 1999: AFLIB Message: 18231/11/0: DTCTransaction::_Enlist(): The DTC call SQLSetConnectOpt(ENLIST_IN_DTC)() failed!

Aug 13 10:21:03 1999: BookongUpdate: ids_contractprocessstat Rowcount: 1

Aug 13 10:21:03 1999: BookongUpdate: Info. Processed contract 200000001035
Aug 13 10:21:03 1999: BookongUpdate: Info. Book/Reject Update Complete. Contracts processed: 1

Aug 13 10:21:03 1999: DEACTIVATE OF n_cst_bookingupdate
Aug 13 10:21:40 1999: ACTIVATE OF n_cst_dtfe_ep_manager
Aug 13 10:21:40 1999: cm__odbc_error: SQLError: 923, SQLState: S1000,