Re: Cursor problem

One place I worked used Pro*C to retrieve GROUPS of records into arrays. We found the maximum number of rows that we could retrieve with one fetch was 50. We never really figured out why there was a limit but there was. So we looped and processed 50 record "batches" at a time. This was a LONG time ago and was using Oracle 6.

There may be something similar occuring for you. Perhaps the new "limit" is 350 records at a time on your platform.

Good Luck
Babette Turner-Underwood, TMI Communications

Roger Snowden wrote in message <367F033C.441EDA66_at_NOT.com>...
>Boa Noite, Marco-
>
>No, you are not perfectly clear. Sorry. Generally, retrieving more rows
>will increase retrieval time, won't it? Does the Pro*C program execute
>on one of the server hosts? Is there a client workstation in the way?
>Are you opening a huge cursor with zillions of rows? Are you using array
>fetches? Is there competition for network or machine resources? How much
>is much?
>
>Roger
>
>Roger Snowden
>Sr. Systems Engineering Specialist
>Oracle Corporation
>rsnowden_at_NOTus.oracle.com <-- to reply, remove the obvious
>
>
>
>Marco Ribeiro wrote:
>>
>> Hi,
>>
>> We are having a problem with a cursior in a Pro*C program. We select
>> some records from a local database and then we insert them in a central
>> database, everything goes smoothly if the query returns less than 350
>> records but when we get more records we process becomes very slow.
>>
>> I hope I made myself clear.
>>
>> Any ideas ?
>>
>> Thanks in advance.
>>
>> Marco Ribeiro
Received on Thu Dec 24 1998 - 09:19:26 CST