Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

PowerDynamo and Open Client connections vs ODBC connections - HELP!!!!

22 posts in General Discussion (old) Last posting was on 2000-04-04 20:36:39.0Z
Brad McLeod Posted on 2000-03-28 20:11:40.0Z
Newsgroups: sybase.public.easerver
From: "Brad McLeod" <brad.mcleod@worldnet.att.net>
Subject: PowerDynamo and Open Client connections vs ODBC connections - HELP!!!!
Date: Tue, 28 Mar 2000 14:11:40 -0600
Lines: 707
X-Newsreader: Microsoft Outlook Express 4.72.3155.0
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0
NNTP-Posting-Host: ailsa-ded.webzone.net 208.152.102.253
Message-ID: <347_wlbGKKPm$GA.52@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:25438
Article PK: 155529

Lance, Carson and Larry -

Based upon a previous thread I posted regarding ASA and ASE environments for
our website DB and the issues we were having, I took your advice and did the
following:

1. Generated our website DB in an ASE 11.9.2 environment instead of ASA
6.0.2
2. Established an Open Client connection profile to the web DB instead of
using ODBC.
3. Created an Open Client connection from the website to the ASE 11.9.2
primary database.

Here's is what is happening now!:( - Please see the attachment!

Summary:

PD pages executing stored procedures under an Open Client/ASE 11.9.2 PD
configuration, do not execute. Under an ODBC/ASE 11.9.2 PD configuration
the do.
We have PD web pages that execute SQL and Stored Procedures against the ASE
11.9.2 database. When accessing the PD web DB via ODBC, the pages executed
correctly and the data was retrieved as expected. Now that we've switched
over to Open Client, we are experiencing failures with all of our stored
procedures executed by our PD web pages that use stored procedures. (Please
refer to the attachment for specifics!)

Further, any stored procedures that use a 'Select Into' or 'Create' command
do not function under either ODBC or Open Client when the PD web DB is in
ASE 11.9.2. When the PD web DB was in ASA and used an ODBC connection, they
worked!!

Any ideas, insight, guidance would be appreciated. As I said, I took all
your advice and this is where we are at now. I have to have this
application, website and supporting database's ready for beta testing in 3
DAYS!! HELP!!!

TIA

Brad McLeod
StoneHenge Partners


Lance Andersen Posted on 2000-03-29 14:19:38.0Z
Newsgroups: sybase.public.easerver
Date: Wed, 29 Mar 2000 09:19:38 -0500
From: Lance Andersen <lancea@sybase.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: PowerDynamo and Open Client connections vs ODBC connections - HELP!!!!
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 78
NNTP-Posting-Host: alder.sybase.com 157.133.125.15
Message-ID: <347_38E210FA.E34D6FA0@sybase.com>
References: <347_wlbGKKPm$GA.52@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:25387
Article PK: 155480

PowerDynamo runs in chained mode (autoCommit = FALSE) for
performance reasons. We explicitly change to autoCommit=FALSE and the
difference between the ODBC driver and Dynamo's OpenClient driver lies
in
each drivers implementation of AutoCommit. Dynamo's OpenClient driver
toggles chained mode. The ODBC driver does not and probably accomplishes
its AutoCommit support in a very complicated way.

You can change this via the Connection.autoCommit property. You can also
use sp_procxmode but please read the docs on transaction handling first
(tsql guide I believe)


As far as select into, make sure you have 'select into' enabled for the
database. See the docs for sp_dboption.

Lance

Brad McLeod wrote:
>
> Lance, Carson and Larry -
>
> Based upon a previous thread I posted regarding ASA and ASE environments for
> our website DB and the issues we were having, I took your advice and did the
> following:
>
> 1. Generated our website DB in an ASE 11.9.2 environment instead of ASA
> 6.0.2
> 2. Established an Open Client connection profile to the web DB instead of
> using ODBC.
> 3. Created an Open Client connection from the website to the ASE 11.9.2
> primary database.
>
> Here's is what is happening now!:( - Please see the attachment!
>
> Summary:
>
> PD pages executing stored procedures under an Open Client/ASE 11.9.2 PD
> configuration, do not execute. Under an ODBC/ASE 11.9.2 PD configuration
> the do.
> We have PD web pages that execute SQL and Stored Procedures against the ASE
> 11.9.2 database. When accessing the PD web DB via ODBC, the pages executed
> correctly and the data was retrieved as expected. Now that we've switched
> over to Open Client, we are experiencing failures with all of our stored
> procedures executed by our PD web pages that use stored procedures. (Please
> refer to the attachment for specifics!)
>
> Further, any stored procedures that use a 'Select Into' or 'Create' command
> do not function under either ODBC or Open Client when the PD web DB is in
> ASE 11.9.2. When the PD web DB was in ASA and used an ODBC connection, they
> worked!!
>
> Any ideas, insight, guidance would be appreciated. As I said, I took all
> your advice and this is where we are at now. I have to have this
> application, website and supporting database's ready for beta testing in 3
> DAYS!! HELP!!!
>
> TIA
>
> Brad McLeod
> StoneHenge Partners
>
> Name: Open Client-ASE Problem.doc
> Open Client-ASE Problem.doc Type: Microsoft Word Document (application/msword)
> Encoding: x-uuencode

--
===============================================================================
Lance J. Andersen Email: lancea@sybase.com
Sybase Product Support Engineering Phone:(781) 564-6336
77 South Bedford Street Fax: (781) 564-7001
Burlington, MA 01803

The Dark Knight Returns!!! Let's Go Penguins!!!
===============================================================================


Brad McLeod Posted on 2000-03-30 16:47:23.0Z
Newsgroups: sybase.public.easerver
From: "Brad McLeod" <brad.mcleod@worldnet.att.net>
Subject: Re: PowerDynamo and Open Client connections vs ODBC connections - HELP!!!!
Date: Thu, 30 Mar 2000 10:47:23 -0600
Lines: 102
X-Newsreader: Microsoft Outlook Express 4.72.3155.0
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0
NNTP-Posting-Host: ailsa-ded.webzone.net 208.152.102.253
Message-ID: <347_fP5YQhmm$GA.52@forums.sybase.com>
References: <347_wlbGKKPm$GA.52@forums.sybase.com> <347_38E210FA.E34D6FA0@sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:25215
Article PK: 155346

Lance -

In a previous thread you had mentioned configuring PowerDynamo document
cache. Is the intent here to load all of the current website db documents
into cache (memory) or just allocate a certain amount of cache based upon
the size of our website db?

TIA

Bad McLeod

Lance Andersen wrote in message <38E210FA.E34D6FA0@sybase.com>...
> PowerDynamo runs in chained mode (autoCommit = FALSE) for
>performance reasons. We explicitly change to autoCommit=FALSE and the
>difference between the ODBC driver and Dynamo's OpenClient driver lies
>in
>each drivers implementation of AutoCommit. Dynamo's OpenClient driver
>toggles chained mode. The ODBC driver does not and probably accomplishes
>its AutoCommit support in a very complicated way.
>
>You can change this via the Connection.autoCommit property. You can also
>use sp_procxmode but please read the docs on transaction handling first
>(tsql guide I believe)
>
>
>As far as select into, make sure you have 'select into' enabled for the
>database. See the docs for sp_dboption.
>
>Lance
>
>Brad McLeod wrote:
>>
>> Lance, Carson and Larry -
>>
>> Based upon a previous thread I posted regarding ASA and ASE environments
for
>> our website DB and the issues we were having, I took your advice and did
the
>> following:
>>
>> 1. Generated our website DB in an ASE 11.9.2 environment instead of ASA
>> 6.0.2
>> 2. Established an Open Client connection profile to the web DB instead
of
>> using ODBC.
>> 3. Created an Open Client connection from the website to the ASE 11.9.2
>> primary database.
>>
>> Here's is what is happening now!:( - Please see the attachment!
>>
>> Summary:
>>
>> PD pages executing stored procedures under an Open Client/ASE 11.9.2 PD
>> configuration, do not execute. Under an ODBC/ASE 11.9.2 PD configuration
>> the do.
>> We have PD web pages that execute SQL and Stored Procedures against the
ASE
>> 11.9.2 database. When accessing the PD web DB via ODBC, the pages
executed
>> correctly and the data was retrieved as expected. Now that we've
switched
>> over to Open Client, we are experiencing failures with all of our stored
>> procedures executed by our PD web pages that use stored procedures.
(Please
>> refer to the attachment for specifics!)
>>
>> Further, any stored procedures that use a 'Select Into' or 'Create'
command
>> do not function under either ODBC or Open Client when the PD web DB is in
>> ASE 11.9.2. When the PD web DB was in ASA and used an ODBC connection,
they
>> worked!!
>>
>> Any ideas, insight, guidance would be appreciated. As I said, I took all
>> your advice and this is where we are at now. I have to have this
>> application, website and supporting database's ready for beta testing in
3
>> DAYS!! HELP!!!
>>
>> TIA
>>
>> Brad McLeod
>> StoneHenge Partners
>>
>> Name: Open Client-ASE Problem.doc
>> Open Client-ASE Problem.doc Type: Microsoft Word Document
(application/msword)
>> Encoding: x-uuencode
>
>--
>===========================================================================
====
>Lance J. Andersen Email: lancea@sybase.com
>Sybase Product Support Engineering Phone:(781) 564-6336
>77 South Bedford Street Fax: (781) 564-7001
>Burlington, MA 01803
>
>The Dark Knight Returns!!! Let's Go Penguins!!!
>===========================================================================

====


Lance Andersen Posted on 2000-03-30 17:37:22.0Z
Newsgroups: sybase.public.easerver
Date: Thu, 30 Mar 2000 12:37:22 -0500
From: Lance Andersen <lancea@sybase.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: PowerDynamo and Open Client connections vs ODBC connections - HELP!!!!
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 120
NNTP-Posting-Host: alder.sybase.com 157.133.125.15
Message-ID: <347_38E390D2.8688C179@sybase.com>
References: <347_wlbGKKPm$GA.52@forums.sybase.com> <347_38E210FA.E34D6FA0@sybase.com> <347_fP5YQhmm$GA.52@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:25210
Article PK: 228491

The goal is to cut down as much work that needs to be done by PD. So
what you are trying to do is minimize access by PD to the backend as
well as the generation of the output from a PD template/script.

Two items get placed into the cache, the source of the document and
optionally the generated output.

You control which document has output stored in the cache by using the
cachedOutputTimeOut tag or property.

for the most optimal performance you want to try and cache as much
output as you possibly can as this saves PD from having to process the
documents on each request.

