Re: ORA-12612 cognos impromptu request server 5.0 - hardware SP2 AIX

Just a guess here, but if you are going against a database that is being updated simultaneously, Oracle will generate one of many different error messages and not allow the Impromptu query to finish. This can happen any time during the query - hence your experience with 700.000 vs 140.000 vs 773.000 rows I have seen Oracle do this to other SQL (non-Impromptu) generated queries as well. You might need to break the query into smaller pieces so that it can retrieve all the necessary data before something changes (ie a new record is added) and Oracle kills the process. The other option is to schedule the queries to run at a time when new data is not being added to the tables. I am not aware of any code that can be applied from the Oracle end that can solve this problem. Perhaps other newsreaders may have a solution.

As for why it works ok when running from the desktop, Impromptu is not extracting all the data, only, say the first 100 rows (unless you are doing complex summaries, such as ranking when it needs to retrieve all the data). As you scroll down the pages, it retrieves the additional data points. This happens quickly enough so that no new data is being added into the Oracle tables, hence no errors. This is different than when you are using Impromptu to generate a text file of the data, or use it as a feed to transformer. In those cases, it is going after the whole data set.

Hope this helps
Kirsten Ritchie

Kees Bovee wrote in message <7h93be$hi5$1_at_zonnetje.NL.net>...
>Hello ,
>
>I've got a big problem. When i issue a repport it fails with a error
>ORA-12612. The first time it fails after all most 700.000 rows the second
>time after 140000 rows. And the latest one after 773000 row.
>
>When I start the repport just form a normal desktop it runs perfect. But
>this is not the thing we want here.
>
>impromptu give the following error :
>DMS-E-General exception has occured during operation 'execute'.
>ORA-12612: Message 12612 not found; product=RDBMS; facility=ORA.
>
>
>this i found in the oracle books -->>
>ORA-12612 TNS: connection is busy
>Cause: Attempted operation failed because it conflicts with an on-going
>action or status of the connection. Action: Not normally visible to user.
>For further details, turn on tracing and reexexecute the operation. If
error
>persists, contact Worldwide Customer Support.
>
>Question : Can some one advice me what i should do to with this problem.
>
>I already asked at the customer support of Cognos and Oracle. The could say
>anything special or come with a solution.
>
>Thanks in advance
>
>Anton Kuiper
>
>ps. I hope some one can help me with this problem.
>IF you need more information just ask.
>
>
Received on Thu May 13 1999 - 08:40:03 CEST