Brad McLeod wrote:
>
> Lance -
>
> In a previous thread you had mentioned configuring PowerDynamo document
> cache. Is the intent here to load all of the current website db documents
> into cache (memory) or just allocate a certain amount of cache based upon
> the size of our website db?
>
> TIA
>
> Bad McLeod
>
> Lance Andersen wrote in message <38E210FA.E34D6FA0@sybase.com>...
> > PowerDynamo runs in chained mode (autoCommit = FALSE) for
> >performance reasons. We explicitly change to autoCommit=FALSE and the
> >difference between the ODBC driver and Dynamo's OpenClient driver lies
> >in
> >each drivers implementation of AutoCommit. Dynamo's OpenClient driver
> >toggles chained mode. The ODBC driver does not and probably accomplishes
> >its AutoCommit support in a very complicated way.
> >
> >You can change this via the Connection.autoCommit property. You can also
> >use sp_procxmode but please read the docs on transaction handling first
> >(tsql guide I believe)
> >
> >
> >As far as select into, make sure you have 'select into' enabled for the
> >database. See the docs for sp_dboption.
> >
> >Lance
> >
> >Brad McLeod wrote:
> >>
> >> Lance, Carson and Larry -
> >>
> >> Based upon a previous thread I posted regarding ASA and ASE environments
> for
> >> our website DB and the issues we were having, I took your advice and did
> the
> >> following:
> >>
> >> 1. Generated our website DB in an ASE 11.9.2 environment instead of ASA
> >> 6.0.2
> >> 2. Established an Open Client connection profile to the web DB instead
> of
> >> using ODBC.
> >> 3. Created an Open Client connection from the website to the ASE 11.9.2
> >> primary database.
> >>
> >> Here's is what is happening now!:( - Please see the attachment!
> >>
> >> Summary:
> >>
> >> PD pages executing stored procedures under an Open Client/ASE 11.9.2 PD
> >> configuration, do not execute. Under an ODBC/ASE 11.9.2 PD configuration
> >> the do.
> >> We have PD web pages that execute SQL and Stored Procedures against the
> ASE
> >> 11.9.2 database. When accessing the PD web DB via ODBC, the pages
> executed
> >> correctly and the data was retrieved as expected. Now that we've
> switched
> >> over to Open Client, we are experiencing failures with all of our stored
> >> procedures executed by our PD web pages that use stored procedures.
> (Please
> >> refer to the attachment for specifics!)
> >>
> >> Further, any stored procedures that use a 'Select Into' or 'Create'
> command
> >> do not function under either ODBC or Open Client when the PD web DB is in
> >> ASE 11.9.2. When the PD web DB was in ASA and used an ODBC connection,
> they
> >> worked!!
> >>
> >> Any ideas, insight, guidance would be appreciated. As I said, I took all
> >> your advice and this is where we are at now. I have to have this
> >> application, website and supporting database's ready for beta testing in
> 3
> >> DAYS!! HELP!!!
> >>
> >> TIA
> >>
> >> Brad McLeod
> >> StoneHenge Partners
> >>
> >> Name: Open Client-ASE Problem.doc
> >> Open Client-ASE Problem.doc Type: Microsoft Word Document
> (application/msword)
> >> Encoding: x-uuencode
> >
> >--
> >===========================================================================
> ====
> >Lance J. Andersen Email: lancea@sybase.com
> >Sybase Product Support Engineering Phone:(781) 564-6336
> >77 South Bedford Street Fax: (781) 564-7001
> >Burlington, MA 01803
> >
> >The Dark Knight Returns!!! Let's Go Penguins!!!
> >===========================================================================
> ====

--
===============================================================================
Lance J. Andersen Email: lancea@sybase.com
Sybase Product Support Engineering Phone:(781) 564-6336
77 South Bedford Street Fax: (781) 564-7001
Burlington, MA 01803

The Dark Knight Returns!!! Let's Go Penguins!!!
===============================================================================


Brad McLeod Posted on 2000-03-30 20:27:58.0Z
Newsgroups: sybase.public.easerver
From: "Brad McLeod" <brad.mcleod@worldnet.att.net>
Subject: Re: PowerDynamo and Open Client connections vs ODBC connections - HELP!!!!
Date: Thu, 30 Mar 2000 14:27:58 -0600
Lines: 167
X-Newsreader: Microsoft Outlook Express 4.72.3155.0
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0
NNTP-Posting-Host: ailsa-ded.webzone.net 208.152.102.253
Message-ID: <347_XcvMlcom$GA.201@forums.sybase.com>
References: <347_wlbGKKPm$GA.52@forums.sybase.com> <347_38E210FA.E34D6FA0@sybase.com> <347_fP5YQhmm$GA.52@forums.sybase.com> <347_38E390D2.8688C179@sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:25191
Article PK: 228465

Lance -

Understand your last and thanks. Back to the original problem. I modified
the the stored procedure to use 'anymode' and the database to allow for
'select into'. Although we no longer get the original error message, we now
get this:

EXEC sp_rptTEST 1,1,'level1','1999-3-1 0:00:00','1999-12-31 0:00:00'-1 --
SELECT INTO command not allowed within multi-statement transaction.

As mentioned earlier, we are running this via an Open Client connection to
ASE 11.9.2. Any other ideas? We've got just under 24 hours till
howtime:( and everything we've tried doesn't seem to work!!

TIA

Brad McLeod
StoneHenge Partners

Lance Andersen wrote in message <38E390D2.8688C179@sybase.com>...
>The goal is to cut down as much work that needs to be done by PD. So
>what you are trying to do is minimize access by PD to the backend as
>well as the generation of the output from a PD template/script.
>
>Two items get placed into the cache, the source of the document and
>optionally the generated output.
>
>You control which document has output stored in the cache by using the
>cachedOutputTimeOut tag or property.
>
>for the most optimal performance you want to try and cache as much
>output as you possibly can as this saves PD from having to process the
>documents on each request.
>
>
>Brad McLeod wrote:
>>
>> Lance -
>>
>> In a previous thread you had mentioned configuring PowerDynamo document
>> cache. Is the intent here to load all of the current website db
documents
>> into cache (memory) or just allocate a certain amount of cache based upon
>> the size of our website db?
>>
>> TIA
>>
>> Bad McLeod
>>
>> Lance Andersen wrote in message <38E210FA.E34D6FA0@sybase.com>...
>> > PowerDynamo runs in chained mode (autoCommit = FALSE) for
>> >performance reasons. We explicitly change to autoCommit=FALSE and the
>> >difference between the ODBC driver and Dynamo's OpenClient driver lies
>> >in
>> >each drivers implementation of AutoCommit. Dynamo's OpenClient driver
>> >toggles chained mode. The ODBC driver does not and probably accomplishes
>> >its AutoCommit support in a very complicated way.
>> >
>> >You can change this via the Connection.autoCommit property. You can also
>> >use sp_procxmode but please read the docs on transaction handling first
>> >(tsql guide I believe)
>> >
>> >
>> >As far as select into, make sure you have 'select into' enabled for the
>> >database. See the docs for sp_dboption.
>> >
>> >Lance
>> >
>> >Brad McLeod wrote:
>> >>
>> >> Lance, Carson and Larry -
>> >>
>> >> Based upon a previous thread I posted regarding ASA and ASE
environments
>> for
>> >> our website DB and the issues we were having, I took your advice and
did
>> the
>> >> following:
>> >>
>> >> 1. Generated our website DB in an ASE 11.9.2 environment instead of
ASA
>> >> 6.0.2
>> >> 2. Established an Open Client connection profile to the web DB
instead
>> of
>> >> using ODBC.
>> >> 3. Created an Open Client connection from the website to the ASE
11.9.2
>> >> primary database.
>> >>
>> >> Here's is what is happening now!:( - Please see the attachment!
>> >>
>> >> Summary:
>> >>
>> >> PD pages executing stored procedures under an Open Client/ASE 11.9.2
PD
>> >> configuration, do not execute. Under an ODBC/ASE 11.9.2 PD
configuration
>> >> the do.
>> >> We have PD web pages that execute SQL and Stored Procedures against
the
>> ASE
>> >> 11.9.2 database. When accessing the PD web DB via ODBC, the pages
>> executed
>> >> correctly and the data was retrieved as expected. Now that we've
>> switched
>> >> over to Open Client, we are experiencing failures with all of our
stored
>> >> procedures executed by our PD web pages that use stored procedures.
>> (Please
>> >> refer to the attachment for specifics!)
>> >>
>> >> Further, any stored procedures that use a 'Select Into' or 'Create'
>> command
>> >> do not function under either ODBC or Open Client when the PD web DB is
in
>> >> ASE 11.9.2. When the PD web DB was in ASA and used an ODBC
connection,
>> they
>> >> worked!!
>> >>
>> >> Any ideas, insight, guidance would be appreciated. As I said, I took
all
>> >> your advice and this is where we are at now. I have to have this
>> >> application, website and supporting database's ready for beta testing
in
>> 3
>> >> DAYS!! HELP!!!
>> >>
>> >> TIA
>> >>
>> >> Brad McLeod
>> >> StoneHenge Partners
>> >>
>> >> Name: Open Client-ASE Problem.doc
>> >> Open Client-ASE Problem.doc Type: Microsoft Word Document
>> (application/msword)
>> >> Encoding: x-uuencode
>> >
>> >--
>>
>===========================================================================
>> ====
>> >Lance J. Andersen Email: lancea@sybase.com
>> >Sybase Product Support Engineering Phone:(781) 564-6336
>> >77 South Bedford Street Fax: (781) 564-7001
>> >Burlington, MA 01803
>> >
>> >The Dark Knight Returns!!! Let's Go Penguins!!!
>>
>===========================================================================
>> ====
>
>--
>===========================================================================
====
>Lance J. Andersen Email: lancea@sybase.com
>Sybase Product Support Engineering Phone:(781) 564-6336
>77 South Bedford Street Fax: (781) 564-7001
>Burlington, MA 01803
>
>The Dark Knight Returns!!! Let's Go Penguins!!!
>===========================================================================

====


Lance Andersen Posted on 2000-03-30 20:35:03.0Z
Newsgroups: sybase.public.easerver
Date: Thu, 30 Mar 2000 15:35:03 -0500
From: Lance Andersen <lancea@sybase.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: PowerDynamo and Open Client connections vs ODBC connections - HELP!!!!
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 33
NNTP-Posting-Host: alder.sybase.com 157.133.125.15
Message-ID: <347_38E3BA77.A1629105@sybase.com>
References: <347_wlbGKKPm$GA.52@forums.sybase.com> <347_38E210FA.E34D6FA0@sybase.com> <347_fP5YQhmm$GA.52@forums.sybase.com> <347_38E390D2.8688C179@sybase.com> <347_XcvMlcom$GA.201@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:25189
Article PK: 155338


Brad McLeod wrote:
>
> Lance -
>
> Understand your last and thanks. Back to the original problem. I modified
> the the stored procedure to use 'anymode' and the database to allow for
> 'select into'. Although we no longer get the original error message, we now
> get this:
>
> EXEC sp_rptTEST 1,1,'level1','1999-3-1 0:00:00','1999-12-31 0:00:00'-1 --
> SELECT INTO command not allowed within multi-statement transaction.
>
> As mentioned earlier, we are running this via an Open Client connection to
> ASE 11.9.2. Any other ideas? We've got just under 24 hours till
> howtime:( and everything we've tried doesn't seem to work!!

Well your answer is in the error as you cannot issue SELECT INTO in
chained mode so your choice is to take the PD connection out of chained
mode (see the previous post) or rework your sprocs.


===============================================================================
Lance J. Andersen Email: lancea@sybase.com
Sybase Product Support Engineering Phone:(781) 564-6336
77 South Bedford Street Fax: (781) 564-7001
Burlington, MA 01803

The Dark Knight Returns!!! Let's Go Penguins!!!
===============================================================================


Brad McLeod Posted on 2000-03-30 16:11:42.0Z
Newsgroups: sybase.public.easerver
From: "Brad McLeod" <brad.mcleod@worldnet.att.net>
Subject: Re: PowerDynamo and Open Client connections vs ODBC connections - HELP!!!!
Date: Thu, 30 Mar 2000 10:11:42 -0600
Lines: 97
X-Newsreader: Microsoft Outlook Express 4.72.3155.0
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0
NNTP-Posting-Host: ailsa-ded.webzone.net 208.152.102.253
Message-ID: <347_2DQSDOmm$GA.298@forums.sybase.com>
References: <347_wlbGKKPm$GA.52@forums.sybase.com> <347_38E210FA.E34D6FA0@sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:25224
Article PK: 155348

Lance -

Thanks! I'll let you know how it goes!!

Brad McLeod

Lance Andersen wrote in message <38E210FA.E34D6FA0@sybase.com>...
> PowerDynamo runs in chained mode (autoCommit = FALSE) for
>performance reasons. We explicitly change to autoCommit=FALSE and the
>difference between the ODBC driver and Dynamo's OpenClient driver lies
>in
>each drivers implementation of AutoCommit. Dynamo's OpenClient driver
>toggles chained mode. The ODBC driver does not and probably accomplishes
>its AutoCommit support in a very complicated way.
>
>You can change this via the Connection.autoCommit property. You can also
>use sp_procxmode but please read the docs on transaction handling first
>(tsql guide I believe)
>
>
>As far as select into, make sure you have 'select into' enabled for the
>database. See the docs for sp_dboption.
>
>Lance
>
>Brad McLeod wrote:
>>
>> Lance, Carson and Larry -
>>
>> Based upon a previous thread I posted regarding ASA and ASE environments
for
>> our website DB and the issues we were having, I took your advice and did
the
>> following:
>>
>> 1. Generated our website DB in an ASE 11.9.2 environment instead of ASA
>> 6.0.2
>> 2. Established an Open Client connection profile to the web DB instead
of
>> using ODBC.
>> 3. Created an Open Client connection from the website to the ASE 11.9.2
>> primary database.
>>
>> Here's is what is happening now!:( - Please see the attachment!
>>
>> Summary:
>>
>> PD pages executing stored procedures under an Open Client/ASE 11.9.2 PD
>> configuration, do not execute. Under an ODBC/ASE 11.9.2 PD configuration
>> the do.
>> We have PD web pages that execute SQL and Stored Procedures against the
ASE
>> 11.9.2 database. When accessing the PD web DB via ODBC, the pages
executed
>> correctly and the data was retrieved as expected. Now that we've
switched
>> over to Open Client, we are experiencing failures with all of our stored
>> procedures executed by our PD web pages that use stored procedures.
(Please
>> refer to the attachment for specifics!)
>>
>> Further, any stored procedures that use a 'Select Into' or 'Create'
command
>> do not function under either ODBC or Open Client when the PD web DB is in
>> ASE 11.9.2. When the PD web DB was in ASA and used an ODBC connection,
they
>> worked!!
>>
>> Any ideas, insight, guidance would be appreciated. As I said, I took all
>> your advice and this is where we are at now. I have to have this
>> application, website and supporting database's ready for beta testing in
3
>> DAYS!! HELP!!!
>>
>> TIA
>>
>> Brad McLeod
>> StoneHenge Partners
>>
>> Name: Open Client-ASE Problem.doc
>> Open Client-ASE Problem.doc Type: Microsoft Word Document
(application/msword)
>> Encoding: x-uuencode
>
>--
>===========================================================================
====
>Lance J. Andersen Email: lancea@sybase.com
>Sybase Product Support Engineering Phone:(781) 564-6336
>77 South Bedford Street Fax: (781) 564-7001
>Burlington, MA 01803
>
>The Dark Knight Returns!!! Let's Go Penguins!!!
>===========================================================================

====


Ashish Mahajan Posted on 2000-03-28 21:17:39.0Z
Newsgroups: sybase.public.easerver
From: "Ashish Mahajan" <ash@NOSPAM.com>
Subject: Re: PowerDynamo and Open Client connections vs ODBC connections - HELP!!!!
Date: Tue, 28 Mar 2000 16:17:39 -0500
Lines: 60
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
NNTP-Posting-Host: pikachu.sybase.com 204.167.42.191
Message-ID: <347_XV73nuPm$GA.298@forums.sybase.com>
References: <347_wlbGKKPm$GA.52@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:25431
Article PK: 228507

Is your sp is trying to do ddl ??
Here is what you could try ? Make sure that before you call the stored
procedure you are in autocommit mode (I'm not sure whether you can 'tell'
Dynamo to set the autocommit mode for you or not)

"Brad McLeod" <brad.mcleod@worldnet.att.net> wrote in message
news:wlbGKKPm$GA.52@forums.sybase.com...
> Lance, Carson and Larry -
>
> Based upon a previous thread I posted regarding ASA and ASE environments
for
> our website DB and the issues we were having, I took your advice and did
the
> following:
>
> 1. Generated our website DB in an ASE 11.9.2 environment instead of ASA
> 6.0.2
> 2. Established an Open Client connection profile to the web DB instead of
> using ODBC.
> 3. Created an Open Client connection from the website to the ASE 11.9.2
> primary database.
>
> Here's is what is happening now!:( - Please see the attachment!
>
> Summary:
>
> PD pages executing stored procedures under an Open Client/ASE 11.9.2 PD
> configuration, do not execute. Under an ODBC/ASE 11.9.2 PD configuration
> the do.
> We have PD web pages that execute SQL and Stored Procedures against the
ASE
> 11.9.2 database. When accessing the PD web DB via ODBC, the pages
executed
> correctly and the data was retrieved as expected. Now that we've switched
> over to Open Client, we are experiencing failures with all of our stored
> procedures executed by our PD web pages that use stored procedures.
(Please
> refer to the attachment for specifics!)
>
> Further, any stored procedures that use a 'Select Into' or 'Create'
command
> do not function under either ODBC or Open Client when the PD web DB is in
> ASE 11.9.2. When the PD web DB was in ASA and used an ODBC connection,
they
> worked!!
>
> Any ideas, insight, guidance would be appreciated. As I said, I took all
> your advice and this is where we are at now. I have to have this
> application, website and supporting database's ready for beta testing in 3
> DAYS!! HELP!!!
>
> TIA
>
> Brad McLeod
> StoneHenge Partners
>
>
>


Bill Zhang Posted on 2000-03-29 16:17:30.0Z
Newsgroups: sybase.public.easerver
From: "Bill Zhang" <bill.zhang@sybase.com>
Subject: Re: PowerDynamo and Open Client connections vs ODBC connections - HELP!!!!
Date: Wed, 29 Mar 2000 11:17:30 -0500
Lines: 90
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
NNTP-Posting-Host: zhangb-nt3.sybase.com 157.133.43.212
Message-ID: <347_$9TIDKcm$GA.52@forums.sybase.com>
References: <347_wlbGKKPm$GA.52@forums.sybase.com> <347_XV73nuPm$GA.298@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:25311
Article PK: 155419

Open Client connections are automatically set to CHAINED = on. The
autoCommit property in PowerDynamo may be used to set the chained mode to
off.

To set chained mode off, you can do:
<!--SCRIPT
connection.autoCommit = true;
-->

Another way to do it is to change your SP to anymode. So, it depends on how
you created your SP. The SP can be executed in Chained, Unchained, and
Anymode. To convert a SP to Anymode, you can do it in any isql session:

sp_procxmode [procname [, tranmode]]

tranmode values are: "chained", "unchained", "anymode"

Hope it helps.

"Ashish Mahajan" <ash@NOSPAM.com> wrote in message
news:XV73nuPm$GA.298@forums.sybase.com...
> Is your sp is trying to do ddl ??
> Here is what you could try ? Make sure that before you call the stored
> procedure you are in autocommit mode (I'm not sure whether you can 'tell'
> Dynamo to set the autocommit mode for you or not)
>
> "Brad McLeod" <brad.mcleod@worldnet.att.net> wrote in message
> news:wlbGKKPm$GA.52@forums.sybase.com...
> > Lance, Carson and Larry -
> >
> > Based upon a previous thread I posted regarding ASA and ASE environments
> for
> > our website DB and the issues we were having, I took your advice and did
> the
> > following:
> >
> > 1. Generated our website DB in an ASE 11.9.2 environment instead of ASA
> > 6.0.2
> > 2. Established an Open Client connection profile to the web DB instead
of
> > using ODBC.
> > 3. Created an Open Client connection from the website to the ASE 11.9.2
> > primary database.
> >
> > Here's is what is happening now!:( - Please see the attachment!
> >
> > Summary:
> >
> > PD pages executing stored procedures under an Open Client/ASE 11.9.2 PD
> > configuration, do not execute. Under an ODBC/ASE 11.9.2 PD
configuration
> > the do.
> > We have PD web pages that execute SQL and Stored Procedures against the
> ASE
> > 11.9.2 database. When accessing the PD web DB via ODBC, the pages
> executed
> > correctly and the data was retrieved as expected. Now that we've
switched
> > over to Open Client, we are experiencing failures with all of our stored
> > procedures executed by our PD web pages that use stored procedures.
> (Please
> > refer to the attachment for specifics!)
> >
> > Further, any stored procedures that use a 'Select Into' or 'Create'
> command
> > do not function under either ODBC or Open Client when the PD web DB is
in
> > ASE 11.9.2. When the PD web DB was in ASA and used an ODBC connection,
> they
> > worked!!
> >
> > Any ideas, insight, guidance would be appreciated. As I said, I took
all
> > your advice and this is where we are at now. I have to have this
> > application, website and supporting database's ready for beta testing in
3
> > DAYS!! HELP!!!
> >
> > TIA
> >
> > Brad McLeod
> > StoneHenge Partners
> >
> >
> >
>
>


Brad McLeod Posted on 2000-03-31 18:29:15.0Z
Newsgroups: sybase.public.easerver
From: "Brad McLeod" <brad.mcleod@worldnet.att.net>
Subject: Re: PowerDynamo and Open Client connections vs ODBC connections - HELP!!!!
Date: Fri, 31 Mar 2000 12:29:15 -0600
Lines: 113
X-Newsreader: Microsoft Outlook Express 4.72.3155.0
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0
NNTP-Posting-Host: ailsa-ded.webzone.net 208.152.102.253
Message-ID: <347_oxzHK$zm$GA.52@forums.sybase.com>
References: <347_wlbGKKPm$GA.52@forums.sybase.com> <347_XV73nuPm$GA.298@forums.sybase.com> <347_$9TIDKcm$GA.52@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:25063
Article PK: 154176

Bill -

Herein lies the problem!! We need for the connection to run in 'unchained'
mode so that we can execute 'select into' statements. The 'autocommit'
needs to be set to false as well. Based upon your thread, how do we
accomplish this? Set the sp's mode to 'unchained' and leave the PD Open
Client connection as is?

TIA

Brad McLeod
StoneHenge Partners

Bill Zhang wrote in message <$9TIDKcm$GA.52@forums.sybase.com>...
>Open Client connections are automatically set to CHAINED = on. The
>autoCommit property in PowerDynamo may be used to set the chained mode to
>off.
>
>To set chained mode off, you can do:
><!--SCRIPT
> connection.autoCommit = true;
>-->
>
>Another way to do it is to change your SP to anymode. So, it depends on
how
>you created your SP. The SP can be executed in Chained, Unchained, and
>Anymode. To convert a SP to Anymode, you can do it in any isql session:
>
>sp_procxmode [procname [, tranmode]]
>
>tranmode values are: "chained", "unchained", "anymode"
>
>Hope it helps.
>
>
>"Ashish Mahajan" <ash@NOSPAM.com> wrote in message
>news:XV73nuPm$GA.298@forums.sybase.com...
>> Is your sp is trying to do ddl ??
>> Here is what you could try ? Make sure that before you call the stored
>> procedure you are in autocommit mode (I'm not sure whether you can 'tell'
>> Dynamo to set the autocommit mode for you or not)
>>
>> "Brad McLeod" <brad.mcleod@worldnet.att.net> wrote in message
>> news:wlbGKKPm$GA.52@forums.sybase.com...
>> > Lance, Carson and Larry -
>> >
>> > Based upon a previous thread I posted regarding ASA and ASE
environments
>> for
>> > our website DB and the issues we were having, I took your advice and
did
>> the
>> > following:
>> >
>> > 1. Generated our website DB in an ASE 11.9.2 environment instead of
ASA
>> > 6.0.2
>> > 2. Established an Open Client connection profile to the web DB instead
>of
>> > using ODBC.
>> > 3. Created an Open Client connection from the website to the ASE
11.9.2
>> > primary database.
>> >
>> > Here's is what is happening now!:( - Please see the attachment!
>> >
>> > Summary:
>> >
>> > PD pages executing stored procedures under an Open Client/ASE 11.9.2 PD
>> > configuration, do not execute. Under an ODBC/ASE 11.9.2 PD
>configuration
>> > the do.
>> > We have PD web pages that execute SQL and Stored Procedures against the
>> ASE
>> > 11.9.2 database. When accessing the PD web DB via ODBC, the pages
>> executed
>> > correctly and the data was retrieved as expected. Now that we've
>switched
>> > over to Open Client, we are experiencing failures with all of our
stored
>> > procedures executed by our PD web pages that use stored procedures.
>> (Please
>> > refer to the attachment for specifics!)
>> >
>> > Further, any stored procedures that use a 'Select Into' or 'Create'
>> command
>> > do not function under either ODBC or Open Client when the PD web DB is
>in
>> > ASE 11.9.2. When the PD web DB was in ASA and used an ODBC connection,
>> they
>> > worked!!
>> >
>> > Any ideas, insight, guidance would be appreciated. As I said, I took
>all
>> > your advice and this is where we are at now. I have to have this
>> > application, website and supporting database's ready for beta testing
in
>3
>> > DAYS!! HELP!!!
>> >
>> > TIA
>> >
>> > Brad McLeod
>> > StoneHenge Partners
>> >
>> >
>> >
>>
>>
>
>


Lance Andersen Posted on 2000-03-31 20:57:55.0Z
Newsgroups: sybase.public.easerver
Date: Fri, 31 Mar 2000 15:57:55 -0500
From: Lance Andersen <lancea@sybase.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: PowerDynamo and Open Client connections vs ODBC connections - HELP!!!!
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 105
NNTP-Posting-Host: alder.sybase.com 157.133.125.15
Message-ID: <347_38E51153.185E8C41@sybase.com>
References: <347_wlbGKKPm$GA.52@forums.sybase.com> <347_XV73nuPm$GA.298@forums.sybase.com> <347_$9TIDKcm$GA.52@forums.sybase.com> <347_oxzHK$zm$GA.52@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:25040
Article PK: 155329

Brad,

I thought I answered your question via email...

let me know...

Lance

Brad McLeod wrote:
>
> Bill -
>
> Herein lies the problem!! We need for the connection to run in 'unchained'
> mode so that we can execute 'select into' statements. The 'autocommit'
> needs to be set to false as well. Based upon your thread, how do we
> accomplish this? Set the sp's mode to 'unchained' and leave the PD Open
> Client connection as is?
>
> TIA
>
> Brad McLeod
> StoneHenge Partners
>
> Bill Zhang wrote in message <$9TIDKcm$GA.52@forums.sybase.com>...
> >Open Client connections are automatically set to CHAINED = on. The
> >autoCommit property in PowerDynamo may be used to set the chained mode to
> >off.
> >
> >To set chained mode off, you can do:
> ><!--SCRIPT
> > connection.autoCommit = true;
> >-->
> >
> >Another way to do it is to change your SP to anymode. So, it depends on
> how
> >you created your SP. The SP can be executed in Chained, Unchained, and
> >Anymode. To convert a SP to Anymode, you can do it in any isql session:
> >
> >sp_procxmode [procname [, tranmode]]
> >
> >tranmode values are: "chained", "unchained", "anymode"
> >
> >Hope it helps.
> >
> >
> >"Ashish Mahajan" <ash@NOSPAM.com> wrote in message
> >news:XV73nuPm$GA.298@forums.sybase.com...
> >> Is your sp is trying to do ddl ??
> >> Here is what you could try ? Make sure that before you call the stored
> >> procedure you are in autocommit mode (I'm not sure whether you can 'tell'
> >> Dynamo to set the autocommit mode for you or not)
> >>
> >> "Brad McLeod" <brad.mcleod@worldnet.att.net> wrote in message
> >> news:wlbGKKPm$GA.52@forums.sybase.com...
> >> > Lance, Carson and Larry -
> >> >
> >> > Based upon a previous thread I posted regarding ASA and ASE
> environments
> >> for
> >> > our website DB and the issues we were having, I took your advice and
> did
> >> the
> >> > following:
> >> >
> >> > 1. Generated our website DB in an ASE 11.9.2 environment instead of
> ASA
> >> > 6.0.2
> >> > 2. Established an Open Client connection profile to the web DB instead
> >of
> >> > using ODBC.
> >> > 3. Created an Open Client connection from the website to the ASE
> 11.9.2
> >> > primary database.
> >> >
> >> > Here's is what is happening now!:( - Please see the attachment!
> >> >
> >> > Summary:
> >> >
> >> > PD pages executing stored procedures under an Open Client/ASE 11.9.2 PD
> >> > configuration, do not execute. Under an ODBC/ASE 11.9.2 PD
> >configuration
> >> > the do.
> >> > We have PD web pages that execute SQL and Stored Procedures against the
> >> ASE
> >> > 11.9.2 database. When accessing the PD web DB via ODBC, the pages
> >> executed
> >> > correctly and the data was retrieved as expected. Now that we've
> >switched
> >> > over to Open Client, we are experiencing failures with all of our
> stored
> >> > procedures executed by our PD web pages that use stored procedures.
> >> (Please
> >> > refer to the attachment for specifics!)
> >> >
> >> > Further, any stored procedures that use a 'Select Into' or 'Create'
> >> command
> >> > do not function under either ODBC or Open Client when the PD web DB is
> >in
> >> > ASE 11.9.2. When the PD web DB was in ASA and used an ODBC connection,
> >> they
> >> > worked!!
> >> >
> >> > Any ideas, insight, guidance would be appreciated. As I said, I took
> >all
> >> > your advice and this is where we are at now. I have to have this
> >> > application, website and supporting database's ready for beta testing
> in
> >3
> >> > DAYS!! HELP!!!
> >> >
> >> > TIA
> >> >
> >> > Brad McLeod
> >> > StoneHenge Partners
> >> >
> >> >
> >> >
> >>
> >>
> >
> >

--
===============================================================================
Lance J. Andersen Email: lancea@sybase.com
Sybase Product Support Engineering Phone:(781) 564-6336
77 South Bedford Street Fax: (781) 564-7001
Burlington, MA 01803

The Dark Knight Returns!!! Let's Go Penguins!!!
===============================================================================


Yong Song Posted on 2000-03-31 21:25:32.0Z
Newsgroups: sybase.public.easerver
Reply-To: "Yong Song" <ysong@stonehenge-ok.com>
From: "Yong Song" <ysong@stonehenge-ok.com>
Subject: Re: PowerDynamo and Open Client connections vs ODBC connections - HELP!!!!
Date: Fri, 31 Mar 2000 15:25:32 -0600
Lines: 117
Organization: Stonehenge
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
NNTP-Posting-Host: ailsa-ded.webzone.net 208.152.102.253
Message-ID: <347_Vznbng1m$GA.52@forums.sybase.com>
References: <347_wlbGKKPm$GA.52@forums.sybase.com> <347_XV73nuPm$GA.298@forums.sybase.com> <347_$9TIDKcm$GA.52@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:25034
Article PK: 228443

We set autoCommit = true; in PD script. Unfortunately, it corrupted our
database. Set SP to Anymode did not work for SP having "Select Into"
command. We got an message "Stored procedure ... may be run only in
unchained transaction mode. The 'SET CHAINED OFF' command will cause the
current session to use unchained transaction mode". Even we changed the SP
to Unchained by sp_procxmode, we still got the same error message.
It looks like stored proc works only under the Chained mode in PD. I hope I
am wrong. Any thought to solve the problem?

Thanks

Bill Zhang <bill.zhang@sybase.com> wrote in message
news:$9TIDKcm$GA.52@forums.sybase.com...
> Open Client connections are automatically set to CHAINED = on. The
> autoCommit property in PowerDynamo may be used to set the chained mode to
> off.
>
> To set chained mode off, you can do:
> <!--SCRIPT
> connection.autoCommit = true;
> -->
>
> Another way to do it is to change your SP to anymode. So, it depends on
how
> you created your SP. The SP can be executed in Chained, Unchained, and
> Anymode. To convert a SP to Anymode, you can do it in any isql session:
>
> sp_procxmode [procname [, tranmode]]
>
> tranmode values are: "chained", "unchained", "anymode"
>
> Hope it helps.
>
>
> "Ashish Mahajan" <ash@NOSPAM.com> wrote in message
> news:XV73nuPm$GA.298@forums.sybase.com...
> > Is your sp is trying to do ddl ??
> > Here is what you could try ? Make sure that before you call the stored
> > procedure you are in autocommit mode (I'm not sure whether you can
'tell'
> > Dynamo to set the autocommit mode for you or not)
> >
> > "Brad McLeod" <brad.mcleod@worldnet.att.net> wrote in message
> > news:wlbGKKPm$GA.52@forums.sybase.com...
> > > Lance, Carson and Larry -
> > >
> > > Based upon a previous thread I posted regarding ASA and ASE
environments
> > for
> > > our website DB and the issues we were having, I took your advice and
did
> > the
> > > following:
> > >
> > > 1. Generated our website DB in an ASE 11.9.2 environment instead of
ASA
> > > 6.0.2
> > > 2. Established an Open Client connection profile to the web DB
instead
> of
> > > using ODBC.
> > > 3. Created an Open Client connection from the website to the ASE
11.9.2
> > > primary database.
> > >
> > > Here's is what is happening now!:( - Please see the attachment!
> > >
> > > Summary:
> > >
> > > PD pages executing stored procedures under an Open Client/ASE 11.9.2
PD
> > > configuration, do not execute. Under an ODBC/ASE 11.9.2 PD
> configuration
> > > the do.
> > > We have PD web pages that execute SQL and Stored Procedures against
the
> > ASE
> > > 11.9.2 database. When accessing the PD web DB via ODBC, the pages
> > executed
> > > correctly and the data was retrieved as expected. Now that we've
> switched
> > > over to Open Client, we are experiencing failures with all of our
stored
> > > procedures executed by our PD web pages that use stored procedures.
> > (Please
> > > refer to the attachment for specifics!)
> > >
> > > Further, any stored procedures that use a 'Select Into' or 'Create'
> > command
> > > do not function under either ODBC or Open Client when the PD web DB is
> in
> > > ASE 11.9.2. When the PD web DB was in ASA and used an ODBC
connection,
> > they
> > > worked!!
> > >
> > > Any ideas, insight, guidance would be appreciated. As I said, I took
> all
> > > your advice and this is where we are at now. I have to have this
> > > application, website and supporting database's ready for beta testing
in
> 3
> > > DAYS!! HELP!!!
> > >
> > > TIA
> > >
> > > Brad McLeod
> > > StoneHenge Partners
> > >
> > >
> > >
> >
> >
>
>


Lance Andersen Posted on 2000-03-31 21:59:48.0Z
Newsgroups: sybase.public.easerver
Date: Fri, 31 Mar 2000 16:59:48 -0500
From: Lance Andersen <lancea@sybase.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: PowerDynamo and Open Client connections vs ODBC connections - HELP!!!!
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 31
NNTP-Posting-Host: alder.sybase.com 157.133.125.15
Message-ID: <347_38E51FD4.8F16EBE9@sybase.com>
References: <347_wlbGKKPm$GA.52@forums.sybase.com> <347_XV73nuPm$GA.298@forums.sybase.com> <347_$9TIDKcm$GA.52@forums.sybase.com> <347_Vznbng1m$GA.52@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:25027
Article PK: 228440


Yong Song wrote:
>
> We set autoCommit = true; in PD script. Unfortunately, it corrupted our
> database. Set SP to Anymode did not work for SP having "Select Into"
> command. We got an message "Stored procedure ... may be run only in
> unchained transaction mode. The 'SET CHAINED OFF' command will cause the
> current session to use unchained transaction mode". Even we changed the SP
> to Unchained by sp_procxmode, we still got the same error message.
> It looks like stored proc works only under the Chained mode in PD. I hope I
> am wrong. Any thought to solve the problem?
>

All this does is disable chained mode. Sounds like an ASE issue now.

Try running the sproc via tsql
and see if you encounter the error. Ribo can show you the TDS that is
being sent to ASE from PD.

Lance
===============================================================================
Lance J. Andersen Email: lancea@sybase.com
Sybase Product Support Engineering Phone:(781) 564-6336
77 South Bedford Street Fax: (781) 564-7001
Burlington, MA 01803

The Dark Knight Returns!!! Let's Go Penguins!!!
===============================================================================


Yong Song Posted on 2000-03-31 22:54:27.0Z
Newsgroups: sybase.public.easerver
Reply-To: "Yong Song" <ysong@stonehenge-ok.com>
From: "Yong Song" <ysong@stonehenge-ok.com>
Subject: Re: PowerDynamo and Open Client connections vs ODBC connections - HELP!!!!
Date: Fri, 31 Mar 2000 16:54:27 -0600
Lines: 46
Organization: Stonehenge
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
NNTP-Posting-Host: ailsa-ded.webzone.net 208.152.102.253
Message-ID: <347_AMX2ZS2m$GA.67@forums.sybase.com>
References: <347_wlbGKKPm$GA.52@forums.sybase.com> <347_XV73nuPm$GA.298@forums.sybase.com> <347_$9TIDKcm$GA.52@forums.sybase.com> <347_Vznbng1m$GA.52@forums.sybase.com> <347_38E51FD4.8F16EBE9@sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:25023
Article PK: 154156


Lance Andersen <lancea@sybase.com> wrote in message
news:38E51FD4.8F16EBE9@sybase.com...
> Yong Song wrote:
> >
> > We set autoCommit = true; in PD script. Unfortunately, it corrupted our
> > database. Set SP to Anymode did not work for SP having "Select Into"
> > command. We got an message "Stored procedure ... may be run only in
> > unchained transaction mode. The 'SET CHAINED OFF' command will cause the
> > current session to use unchained transaction mode". Even we changed the
SP
> > to Unchained by sp_procxmode, we still got the same error message.
> > It looks like stored proc works only under the Chained mode in PD. I
hope I
> > am wrong. Any thought to solve the problem?
> >
>
> All this does is disable chained mode. Sounds like an ASE issue now.
>
> Try running the sproc via tsql
> and see if you encounter the error. Ribo can show you the TDS that is
> being sent to ASE from PD.
>
> Lance
>

============================================================================
===
> Lance J. Andersen Email: lancea@sybase.com
> Sybase Product Support Engineering Phone:(781) 564-6336
> 77 South Bedford Street Fax: (781) 564-7001
> Burlington, MA 01803
>
> The Dark Knight Returns!!! Let's Go Penguins!!!
>
============================================================================
===

Yes, the proc works via tsql. I also tried sproc having only one query( with
or without Select into). The same thing happened.
By the way, could you tell me what TDS means?

Thanks

Yong


Andersen, Lance / Tonya Posted on 2000-04-01 16:17:56.0Z
Newsgroups: sybase.public.easerver
Date: Sat, 01 Apr 2000 08:17:56 -0800
From: "Andersen, Lance / Tonya" <lta@tiac.net>
X-Mailer: Mozilla 4.72 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: PowerDynamo and Open Client connections vs ODBC connections - HELP!!!!
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 54
NNTP-Posting-Host: 158.159.8.12
Message-ID: <347_38E62134.19DFF796@tiac.net>
References: <347_wlbGKKPm$GA.52@forums.sybase.com> <347_XV73nuPm$GA.298@forums.sybase.com> <347_$9TIDKcm$GA.52@forums.sybase.com> <347_Vznbng1m$GA.52@forums.sybase.com> <347_38E51FD4.8F16EBE9@sybase.com> <347_AMX2ZS2m$GA.67@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:25009
Article PK: 154142

TDS is the protocol used to speak to ASE, RepServer, OPenSErver..etc

I would suggest next to download Ribo from the jConnect HOme page,
point your PD app to it which in turn will point to ASE. This will
let us see the TDS (queries, token types) being sent to ASE.

Please if you can zip up your proc and bcp dump of the data along with
the schema for the table and we will try and take a look. At the
same time, please open a case with Tech Support.

thanks
Lance

Yong Song wrote:
>
> Lance Andersen <lancea@sybase.com> wrote in message
> news:38E51FD4.8F16EBE9@sybase.com...
> > Yong Song wrote:
> > >
> > > We set autoCommit = true; in PD script. Unfortunately, it corrupted our
> > > database. Set SP to Anymode did not work for SP having "Select Into"
> > > command. We got an message "Stored procedure ... may be run only in
> > > unchained transaction mode. The 'SET CHAINED OFF' command will cause the
> > > current session to use unchained transaction mode". Even we changed the
> SP
> > > to Unchained by sp_procxmode, we still got the same error message.
> > > It looks like stored proc works only under the Chained mode in PD. I
> hope I
> > > am wrong. Any thought to solve the problem?
> > >
> >
> > All this does is disable chained mode. Sounds like an ASE issue now.
> >
> > Try running the sproc via tsql
> > and see if you encounter the error. Ribo can show you the TDS that is
> > being sent to ASE from PD.
> >
> > Lance
> >
> ============================================================================
> ===
> > Lance J. Andersen Email: lancea@sybase.com
> > Sybase Product Support Engineering Phone:(781) 564-6336
> > 77 South Bedford Street Fax: (781) 564-7001
> > Burlington, MA 01803
> >
> > The Dark Knight Returns!!! Let's Go Penguins!!!
> >
> ============================================================================
> ===
>
> Yes, the proc works via tsql. I also tried sproc having only one query( with
> or without Select into). The same thing happened.
> By the way, could you tell me what TDS means?
>
> Thanks
>
> Yong


Yong Song Posted on 2000-04-03 22:01:09.0Z
Newsgroups: sybase.public.easerver
Reply-To: "Yong Song" <ysong@stonehenge-ok.com>
From: "Yong Song" <ysong@stonehenge-ok.com>
Subject: Re: PowerDynamo and Open Client connections vs ODBC connections - HELP!!!!
Date: Mon, 3 Apr 2000 17:01:09 -0500
Lines: 88
Organization: Stonehenge
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
NNTP-Posting-Host: ailsa-ded.webzone.net 208.152.102.253
Message-ID: <347_5efDsibn$GA.266@forums.sybase.com>
References: <347_wlbGKKPm$GA.52@forums.sybase.com> <347_XV73nuPm$GA.298@forums.sybase.com> <347_$9TIDKcm$GA.52@forums.sybase.com> <347_Vznbng1m$GA.52@forums.sybase.com> <347_38E51FD4.8F16EBE9@sybase.com> <347_AMX2ZS2m$GA.67@forums.sybase.com> <347_38E62134.19DFF796@tiac.net>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:24870
Article PK: 155290

Hi, Lance,

Glad to hear from you.

I also doubt that is an ASE issue because it happens on every proc having
select into, even a proc only has "Select * into #MyTemp from ar_store"
command. It seems to be a generic problem. I am not a ASE DBA. Could you
point me to somewhere I may find the solution?

I downloaded Ribo but I don't know how to point my PD app to Ribo then to
ASE. What computer should I run Ribo on, client PC or Server?
Is the PD port assigned to the listen_port? I tried command Ribo -l 9000 -s
localhost -gui. Ribo gave an error message "The port is in use". 9000 is our
PD port.

Thanks for your help.

Yong

Andersen, Lance / Tonya <lta@tiac.net> wrote in message
news:38E62134.19DFF796@tiac.net...
> TDS is the protocol used to speak to ASE, RepServer, OPenSErver..etc
>
> I would suggest next to download Ribo from the jConnect HOme page,
> point your PD app to it which in turn will point to ASE. This will
> let us see the TDS (queries, token types) being sent to ASE.
>
> Please if you can zip up your proc and bcp dump of the data along with
> the schema for the table and we will try and take a look. At the
> same time, please open a case with Tech Support.
>
> thanks
> Lance
>
> Yong Song wrote:
> >
> > Lance Andersen <lancea@sybase.com> wrote in message
> > news:38E51FD4.8F16EBE9@sybase.com...
> > > Yong Song wrote:
> > > >
> > > > We set autoCommit = true; in PD script. Unfortunately, it corrupted
our
> > > > database. Set SP to Anymode did not work for SP having "Select
Into"
> > > > command. We got an message "Stored procedure ... may be run only in
> > > > unchained transaction mode. The 'SET CHAINED OFF' command will cause
the
> > > > current session to use unchained transaction mode". Even we changed
the
> > SP
> > > > to Unchained by sp_procxmode, we still got the same error message.
> > > > It looks like stored proc works only under the Chained mode in PD. I
> > hope I
> > > > am wrong. Any thought to solve the problem?
> > > >
> > >
> > > All this does is disable chained mode. Sounds like an ASE issue now.
> > >
> > > Try running the sproc via tsql
> > > and see if you encounter the error. Ribo can show you the TDS that is
> > > being sent to ASE from PD.
> > >
> > > Lance
> > >
> >
============================================================================
> > ===
> > > Lance J. Andersen Email: lancea@sybase.com
> > > Sybase Product Support Engineering Phone:(781) 564-6336
> > > 77 South Bedford Street Fax: (781) 564-7001
> > > Burlington, MA 01803
> > >
> > > The Dark Knight Returns!!! Let's Go Penguins!!!
> > >
> >
============================================================================
> > ===
> >
> > Yes, the proc works via tsql. I also tried sproc having only one
uery( with
> > or without Select into). The same thing happened.
> > By the way, could you tell me what TDS means?
> >
> > Thanks
> >
> > Yong


Lance Andersen Posted on 2000-04-04 11:46:04.0Z
Newsgroups: sybase.public.easerver
Date: Tue, 04 Apr 2000 07:46:04 -0400
From: Lance Andersen <lancea@sybase.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: PowerDynamo and Open Client connections vs ODBC connections - HELP!!!!
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 119
NNTP-Posting-Host: alder.sybase.com 157.133.125.15
Message-ID: <347_38E9D5FC.E3DB4B93@sybase.com>
References: <347_wlbGKKPm$GA.52@forums.sybase.com> <347_XV73nuPm$GA.298@forums.sybase.com> <347_$9TIDKcm$GA.52@forums.sybase.com> <347_Vznbng1m$GA.52@forums.sybase.com> <347_38E51FD4.8F16EBE9@sybase.com> <347_AMX2ZS2m$GA.67@forums.sybase.com> <347_38E62134.19DFF796@tiac.net> <347_5efDsibn$GA.266@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:24842
Article PK: 155265

Yong,

What is the exact error you get when you run the sproc?

Ribo can run anywhere you like.

Port 9000 is usually used by Jaguar. What you do is this:

Point PD connections to use port 5005 (the default listener port for
Ribo), Start Ribo specifying the host and port that that your ASE server
is running on.

Run your query and then when complete, use Ribo to translate the binary
stream to an ascii human readable file.

This will show you the resultsets, queries and errors that have gone
back and forth between your PD client and ASE.


I have just tried a sproc which was

create proc procTest as
select * into #foo from pubs2..authors
select * from #foo
go


My PD script:
<html>
<title>test</title>
<body>
<h1>xxx</h1>
<!--Script
connection.autoCommit=true;
qu= connection.createQuery("test..procTest");
if(qu.GetErrorCode())
{
document.writeln("<strong>error:</strong>" +qu.GetErrorInfo()+
"<p>");
}
while(qu.MoveNext())
{
document.writeln(qu.GetValue(1) +"<br>");
}
-->
</body>
</html>

this works fine.

Regards,
Lance

Yong Song wrote:
>
> Hi, Lance,
>
> Glad to hear from you.
>
> I also doubt that is an ASE issue because it happens on every proc having
> select into, even a proc only has "Select * into #MyTemp from ar_store"
> command. It seems to be a generic problem. I am not a ASE DBA. Could you
> point me to somewhere I may find the solution?
>
> I downloaded Ribo but I don't know how to point my PD app to Ribo then to
> ASE. What computer should I run Ribo on, client PC or Server?
> Is the PD port assigned to the listen_port? I tried command Ribo -l 9000 -s
> localhost -gui. Ribo gave an error message "The port is in use". 9000 is our
> PD port.
>
> Thanks for your help.
>
> Yong
>
> Andersen, Lance / Tonya <lta@tiac.net> wrote in message
> news:38E62134.19DFF796@tiac.net...
> > TDS is the protocol used to speak to ASE, RepServer, OPenSErver..etc
> >
> > I would suggest next to download Ribo from the jConnect HOme page,
> > point your PD app to it which in turn will point to ASE. This will
> > let us see the TDS (queries, token types) being sent to ASE.
> >
> > Please if you can zip up your proc and bcp dump of the data along with
> > the schema for the table and we will try and take a look. At the
> > same time, please open a case with Tech Support.
> >
> > thanks
> > Lance
> >
> > Yong Song wrote:
> > >
> > > Lance Andersen <lancea@sybase.com> wrote in message
> > > news:38E51FD4.8F16EBE9@sybase.com...
> > > > Yong Song wrote:
> > > > >
> > > > > We set autoCommit = true; in PD script. Unfortunately, it corrupted
> our
> > > > > database. Set SP to Anymode did not work for SP having "Select
> Into"
> > > > > command. We got an message "Stored procedure ... may be run only in
> > > > > unchained transaction mode. The 'SET CHAINED OFF' command will cause
> the
> > > > > current session to use unchained transaction mode". Even we changed
> the
> > > SP
> > > > > to Unchained by sp_procxmode, we still got the same error message.
> > > > > It looks like stored proc works only under the Chained mode in PD. I
> > > hope I
> > > > > am wrong. Any thought to solve the problem?
> > > > >
> > > >
> > > > All this does is disable chained mode. Sounds like an ASE issue now.
> > > >
> > > > Try running the sproc via tsql
> > > > and see if you encounter the error. Ribo can show you the TDS that is
> > > > being sent to ASE from PD.
> > > >
> > > > Lance
> > > >
> > >
> ============================================================================
> > > ===
> > > > Lance J. Andersen Email: lancea@sybase.com
> > > > Sybase Product Support Engineering Phone:(781) 564-6336
> > > > 77 South Bedford Street Fax: (781) 564-7001
> > > > Burlington, MA 01803
> > > >
> > > > The Dark Knight Returns!!! Let's Go Penguins!!!
> > > >
> > >
> ============================================================================
> > > ===
> > >
> > > Yes, the proc works via tsql. I also tried sproc having only one
> uery( with
> > > or without Select into). The same thing happened.
> > > By the way, could you tell me what TDS means?
> > >
> > > Thanks
> > >
> > > Yong

--
===============================================================================
Lance J. Andersen Email: lancea@sybase.com
Sybase Product Support Engineering Phone:(781) 564-6336
77 South Bedford Street Fax: (781) 564-7001
Burlington, MA 01803

The Dark Knight Returns!!! Let's Go Penguins!!!
===============================================================================


Yong Song Posted on 2000-04-04 15:32:58.0Z
Newsgroups: sybase.public.easerver
Reply-To: "Yong Song" <ysong@stonehenge-ok.com>
From: "Yong Song" <ysong@stonehenge-ok.com>
Subject: Re: PowerDynamo and Open Client connections vs ODBC connections - HELP!!!!
Date: Tue, 4 Apr 2000 10:32:58 -0500
Lines: 228
Organization: Stonehenge
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
NNTP-Posting-Host: ailsa-ded.webzone.net 208.152.102.253
Message-ID: <347_YLJ9cukn$GA.299@forums.sybase.com>
References: <347_wlbGKKPm$GA.52@forums.sybase.com> <347_XV73nuPm$GA.298@forums.sybase.com> <347_$9TIDKcm$GA.52@forums.sybase.com> <347_Vznbng1m$GA.52@forums.sybase.com> <347_38E51FD4.8F16EBE9@sybase.com> <347_AMX2ZS2m$GA.67@forums.sybase.com> <347_38E62134.19DFF796@tiac.net> <347_5efDsibn$GA.266@forums.sybase.com> <347_38E9D5FC.E3DB4B93@sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:24824
Article PK: 154036

Thanks, Lance.

The error message is:
Stored procedure 'sp_TEST' may be run only in unchained transaction mode.
The 'SET CHAINED OFF' command will cause the current session to use
unchained transaction mode.

The error code I got from PD is -1.

The test script is:
<%@ LANGUAGE=JavaScript %>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>
<META NAME=SERVERLANGUAGE CONTENT=JavaScript HTTP-EQUIV=PowerSiteData>
</HEAD>
<BODY>
<%
var MyConnection = site.GetConnection("Intelimatrix");
var sSQL = "";
var MyQuery = MyConnection.CreateQuery();
sSQL = "EXEC sp_TEST";
document.writeln(sSQL);
MyQuery.SetSQL(sSQL);
MyQuery.Execute();
if (MyQuery.GetErrorCode())
{
document.write(MyQuery.GetErrorCode() + " -- " +
MyQuery.GetErrorInfo());
return;
}
else
document.writeln("Success!");
%>
</BODY>
</HTML>

sproc:
CREATE PROCEDURE dbo.sp_test;1
AS
BEGIN
select * into #tempTB
from ar_store where ar_client_id = 1
END

I didn't put MyConnection.autoCommit = true in the script. Our database
corrupted just after I tested another sproc having select into. It could be
an occincidence but I don't want to take the risk.

I will follow your instruction to use Ribo and let you know the result.

Thanks again.

Yong

Lance Andersen <lancea@sybase.com> wrote in message
news:38E9D5FC.E3DB4B93@sybase.com...
> Yong,
>
> What is the exact error you get when you run the sproc?
>
> Ribo can run anywhere you like.
>
> Port 9000 is usually used by Jaguar. What you do is this:
>
> Point PD connections to use port 5005 (the default listener port for
> Ribo), Start Ribo specifying the host and port that that your ASE server
> is running on.
>
> Run your query and then when complete, use Ribo to translate the binary
> stream to an ascii human readable file.
>
> This will show you the resultsets, queries and errors that have gone
> back and forth between your PD client and ASE.
>
>
> I have just tried a sproc which was
>
> create proc procTest as
> select * into #foo from pubs2..authors
> select * from #foo
> go
>
>
> My PD script:
> <html>
> <title>test</title>
> <body>
> <h1>xxx</h1>
> <!--Script
> connection.autoCommit=true;
> qu= connection.createQuery("test..procTest");
> if(qu.GetErrorCode())
> {
> document.writeln("<strong>error:</strong>" +qu.GetErrorInfo()+
> "<p>");
> }
> while(qu.MoveNext())
> {
> document.writeln(qu.GetValue(1) +"<br>");
> }
> -->
> </body>
> </html>
>
> this works fine.
>
> Regards,
> Lance
>
> Yong Song wrote:
> >
> > Hi, Lance,
> >
> > Glad to hear from you.
> >
> > I also doubt that is an ASE issue because it happens on every proc
having
> > select into, even a proc only has "Select * into #MyTemp from ar_store"
> > command. It seems to be a generic problem. I am not a ASE DBA. Could you
> > point me to somewhere I may find the solution?
> >
> > I downloaded Ribo but I don't know how to point my PD app to Ribo then
to
> > ASE. What computer should I run Ribo on, client PC or Server?
> > Is the PD port assigned to the listen_port? I tried command Ribo -l
9000 -s
> > localhost -gui. Ribo gave an error message "The port is in use". 9000 is
our
> > PD port.
> >
> > Thanks for your help.
> >
> > Yong
> >
> > Andersen, Lance / Tonya <lta@tiac.net> wrote in message
> > news:38E62134.19DFF796@tiac.net...
> > > TDS is the protocol used to speak to ASE, RepServer, OPenSErver..etc
> > >
> > > I would suggest next to download Ribo from the jConnect HOme page,
> > > point your PD app to it which in turn will point to ASE. This will
> > > let us see the TDS (queries, token types) being sent to ASE.
> > >
> > > Please if you can zip up your proc and bcp dump of the data along with
> > > the schema for the table and we will try and take a look. At the
> > > same time, please open a case with Tech Support.
> > >
> > > thanks
> > > Lance
> > >
> > > Yong Song wrote:
> > > >
> > > > Lance Andersen <lancea@sybase.com> wrote in message
> > > > news:38E51FD4.8F16EBE9@sybase.com...
> > > > > Yong Song wrote:
> > > > > >
> > > > > > We set autoCommit = true; in PD script. Unfortunately, it
corrupted
> > our
> > > > > > database. Set SP to Anymode did not work for SP having "Select
> > Into"
> > > > > > command. We got an message "Stored procedure ... may be run only
in
> > > > > > unchained transaction mode. The 'SET CHAINED OFF' command will
cause
> > the
> > > > > > current session to use unchained transaction mode". Even we
changed
> > the
> > > > SP
> > > > > > to Unchained by sp_procxmode, we still got the same error
message.
> > > > > > It looks like stored proc works only under the Chained mode in
PD. I
> > > > hope I
> > > > > > am wrong. Any thought to solve the problem?
> > > > > >
> > > > >
> > > > > All this does is disable chained mode. Sounds like an ASE issue
now.
> > > > >
> > > > > Try running the sproc via tsql
> > > > > and see if you encounter the error. Ribo can show you the TDS
that is
> > > > > being sent to ASE from PD.
> > > > >
> > > > > Lance
> > > > >
> > > >
> >
============================================================================
> > > > ===
> > > > > Lance J. Andersen Email: lancea@sybase.com
> > > > > Sybase Product Support Engineering Phone:(781) 564-6336
> > > > > 77 South Bedford Street Fax: (781) 564-7001
> > > > > Burlington, MA 01803
> > > > >
> > > > > The Dark Knight Returns!!! Let's Go Penguins!!!
> > > > >
> > > >
> >
============================================================================
> > > > ===
> > > >
> > > > Yes, the proc works via tsql. I also tried sproc having only one
> > uery( with
> > > > or without Select into). The same thing happened.
> > > > By the way, could you tell me what TDS means?
> > > >
> > > > Thanks
> > > >
> > > > Yong
>
> --
>

============================================================================
===
> Lance J. Andersen Email: lancea@sybase.com
> Sybase Product Support Engineering Phone:(781) 564-6336
> 77 South Bedford Street Fax: (781) 564-7001
> Burlington, MA 01803
>
> The Dark Knight Returns!!! Let's Go Penguins!!!
>
============================================================================
===


Lance Andersen Posted on 2000-04-04 15:48:19.0Z
Newsgroups: sybase.public.easerver
Date: Tue, 04 Apr 2000 11:48:19 -0400
From: Lance Andersen <lancea@sybase.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: PowerDynamo and Open Client connections vs ODBC connections - HELP!!!!
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 189
NNTP-Posting-Host: alder.sybase.com 157.133.125.15
Message-ID: <347_38EA0EC3.1AA0524A@sybase.com>
References: <347_wlbGKKPm$GA.52@forums.sybase.com> <347_XV73nuPm$GA.298@forums.sybase.com> <347_$9TIDKcm$GA.52@forums.sybase.com> <347_Vznbng1m$GA.52@forums.sybase.com> <347_38E51FD4.8F16EBE9@sybase.com> <347_AMX2ZS2m$GA.67@forums.sybase.com> <347_38E62134.19DFF796@tiac.net> <347_5efDsibn$GA.266@forums.sybase.com> <347_38E9D5FC.E3DB4B93@sybase.com> <347_YLJ9cukn$GA.299@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:24818
Article PK: 154031

You are going to want to run with autoCommit as in my example.

There are restrictions with what you can do in chained mode.

Yong Song wrote:
>
> Thanks, Lance.
>
> The error message is:
> Stored procedure 'sp_TEST' may be run only in unchained transaction mode.
> The 'SET CHAINED OFF' command will cause the current session to use
> unchained transaction mode.
>
> The error code I got from PD is -1.
>
> The test script is:
> <%@ LANGUAGE=JavaScript %>
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
> <HTML>
> <HEAD>
> <META NAME=SERVERLANGUAGE CONTENT=JavaScript HTTP-EQUIV=PowerSiteData>
> </HEAD>
> <BODY>
> <%
> var MyConnection = site.GetConnection("Intelimatrix");
> var sSQL = "";
> var MyQuery = MyConnection.CreateQuery();
> sSQL = "EXEC sp_TEST";
> document.writeln(sSQL);
> MyQuery.SetSQL(sSQL);
> MyQuery.Execute();
> if (MyQuery.GetErrorCode())
> {
> document.write(MyQuery.GetErrorCode() + " -- " +
> MyQuery.GetErrorInfo());
> return;
> }
> else
> document.writeln("Success!");
> %>
> </BODY>
> </HTML>
>
> sproc:
> CREATE PROCEDURE dbo.sp_test;1
> AS
> BEGIN
> select * into #tempTB
> from ar_store where ar_client_id = 1
> END
>
> I didn't put MyConnection.autoCommit = true in the script. Our database
> corrupted just after I tested another sproc having select into. It could be
> an occincidence but I don't want to take the risk.
>
> I will follow your instruction to use Ribo and let you know the result.
>
> Thanks again.
>
> Yong
>
> Lance Andersen <lancea@sybase.com> wrote in message
> news:38E9D5FC.E3DB4B93@sybase.com...
> > Yong,
> >
> > What is the exact error you get when you run the sproc?
> >
> > Ribo can run anywhere you like.
> >
> > Port 9000 is usually used by Jaguar. What you do is this:
> >
> > Point PD connections to use port 5005 (the default listener port for
> > Ribo), Start Ribo specifying the host and port that that your ASE server
> > is running on.
> >
> > Run your query and then when complete, use Ribo to translate the binary
> > stream to an ascii human readable file.
> >
> > This will show you the resultsets, queries and errors that have gone
> > back and forth between your PD client and ASE.
> >
> >
> > I have just tried a sproc which was
> >
> > create proc procTest as
> > select * into #foo from pubs2..authors
> > select * from #foo
> > go
> >
> >
> > My PD script:
> > <html>
> > <title>test</title>
> > <body>
> > <h1>xxx</h1>
> > <!--Script
> > connection.autoCommit=true;
> > qu= connection.createQuery("test..procTest");
> > if(qu.GetErrorCode())
> > {
> > document.writeln("<strong>error:</strong>" +qu.GetErrorInfo()+
> > "<p>");
> > }
> > while(qu.MoveNext())
> > {
> > document.writeln(qu.GetValue(1) +"<br>");
> > }
> > -->
> > </body>
> > </html>
> >
> > this works fine.
> >
> > Regards,
> > Lance
> >
> > Yong Song wrote:
> > >
> > > Hi, Lance,
> > >
> > > Glad to hear from you.
> > >
> > > I also doubt that is an ASE issue because it happens on every proc
> having
> > > select into, even a proc only has "Select * into #MyTemp from ar_store"
> > > command. It seems to be a generic problem. I am not a ASE DBA. Could you
> > > point me to somewhere I may find the solution?
> > >
> > > I downloaded Ribo but I don't know how to point my PD app to Ribo then
> to
> > > ASE. What computer should I run Ribo on, client PC or Server?
> > > Is the PD port assigned to the listen_port? I tried command Ribo -l
> 9000 -s
> > > localhost -gui. Ribo gave an error message "The port is in use". 9000 is
> our
> > > PD port.
> > >
> > > Thanks for your help.
> > >
> > > Yong
> > >
> > > Andersen, Lance / Tonya <lta@tiac.net> wrote in message
> > > news:38E62134.19DFF796@tiac.net...
> > > > TDS is the protocol used to speak to ASE, RepServer, OPenSErver..etc
> > > >
> > > > I would suggest next to download Ribo from the jConnect HOme page,
> > > > point your PD app to it which in turn will point to ASE. This will
> > > > let us see the TDS (queries, token types) being sent to ASE.
> > > >
> > > > Please if you can zip up your proc and bcp dump of the data along with
> > > > the schema for the table and we will try and take a look. At the
> > > > same time, please open a case with Tech Support.
> > > >
> > > > thanks
> > > > Lance
> > > >
> > > > Yong Song wrote:
> > > > >
> > > > > Lance Andersen <lancea@sybase.com> wrote in message
> > > > > news:38E51FD4.8F16EBE9@sybase.com...
> > > > > > Yong Song wrote:
> > > > > > >
> > > > > > > We set autoCommit = true; in PD script. Unfortunately, it
> corrupted
> > > our
> > > > > > > database. Set SP to Anymode did not work for SP having "Select
> > > Into"
> > > > > > > command. We got an message "Stored procedure ... may be run only
> in
> > > > > > > unchained transaction mode. The 'SET CHAINED OFF' command will
> cause
> > > the
> > > > > > > current session to use unchained transaction mode". Even we
> changed
> > > the
> > > > > SP
> > > > > > > to Unchained by sp_procxmode, we still got the same error
> message.
> > > > > > > It looks like stored proc works only under the Chained mode in
> PD. I
> > > > > hope I
> > > > > > > am wrong. Any thought to solve the problem?
> > > > > > >
> > > > > >
> > > > > > All this does is disable chained mode. Sounds like an ASE issue
> now.
> > > > > >
> > > > > > Try running the sproc via tsql
> > > > > > and see if you encounter the error. Ribo can show you the TDS
> that is
> > > > > > being sent to ASE from PD.
> > > > > >
> > > > > > Lance
> > > > > >
> > > > >
> > >
> ============================================================================
> > > > > ===
> > > > > > Lance J. Andersen Email: lancea@sybase.com
> > > > > > Sybase Product Support Engineering Phone:(781) 564-6336
> > > > > > 77 South Bedford Street Fax: (781) 564-7001
> > > > > > Burlington, MA 01803
> > > > > >
> > > > > > The Dark Knight Returns!!! Let's Go Penguins!!!
> > > > > >
> > > > >
> > >
> ============================================================================
> > > > > ===
> > > > >
> > > > > Yes, the proc works via tsql. I also tried sproc having only one
> > > uery( with
> > > > > or without Select into). The same thing happened.
> > > > > By the way, could you tell me what TDS means?
> > > > >
> > > > > Thanks
> > > > >
> > > > > Yong
> >
> > --
> >
> ============================================================================
> ===
> > Lance J. Andersen Email: lancea@sybase.com
> > Sybase Product Support Engineering Phone:(781) 564-6336
> > 77 South Bedford Street Fax: (781) 564-7001
> > Burlington, MA 01803
> >
> > The Dark Knight Returns!!! Let's Go Penguins!!!
> >
> ============================================================================
> ===

--
===============================================================================
Lance J. Andersen Email: lancea@sybase.com
Sybase Product Support Engineering Phone:(781) 564-6336
77 South Bedford Street Fax: (781) 564-7001
Burlington, MA 01803

The Dark Knight Returns!!! Let's Go Penguins!!!
===============================================================================


Yong Song Posted on 2000-04-04 20:36:39.0Z
Newsgroups: sybase.public.easerver
Reply-To: "Yong Song" <ysong@stonehenge-ok.com>
From: "Yong Song" <ysong@stonehenge-ok.com>
Subject: Re: PowerDynamo and Open Client connections vs ODBC connections - HELP!!!!
Date: Tue, 4 Apr 2000 15:36:39 -0500
Lines: 284
Organization: Stonehenge
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
NNTP-Posting-Host: ailsa-ded.webzone.net 208.152.102.253
Message-ID: <347_G81GMYnn$GA.299@forums.sybase.com>
References: <347_wlbGKKPm$GA.52@forums.sybase.com> <347_XV73nuPm$GA.298@forums.sybase.com> <347_$9TIDKcm$GA.52@forums.sybase.com> <347_Vznbng1m$GA.52@forums.sybase.com> <347_38E51FD4.8F16EBE9@sybase.com> <347_AMX2ZS2m$GA.67@forums.sybase.com> <347_38E62134.19DFF796@tiac.net> <347_5efDsibn$GA.266@forums.sybase.com> <347_38E9D5FC.E3DB4B93@sybase.com> <347_YLJ9cukn$GA.299@forums.sybase.com> <347_38EA0EC3.1AA0524A@sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:24778
Article PK: 153991

Hi, Lance,

I took your advice adding connection.autoCommit = true in the script. It
worked!
So it meant the setting autoCommit = true might not be a piece of the
database corruption puzzle.

Thank you very much. You gave us a hugh help.

Best regards,

Yong

Lance Andersen <lancea@sybase.com> wrote in message
news:38EA0EC3.1AA0524A@sybase.com...
> You are going to want to run with autoCommit as in my example.
>
> There are restrictions with what you can do in chained mode.
>
> Yong Song wrote:
> >
> > Thanks, Lance.
> >
> > The error message is:
> > Stored procedure 'sp_TEST' may be run only in unchained transaction
mode.
> > The 'SET CHAINED OFF' command will cause the current session to use
> > unchained transaction mode.
> >
> > The error code I got from PD is -1.
> >
> > The test script is:
> > <%@ LANGUAGE=JavaScript %>
> > <!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
> > <HTML>
> > <HEAD>
> > <META NAME=SERVERLANGUAGE CONTENT=JavaScript
HTTP-EQUIV=PowerSiteData>
> > </HEAD>
> > <BODY>
> > <%
> > var MyConnection = site.GetConnection("Intelimatrix");
> > var sSQL = "";
> > var MyQuery = MyConnection.CreateQuery();
> > sSQL = "EXEC sp_TEST";
> > document.writeln(sSQL);
> > MyQuery.SetSQL(sSQL);
> > MyQuery.Execute();
> > if (MyQuery.GetErrorCode())
> > {
> > document.write(MyQuery.GetErrorCode() + " -- " +
> > MyQuery.GetErrorInfo());
> > return;
> > }
> > else
> > document.writeln("Success!");
> > %>
> > </BODY>
> > </HTML>
> >
> > sproc:
> > CREATE PROCEDURE dbo.sp_test;1
> > AS
> > BEGIN
> > select * into #tempTB
> > from ar_store where ar_client_id = 1
> > END
> >
> > I didn't put MyConnection.autoCommit = true in the script. Our database
> > corrupted just after I tested another sproc having select into. It could
be
> > an occincidence but I don't want to take the risk.
> >
> > I will follow your instruction to use Ribo and let you know the result.
> >
> > Thanks again.
> >
> > Yong
> >
> > Lance Andersen <lancea@sybase.com> wrote in message
> > news:38E9D5FC.E3DB4B93@sybase.com...
> > > Yong,
> > >
> > > What is the exact error you get when you run the sproc?
> > >
> > > Ribo can run anywhere you like.
> > >
> > > Port 9000 is usually used by Jaguar. What you do is this:
> > >
> > > Point PD connections to use port 5005 (the default listener port for
> > > Ribo), Start Ribo specifying the host and port that that your ASE
server
> > > is running on.
> > >
> > > Run your query and then when complete, use Ribo to translate the
binary
> > > stream to an ascii human readable file.
> > >
> > > This will show you the resultsets, queries and errors that have gone
> > > back and forth between your PD client and ASE.
> > >
> > >
> > > I have just tried a sproc which was
> > >
> > > create proc procTest as
> > > select * into #foo from pubs2..authors
> > > select * from #foo
> > > go
> > >
> > >
> > > My PD script:
> > > <html>
> > > <title>test</title>
> > > <body>
> > > <h1>xxx</h1>
> > > <!--Script
> > > connection.autoCommit=true;
> > > qu= connection.createQuery("test..procTest");
> > > if(qu.GetErrorCode())
> > > {
> > > document.writeln("<strong>error:</strong>" +qu.GetErrorInfo()+
> > > "<p>");
> > > }
> > > while(qu.MoveNext())
> > > {
> > > document.writeln(qu.GetValue(1) +"<br>");
> > > }
> > > -->
> > > </body>
> > > </html>
> > >
> > > this works fine.
> > >
> > > Regards,
> > > Lance
> > >
> > > Yong Song wrote:
> > > >
> > > > Hi, Lance,
> > > >
> > > > Glad to hear from you.
> > > >
> > > > I also doubt that is an ASE issue because it happens on every proc
> > having
> > > > select into, even a proc only has "Select * into #MyTemp from
ar_store"
> > > > command. It seems to be a generic problem. I am not a ASE DBA. Could
you
> > > > point me to somewhere I may find the solution?
> > > >
> > > > I downloaded Ribo but I don't know how to point my PD app to Ribo
then
> > to
> > > > ASE. What computer should I run Ribo on, client PC or Server?
> > > > Is the PD port assigned to the listen_port? I tried command Ribo -l
> > 9000 -s
> > > > localhost -gui. Ribo gave an error message "The port is in use".
9000 is
> > our
> > > > PD port.
> > > >
> > > > Thanks for your help.
> > > >
> > > > Yong
> > > >
> > > > Andersen, Lance / Tonya <lta@tiac.net> wrote in message
> > > > news:38E62134.19DFF796@tiac.net...
> > > > > TDS is the protocol used to speak to ASE, RepServer,
OPenSErver..etc
> > > > >
> > > > > I would suggest next to download Ribo from the jConnect HOme page,
> > > > > point your PD app to it which in turn will point to ASE. This
will
> > > > > let us see the TDS (queries, token types) being sent to ASE.
> > > > >
> > > > > Please if you can zip up your proc and bcp dump of the data along
with
> > > > > the schema for the table and we will try and take a look. At the
> > > > > same time, please open a case with Tech Support.
> > > > >
> > > > > thanks
> > > > > Lance
> > > > >
> > > > > Yong Song wrote:
> > > > > >
> > > > > > Lance Andersen <lancea@sybase.com> wrote in message
> > > > > > news:38E51FD4.8F16EBE9@sybase.com...
> > > > > > > Yong Song wrote:
> > > > > > > >
> > > > > > > > We set autoCommit = true; in PD script. Unfortunately, it
> > corrupted
> > > > our
> > > > > > > > database. Set SP to Anymode did not work for SP having
"Select
> > > > Into"
> > > > > > > > command. We got an message "Stored procedure ... may be run
only
> > in
> > > > > > > > unchained transaction mode. The 'SET CHAINED OFF' command
will
> > cause
> > > > the
> > > > > > > > current session to use unchained transaction mode". Even we
> > changed
> > > > the
> > > > > > SP
> > > > > > > > to Unchained by sp_procxmode, we still got the same error
> > message.
> > > > > > > > It looks like stored proc works only under the Chained mode
in
> > PD. I
> > > > > > hope I
> > > > > > > > am wrong. Any thought to solve the problem?
> > > > > > > >
> > > > > > >
> > > > > > > All this does is disable chained mode. Sounds like an ASE
issue
> > now.
> > > > > > >
> > > > > > > Try running the sproc via tsql
> > > > > > > and see if you encounter the error. Ribo can show you the TDS
> > that is
> > > > > > > being sent to ASE from PD.
> > > > > > >
> > > > > > > Lance
> > > > > > >
> > > > > >
> > > >
> >
============================================================================
> > > > > > ===
> > > > > > > Lance J. Andersen Email: lancea@sybase.com
> > > > > > > Sybase Product Support Engineering Phone:(781) 564-6336
> > > > > > > 77 South Bedford Street Fax: (781) 564-7001
> > > > > > > Burlington, MA 01803
> > > > > > >
> > > > > > > The Dark Knight Returns!!! Let's Go Penguins!!!
> > > > > > >
> > > > > >
> > > >
> >
============================================================================
> > > > > > ===
> > > > > >
> > > > > > Yes, the proc works via tsql. I also tried sproc having only one
> > > > uery( with
> > > > > > or without Select into). The same thing happened.
> > > > > > By the way, could you tell me what TDS means?
> > > > > >
> > > > > > Thanks
> > > > > >
> > > > > > Yong
> > >
> > > --
> > >
> >
============================================================================
> > ===
> > > Lance J. Andersen Email: lancea@sybase.com
> > > Sybase Product Support Engineering Phone:(781) 564-6336
> > > 77 South Bedford Street Fax: (781) 564-7001
> > > Burlington, MA 01803
> > >
> > > The Dark Knight Returns!!! Let's Go Penguins!!!
> > >
> >
============================================================================
> > ===
>
> --
>

============================================================================
===
> Lance J. Andersen Email: lancea@sybase.com
> Sybase Product Support Engineering Phone:(781) 564-6336
> 77 South Bedford Street Fax: (781) 564-7001
> Burlington, MA 01803
>
> The Dark Knight Returns!!! Let's Go Penguins!!!
>
============================================================================
===


Brad McLeod Posted on 2000-03-30 16:13:01.0Z
Newsgroups: sybase.public.easerver
From: "Brad McLeod" <brad.mcleod@worldnet.att.net>
Subject: Re: PowerDynamo and Open Client connections vs ODBC connections - HELP!!!!
Date: Thu, 30 Mar 2000 10:13:01 -0600
Lines: 109
X-Newsreader: Microsoft Outlook Express 4.72.3155.0
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0
NNTP-Posting-Host: ailsa-ded.webzone.net 208.152.102.253
Message-ID: <347_XGC2DOmm$GA.298@forums.sybase.com>
References: <347_wlbGKKPm$GA.52@forums.sybase.com> <347_XV73nuPm$GA.298@forums.sybase.com> <347_$9TIDKcm$GA.52@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:25223
Article PK: 228488

Bill -

Between you and Lance, I should be able to get this puppy to work correctly.
I appreciate your advice and I'll let you know what happens!:)

TIA

Brad McLeod

Bill Zhang wrote in message <$9TIDKcm$GA.52@forums.sybase.com>...
>Open Client connections are automatically set to CHAINED = on. The
>autoCommit property in PowerDynamo may be used to set the chained mode to
>off.
>
>To set chained mode off, you can do:
><!--SCRIPT
> connection.autoCommit = true;
>-->
>
>Another way to do it is to change your SP to anymode. So, it depends on
how
>you created your SP. The SP can be executed in Chained, Unchained, and
>Anymode. To convert a SP to Anymode, you can do it in any isql session:
>
>sp_procxmode [procname [, tranmode]]
>
>tranmode values are: "chained", "unchained", "anymode"
>
>Hope it helps.
>
>
>"Ashish Mahajan" <ash@NOSPAM.com> wrote in message
>news:XV73nuPm$GA.298@forums.sybase.com...
>> Is your sp is trying to do ddl ??
>> Here is what you could try ? Make sure that before you call the stored
>> procedure you are in autocommit mode (I'm not sure whether you can 'tell'
>> Dynamo to set the autocommit mode for you or not)
>>
>> "Brad McLeod" <brad.mcleod@worldnet.att.net> wrote in message
>> news:wlbGKKPm$GA.52@forums.sybase.com...
>> > Lance, Carson and Larry -
>> >
>> > Based upon a previous thread I posted regarding ASA and ASE
environments
>> for
>> > our website DB and the issues we were having, I took your advice and
did
>> the
>> > following:
>> >
>> > 1. Generated our website DB in an ASE 11.9.2 environment instead of
ASA
>> > 6.0.2
>> > 2. Established an Open Client connection profile to the web DB instead
>of
>> > using ODBC.
>> > 3. Created an Open Client connection from the website to the ASE
11.9.2
>> > primary database.
>> >
>> > Here's is what is happening now!:( - Please see the attachment!
>> >
>> > Summary:
>> >
>> > PD pages executing stored procedures under an Open Client/ASE 11.9.2 PD
>> > configuration, do not execute. Under an ODBC/ASE 11.9.2 PD
>configuration
>> > the do.
>> > We have PD web pages that execute SQL and Stored Procedures against the
>> ASE
>> > 11.9.2 database. When accessing the PD web DB via ODBC, the pages
>> executed
>> > correctly and the data was retrieved as expected. Now that we've
>switched
>> > over to Open Client, we are experiencing failures with all of our
stored
>> > procedures executed by our PD web pages that use stored procedures.
>> (Please
>> > refer to the attachment for specifics!)
>> >
>> > Further, any stored procedures that use a 'Select Into' or 'Create'
>> command
>> > do not function under either ODBC or Open Client when the PD web DB is
>in
>> > ASE 11.9.2. When the PD web DB was in ASA and used an ODBC connection,
>> they
>> > worked!!
>> >
>> > Any ideas, insight, guidance would be appreciated. As I said, I took
>all
>> > your advice and this is where we are at now. I have to have this
>> > application, website and supporting database's ready for beta testing
in
>3
>> > DAYS!! HELP!!!
>> >
>> > TIA
>> >
>> > Brad McLeod
>> > StoneHenge Partners
>> >
>> >
>> >
>>
>>
>
>


Brad McLeod Posted on 2000-03-28 22:40:59.0Z
Newsgroups: sybase.public.easerver
From: "Brad McLeod" <brad.mcleod@worldnet.att.net>
Subject: Re: PowerDynamo and Open Client connections vs ODBC connections - HELP!!!!
Date: Tue, 28 Mar 2000 16:40:59 -0600
Lines: 70
X-Newsreader: Microsoft Outlook Express 4.72.3155.0
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0
NNTP-Posting-Host: ailsa-ded.webzone.net 208.152.102.253
Message-ID: <347_m872idQm$GA.201@forums.sybase.com>
References: <347_wlbGKKPm$GA.52@forums.sybase.com> <347_XV73nuPm$GA.298@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:25416
Article PK: 155507

Ashish -

Did you check out the attachment to this thread that contains the actual sp?

Ashish Mahajan wrote in message ...
>Is your sp is trying to do ddl ??
>Here is what you could try ? Make sure that before you call the stored
>procedure you are in autocommit mode (I'm not sure whether you can 'tell'
>Dynamo to set the autocommit mode for you or not)
>
>"Brad McLeod" <brad.mcleod@worldnet.att.net> wrote in message
>news:wlbGKKPm$GA.52@forums.sybase.com...
>> Lance, Carson and Larry -
>>
>> Based upon a previous thread I posted regarding ASA and ASE environments
>for
>> our website DB and the issues we were having, I took your advice and did
>the
>> following:
>>
>> 1. Generated our website DB in an ASE 11.9.2 environment instead of ASA
>> 6.0.2
>> 2. Established an Open Client connection profile to the web DB instead
of
>> using ODBC.
>> 3. Created an Open Client connection from the website to the ASE 11.9.2
>> primary database.
>>
>> Here's is what is happening now!:( - Please see the attachment!
>>
>> Summary:
>>
>> PD pages executing stored procedures under an Open Client/ASE 11.9.2 PD
>> configuration, do not execute. Under an ODBC/ASE 11.9.2 PD configuration
>> the do.
>> We have PD web pages that execute SQL and Stored Procedures against the
>ASE
>> 11.9.2 database. When accessing the PD web DB via ODBC, the pages
>executed
>> correctly and the data was retrieved as expected. Now that we've
switched
>> over to Open Client, we are experiencing failures with all of our stored
>> procedures executed by our PD web pages that use stored procedures.
>(Please
>> refer to the attachment for specifics!)
>>
>> Further, any stored procedures that use a 'Select Into' or 'Create'
>command
>> do not function under either ODBC or Open Client when the PD web DB is in
>> ASE 11.9.2. When the PD web DB was in ASA and used an ODBC connection,
>they
>> worked!!
>>
>> Any ideas, insight, guidance would be appreciated. As I said, I took all
>> your advice and this is where we are at now. I have to have this
>> application, website and supporting database's ready for beta testing in
3
>> DAYS!! HELP!!!
>>
>> TIA
>>
>> Brad McLeod
>> StoneHenge Partners
>>
>>
>>
>
>