MAX OPEN CURSORS

When many requests to the INSERTXML of the Demo samples are processed, we experience the "Max Open Cursor" problem.
We are running XSU 1.0.4.3 and Tomcat 3.2.2.
Any Info would be appreciated.
Many Thanks

Hi Steve
I've looked at a previous discussion
'XSQL Servlet in a high-capacity environment'. Is this bug been fix when using processToXML? I've tried specifying a stylesheet using the XSQLStylesheetProcessor. It seems to run much longer and then the Web Server hangs. Any new connections to the Web Server abd Database does not seem to clear the connections, and then we run out of cursors.
Any help will do!
Many Thanks

Similar Messages

Max open cursors exceedeed in SQL Developer 1.1 Patch 2.(1.1.2.25.79)

While browsing the tables in a schema, I get an ORA-01000 after navigating back and forth between different tabs for a table.
Example:
logon and navigate to other users, schema1, tables
show columns for table one
counts in v$open_cursor for the sid shows
select count(*) from v$pwfile_users where username = :OWNER 3
select sum(cnt) privs from (select count(*) cnt from user_ta 3
click the statistics tab
counts go to 6, no suprise here
click on the column tab
the counts go to 9
click the statistics tab
the counts go to 12
and on and on until the error is produced.

We're doing rolling 2 week releases until production. Expect something new next week.

Maximum open cursors in SQLJ, ORA-01000

Hello,
Can someone please help me with the following: I have a java application that does 7000 insert statements, but I get ORA-01000 after only 200-300 inserts. The error message is:
Exception: java.sql.SQLException: ORA-01000: maximum open cursors exceeded
A simplified version of my insert in sqlj:
try {
     #sql [_ctx] {
          insert into TABLE_X
          ( name, addr ) values
          (:m_name,m_addr)
} catch(SQLException e){
          m_mgr.GetErrorLog().logError("Critical",
     "Failed to insert user into TABLE_X","","Program aborting","?",e );
          m_mgr.SystemErrorExit();
1. The only answers I can find in the forums is either to increase max open cursors in inti.ora, or to close your statements correctly. I'v tried increasing max open cursors but this does not help..(its not a very god approach anyway), and I can't see why I should close my statements from SQLJ: This error did not occur in the same application on a different platform 10 months ago.
2. Could it have something to do with the thin driver version I'm using. Either in JDev or in the database. I use JDev 903 (on win 2000) and a 8.1.7.4 database (on solaris).
3. I tried using oci8 connectoin, but could not get it working. Using oci8 i got the error
java.lang.UnsatisfiedLinkError: no ocijdbc9 in java.library.path
Feedback appreciated.
/Anders

For oci to work you should have Oracle or SQL client installed on your machine.
You should also have ORACLE_HOME\bin in you path.
ocijdbc9.dll is available in the above directory.
Chandar

Maximum Open Cursors Exceeded problem in XSQL

Hi,
We are processing an XSQL page by calling XSQLRequest.process() programatically within our application. Within the XSQL page there are several queries which involve multiple nested CURSOR expressions... when the query returns enough rows we are running into the error "ORA-00604: error occurred at recursive SQL level 1 ORA-01000: maximum open cursors exceeded".
When searching this forum I have seen many (old) postings regarding this error and a bug in the XDK... seems like it was some time ago, but while we set about improving the structure of our XSQL page (or increasing the max open cursor init parameter currently at 500 or both) can anyone confirm that this bug no longer exists?
Also, any general suggestions on working around this limit rather than increasing it? We have considered splitting up our queries into smaller queries (and merging the results via XSLT) and closing cursors during the session explicitly by issuing commits within the XSQL page... but any better ideas?
Thanks,
Bob

I have found this max open cursors problem to be related to Statement object not being closed. This presents a problem for the use of PreparedStatements, because they are only useful if you can keep them open and resuse them. However, in doing so, each iteration through the PreparedStatement creates another open cursor in the databse rather than reusing the previous one. A work around I discovered by reading about REF CURSORS and I use in JDBC is as follows:
Assuming a previously prepared PreparedStatement pstmt and a ResultSet rset-
while (rset.next()) {
rset.close();
// This line closes the cursor in the database
// but does not require you to re-prepare the
// PreparedStatement. Don't ask me why--ask the
// Oracle API guys.
rset.getStatement().close();
// make ready for GC
rset = null;

Error : Maximum Open Cursors Exceded

Hi!
The error appear in that check out or check an objet using OSCM. At first I cna do it but when i trying to check in or out files the messages appear. I don´t understand why and for waht action it appear.
Any suggestion??
Thanks!
Matias

Did you increase the max open cursors to 3000 as recommended in the OracleSCM install guide?
Rob

Open cursors in 11.5.10.2

Hi,
Per metalink note: 216205.1
In 10g, the upper limit is now
# controlled by the parameter session_cached_cursors.
# For 10g environments, the parameters open_cursors and
# session_cached_cursors should be set as follows, in
# accordance with this change in behavior.
open_cursors = 600
session_cached_cursors = 500
Does increasing OPEN_CURSORS parameter value increase performanance in 10.2.3 DB in 11.5.10.2 Application?
Thanks,

Hi,
Does increasing OPEN_CURSORS parameter value increase performanance in 10.2.3 DB in 11.5.10.2 Application?No. You would need to increase the value of this parameter if you get ORA-01000 error -- See (Note: 108886.1 - ORA-1000 Max Open Cursors Exceeded), (Note: 76684.1 - Monitoring Open Cursors & Troubleshooting ORA-1000 Errors), and (Note: 30781.1 - Init.ora Parameter "OPEN_CURSORS" Reference Note).
Regards,
Hussein

JDBC & Open Cursors

Hi,
Could it be possible that even if all ResultSet and Statement objects are closed (in finally blocks so that the close() statements are guaranteed to be executed), one can still get ORA 1000 or max open cursors exceeded? Is there a bug in JDBC that makes the cursors linger even though they have been closed by the program? I ask this because a colleague of mine insists that there is such a JDBC bug and that the only workaround is to close the Connection object. He also claims that the "bug" is fixed in Oracle 9i. We are using Oracle 8.1.7.0.0 on HP-UX 11.0 with java 1.3.1 Any info greatly appreciated. Thanks.
Vasu

Max cursors open, is the problem encountered because of the database limitation of opening of new sessions. A new database session is created whenever a Statement/PreparedStatament is opened.
Make sure to close, Statement/PreparedStatement after its usage, as you have done in finally. This will ensure that it wont exceed the maximum open cursor limit.
I think this is the only cause for the baove problem and can be avoided.
Hope this helps
Ravi

How can you set the max row for a 'open cursor' in a stored proc?

I would like to know how can you set the maximum amount of row returned in a resultset coming from a stored proc?
You can do it via JDBC with cStatement.setMaxRows(10); but it works only for select that you do via JDBC...
I would like the same functionality using open cursor inside a stored proc...
Thanks...

is "where ROWNUM <= 10" the equivalent of "cStatement.setMaxRows(10);" because the ROWNUM as problem with the ORDER BY clause and the setMaxRows() as no problem...

Open cursors are NOT closed only by closing the ResultSet or Statement

I've realised that the open cursors are only closed by closing the connection.
In my example code I have for-loop with a vector of table-names. For every table-name I start a query to retrieve metainformation (row-size, column-names). Although I close the ResultSet (which automatically closes the PreparedStatement/Statement) I reached after the 150th loop a max-cursor-exception (ora-01000) ?!
It seems that there is only the workaround to close and re-open the connection at the end of the for-loop. Which is performance-side pretty bad :-(.
Is there really no other solution?
Besides: does anyone know WHY the statement.close() also closes the ResultSet?? I think this is a bad design (hence to tight dependency between both classes). What if the garbage collector closes the statement (and hence to the JDOC the statement.close()-method also closes the ResultSet)? For example if a method uses a local Statement and returns a ResultSet (and the Statement-garbage is collected), then the ResultSet would cause an exception?!
Thanks for the help in advance
Tai

I've realised that the open cursors are only closed by
closing the connection.Or by closing the Statement!
In my example code I have for-loop with a vector of
table-names. For every table-name I start a query to
retrieve metainformation (row-size, column-names).
Although I close the ResultSet (which automatically
closes the PreparedStatement/Statement) I reached
after the 150th loop a max-cursor-exception
(ora-01000) ?!Closing the ResutSet does not automatically close the PreparedStatement/Statement.
>
It seems that there is only the workaround to close
and re-open the connection at the end of the for-loop.
Which is performance-side pretty bad :-(.
Is there really no other solution?
Just explicitly close the PreparedStatement/Statement!
Besides: does anyone know WHY the statement.close()
also closes the ResultSet?? You need to think of a resultset as a live connection to the database.
Consider SELECT * FROM ABIGTABLE, it would be inefficient to populate the Resultset with all of the rows (could even eat up all memory) so the first n rows are returned ( n = Statement.getFetchSize() ) and the next n rows are returned as needed.
I think this is a bad
design (hence to tight dependency between both
classes). What if the garbage collector closes the
statement (and hence to the JDOC the
statement.close()-method also closes the ResultSet)?
For example if a method uses a local Statement and
returns a ResultSet (and the Statement-garbage is
collected), then the ResultSet would cause an
exception?!You should use a statment and resultset, read all your data into a collection or a CachedRowSet (http://www.javaworld.com/javaworld/jw-02-2001/jw-0202-cachedrow.html) then close the statment as soon as possible. Never return a resultset form your data tier: that is tight coupling between the tiers of your application!

More on "maximum open cursors exceeded"

It seems a lot of people have been seeing this error message, but reading through the posts on the topic hasn't given me any new insight on the problem. Here's an account of my particular situation:
I am using the XSQL servlet, v.1.0.0.0 with the thin jdbc driver v.1.x. The servlet is running within an Apache server (1.3.12) on a Linux box, and the Oracle database (8.1.5) is located on a Solaris 2.6 machine.
The servlet accepts HTTP connections, performs the corresponding SQL queries and returns the output from the database to the HTTP client. Here's a simple example:
(Sorry about potential bad line breaks.)
client request:
% telnet xsql-host.some.domain 80
Trying xxx.xxx.xxx.xxx
Connected to xsql-host.some.domain.
GET /xsql/test/listall.xsql
<server response here>
listall.xsql:
<?xml version="1.0"?>
<page connection="boss" xmlns:xsql="urn:oracle-xsql">
<accounts>
<xsql:query tag-case="lower" rowset-element="" row-element="accountinfo">
select * from test
</xsql:query>
</accounts>
</page>
Very simple stuff indeed. Now, this has worked perfectly for 3 weeks or so. During this period, the xsql servlet has been stopped and restarted numerous times and the machine hosting the database has been rebooted at least three times. Then, for no apparent reason (as nothing had changed in the setup described above), I started getting "maximum open cursors exceeded" on every request. Since then, I have been unable to get the system working as it had up until now. I haven't restarted the database and I would like to avoid doing so, because that would not be a valid solution for us if the problem reappeared in production. The maximum open cursors setting in Oracle should be correct, since things were running smoothly before.
From what I can see, the problem could be with the servlet not closing its cursors. One post mentioned that it did, but I would appreciate it if this could be double-checked. Considering the database is the only portion of the system which has been kept running for extended periods of time, it seems to me that this might indeed be the problem.
Confirmation, workarounds, suggestions, patches, or a consolation box of chocolates would all be appreciated.
Thanks,
- Fad
([email protected])
null

Check which process is making all the cursors on which database. If it is your procedure, try explicitly closing the cursors. I think the cursors are only implicitely closed after the transaction is ended. If you loop and open a cursor within the loop, that might be the problem.
I also had this problem with Java working over a JDBC connection some time ago on a 815 database. If I recall correctly, that was caused by the JDBC driver and fixed by replacing it with a JDBC driver of 9i.
The following script is what I used previously in a program that can draw a graph from the results. It is ugly, but does the job.
Hope this helps,
L.
select
'max cursors',
to_number(value)
from
v$parameter
where
name = 'open_cursors'
union
select
substr(lower(username),1,10)||'('||substr(to_char(ses.sid)||','
||to_char(serial#),1,9)||')',
s.value
from
v$sesstat s,
v$statname n,
v$session ses
where
s.statistic#=n.statistic#
and ses.sid=s.sid
and n.name like '%cursor%'
and n.name like '%current%'
and not (ses.sid between 1 and 6)

TOO many OPEN CURSORS during loop of INSERT's

Running ODP.NET beta2 (can't move up yet but will do that soon)
I don't think it is related with ODP itself but probably on how .Net works with cursors. We have a for/next loop that executes INSERT INTO xxx VALUES (:a,:b,:c)
statements. Apparently, when monitoring v$sysstat (current open cursors) we see these raising with 1 INSERT = 1 cursor. If subsequently we try to perform another action, we get max cursors exceeded. We allready set open_cursor = 1000, but the number of inserts can be very high. Is there a way to release these cursors (already wrote oDataAdaptor.dispose, oCmd.dispose but this does not help.
Is it normal that each INSERT has it's own cursor ? they all have the same hashvalue in v$open_cursor. They seem to be released after a while, especially when moving to another asp.net page, but it's not clear when that happens and if it is possible to force the release of the (implicit?) cursors faster.
Below is a snippet of the code, I unrolled a couple of function-calls into the code so this is just an example, not sure it will run without errors like this, but the idea should be clear (the code looks rather complex for what it does but the unrolled functions make the code more generic and we have a database-independend datalayer):
Try
' Set the Base Delete statement
lBaseSql = _
"INSERT INTO atable(col1,col2,col3) " & _
"VALUES(:col1,:col2,:col3)"
' Initialize a transaction
lTransaction = oConnection.BeginTransaction()
' Create the parameter collection, containing for each
' row in the list the arguments
For Each lDataRow In aList.Rows
lOracleParamters = New OracleParameterCollection()
lOracleParameter = New OracleParameter("luserid", OracleDbType.Varchar2,
_ CType(aCol1, Object))
lOracleParamters.Add(lOracleParameter)
lOracleParameter = New OracleParameter("part_no", OracleDbType.Varchar2, _
CType(lDataRow.Item("col2"), Object))
lOracleParamters.Add(lOracleParameter)
lOracleParameter = New OracleParameter("revision", OracleDbType.Int32, _
CType(lDataRow.Item("col3"), Object))
lOracleParamters.Add(lOracleParameter)
' Execute the Statement;
' If the execution fails because the row already exists,
' then the insert should be considered as succesfull.
Try
Dim aCommand As New OracleCommand()
Dim retval As Integer
'associate the aConnection with the aCommand
aCommand.Connection = oConnection
'set the aCommand text (stored procedure name or SQL statement)
aCommand.CommandText = lBaseSQL
'set the aCommand type
aCommand.CommandType = CommandType.Text
'attach the aCommand parameters if they are provided
If Not (lOracleParameters Is Nothing) Then
Dim lParameter As OracleParameter
For Each lParameter In lOracleParameters
'check for derived output value with no value assigned
If lParameter.Direction = ParameterDirection.InputOutput _
And lParameter.Value Is Nothing Then
lParameter.Value = Nothing
End If
aCommand.Parameters.Add(lParameter)
Next lParameter
End If
Return
' finally, execute the aCommand.
retval = cmd.ExecuteNonQuery()
' detach the OracleParameters from the aCommand object,
' so they can be used again
cmd.Parameters.Clear()
Catch ex As Exception
Dim lErrorMsg As String
lErrorMsg = ex.ToString
If Not lTransaction Is Nothing Then
lTransaction.Rollback()
End If
End Try
Next
lTransaction.Commit()
Catch ex As Exception
lTransaction.Rollback()
Throw New DLDataException(aConnection, ex)
End Try

I have run into this problem as well. To my mind
Phillip's solution will work but seems completey unnecessary. This is work the provider itself should be managing.
I've done extensive testing with both ODP and OracleClient. Here is one of the scenarios: In a tight loop of 10,000 records, each of which is either going to be inserted or updated via a stored procedure call, the ODP provider throws the "too many cursor errors at around the 800th iteration. With over 300 cursors being open. The exact same code with OracleClient as the provider never throws an error and opens up 40+ cursors during execution.
The applicaation I have updates a Oracle8i database from a DB2 database. There are over 30 tables being updated in near real time. Reusing the command object is not an option and adding all the code Phillip did for each call seems highly unnecessary. I say Oracle needs to fix this problem. As much as I hate to say it the microsoft provider seems superior at this point.

Maximum open cursors exceeded when inserting to a remote db

I receive the error:
ORA-01000: maximum open cursors exceeded
ORA-02063: preceding line
from ONTARIO
(where ONTARIO is my remote db) when I am performing inserts from a pl/sql procedure to the remote db. I am performing two inserts from inside pl/sql and then issuing an explicit commit. I checked the open_cursors init param on both the local db and remote db and it was set to 300. I bumped up the remote db init param to 600. I was able to perform more inserts but still received this error.
I thought implicit cursors close themselves, especially after a commit. Do I need to do something special to close the cursors on the remote machine?
Thanks for your time...

Check which process is making all the cursors on which database. If it is your procedure, try explicitly closing the cursors. I think the cursors are only implicitely closed after the transaction is ended. If you loop and open a cursor within the loop, that might be the problem.
I also had this problem with Java working over a JDBC connection some time ago on a 815 database. If I recall correctly, that was caused by the JDBC driver and fixed by replacing it with a JDBC driver of 9i.
The following script is what I used previously in a program that can draw a graph from the results. It is ugly, but does the job.
Hope this helps,
L.
select
'max cursors',
to_number(value)
from
v$parameter
where
name = 'open_cursors'
union
select
substr(lower(username),1,10)||'('||substr(to_char(ses.sid)||','
||to_char(serial#),1,9)||')',
s.value
from
v$sesstat s,
v$statname n,
v$session ses
where
s.statistic#=n.statistic#
and ses.sid=s.sid
and n.name like '%cursor%'
and n.name like '%current%'
and not (ses.sid between 1 and 6)

Help needed, getting ORA-01000: maximum open cursors exceeded

CJ or anyone that may have come across this problem in the past, I hope that you may be able to help me
I am trying to implement a function from the Salesforce PHP tool kit that runs against a class that returns a object of ID's that have been updated in a given time frame.
This is a lot of code. I am sorry for that:
<?php
error_reporting(E_ERROR | E_WARNING | E_PARSE | E_NOTICE);
//Keep the SOAP cache clean
ini_set("soap.wsdl_cache_enabled","0");
$delete_count = 0;
$oracle_deleted = 0;
//Setup array for local ID's'
$opportunity_data = array();
$deleted_data = array();
//start setup for PL SQL statement
$strsql = "begin mapsapp.sforce_opp_insert(";
$strsql .= ":pm_id,";
$strsql .= ":pm_accountid,";
$strsql .= ":pm_name,";
$strsql .= ":pm_description,";
$strsql .= ":pm_stagename,";
$strsql .= ":pm_amount,";
$strsql .= ":pm_probability,";
$strsql .= ":pm_expectedrevenue,";
$strsql .= ":pm_closedate,";
$strsql .= ":pm_type,";
$strsql .= ":pm_nextstep,";
$strsql .= ":pm_leadsource,";
$strsql .= ":pm_isclosed,";
$strsql .= ":pm_iswon,";
$strsql .= ":pm_forecastcategory,";
$strsql .= ":pm_campaignid,";
$strsql .= ":pm_hasopportunitylineitem,";
$strsql .= ":pm_pricebook2id,";
$strsql .= ":pm_ownerid,";
$strsql .= ":pm_createddate,";
$strsql .= ":pm_createdbyid,";
$strsql .= ":pm_lastmodifieddate,";
$strsql .= ":pm_lastmodifiedbyid,";
$strsql .= ":pm_systemmodstamp,";
$strsql .= ":pm_rsm_project_id_score__c,";
$strsql .= ":pm_lead_fae__c,";
$strsql .= ":pm_avg_annual_volume__c,";
$strsql .= ":pm_priority__c,";
$strsql .= ":pm_design_start_date__c,";
$strsql .= ":pm_design_proto_date__c,";
$strsql .= ":pm_production_years__c,";
$strsql .= ":pm_production_life_months__c,";
$strsql .= ":pm_production_months__c,";
$strsql .= ":pm_design_freeze_date__c,";
$strsql .= ":pm_production_proto_date__c,";
$strsql .= ":pm_mass_production_date__c,";
$strsql .= ":pm_fae_status__c,";
$strsql .= ":pm_fae_assigned_date__c,";
$strsql .= ":pm_fae_accepted_date__c,";
$strsql .= ":pm_potential__c,";
$strsql .= ":pm_fae_reject_reason__c,";
$strsql .= ":pm_fae_project_complexity__c,";
$strsql .= ":pm_design_phase__c,";
$strsql .= ":pm_maxim_id__c,";
$strsql .= ":pm_project_number__c,";
$strsql .= ":pm_active__c,";
$strsql .= ":pm_pivotal_created_by__c,";
$strsql .= ":pm_manufactured_by__c,";
$strsql .= ":pm_isdeleted,";
$strsql .= ":pm_lastactivitydate";
$strsql .= "); end;";
//end setup for PL SQL statement
//include common files
require_once ('/users/msimonds/public_html/includes/sfdc.inc');
include_once ('adodb.inc.php');
$db = ADONewConnection("oci8");
//connect to Oracle
$db->Connect('',"database_user","password","dev2");
//$db->BeginTrans();
$db->SetFetchMode(ADODB_FETCH_ASSOC);
if ($db)
 try
 //Set current time to get records from Salesforce
 $currentTime = mktime();
 // assume that update occured within the last 24 hrs.
 $startTime = $currentTime - (60 * 60 * 36); //(seconds * minutes * hours)
 $endTime = $currentTime;
 echo "***** Get Updated Opportunities from the last 24 hours ***** ";
 $getUpdateddResponse = $client->getUpdated('Opportunity',$startTime,$endTime);
 //$getUpdateddResponse->ids = "";
 //echo '<pre>'.print_r($getUpdateddResponse,true).'</pre>';
 //exit;
 $opportunity_data = $getUpdateddResponse->ids;
 if (is_array($opportunity_data) || is_object($opportunity_data))
 set_time_limit(0);
 ini_set("memory_limit","512M");
 //copy data from Object to local array
 //count the number of records coming in from Salesforce
 $record_count = count($opportunity_data);
 echo $record_count;
 exit;
 //echo '<pre>'.print_r($opportunity_data,true).'</pre>';
 //exit;
 //loop through the records
 for ($i = 0; $i < $record_count; $i++)
 $id = $opportunity_data[$i];
 //SQL query for Salesforce
 $soql = "Select Id, IsDeleted, AccountId, Name, Description, StageName, Amount, Probability, ExpectedRevenue, CloseDate, Type, NextStep, LeadSource, IsClosed, IsWon, ForecastCategory, CampaignId, HasOpportunityLineItem, Pricebook2Id, OwnerId, CreatedDate, CreatedById, LastModifiedDate, LastModifiedById, SystemModstamp, LastActivityDate, RSM_Original_Project_ID_Score__c, Lead_FAE__c, Avg_Annual_Volume__c, Priority__c, Design_Start_Date__c, Design_Proto_Date__c, Production_Years__c, Production_Life_months__c, Production_Months__c, Design_Freeze_Date__c, Production_Proto_Date__c, Mass_Production_Date__c, FAE_Status__c, FAE_Assigned_Date__c, FAE_Accepted_Date__c, Project_Potential__c, FAE_Reject_Reason__c, FAE_Project_Complexity__c, Design_Phase__c, maxim_id__c, Project_Number__c, Active__c, Project_Comments__c, Pivotal_Created_By__c, Manufactured_By__c FROM Opportunity WHERE Id = '{$id}'";
 //setup query to local Oracle MAPS database
 $get_oracle_record = query_db($id,$db);
 if ($get_oracle_record)
 $sql = "DELETE FROM sforce_opportunity WHERE ID = '{$id}'";
 if ($db->Execute($sql)) ;
 $insert_records = get_records($client,$soql);
 else
 $insert_records = get_records($client,$soql);
 foreach ($insert_records as $r)
 $pass_this['id'] = $id;
 $pass_this['accountid'] = (string )$r->fields->AccountId;
 $pass_this['name'] = (string )$r->fields->Name;
 $pass_this['description'] = (string )$r->fields->Description;
 $pass_this['stagename'] = (string )$r->fields->StageName;
 $pass_this['amount'] = (int)$r->fields->Amount;
 $pass_this['probability'] = (int)$r->fields->Probability;
 $pass_this['expectedrevenue'] = (int)$r->fields->ExpectedRevenue;
 $pass_this['closedate'] = (string )$r->fields->CloseDate;
 $pass_this['type'] = (string )$r->fields->Type;
 $pass_this['nextstep'] = (string )$r->fields->NextStep;
 $pass_this['leadsource'] = (string )$r->fields->LeadSource;
 $pass_this['isclosed'] = (string )$r->fields->IsClosed;
 $pass_this['iswon'] = (string )$r->fields->IsWon;
 $pass_this['forecastcategory'] = (string )$r->fields->ForecastCategory;
 $pass_this['campaignid'] = (string )$r->fields->CampaignId;
 $pass_this['hasopportunitylineitem'] = (string )$r->fields->HasOpportunityLineItem;
 $pass_this['pricebook2id'] = $r->fields->Pricebook2Id;
 $pass_this['ownerid'] = $r->fields->OwnerId;
 $pass_this['createddate'] = (string )$r->fields->CreatedDate;
 $pass_this['createdbyid'] = (string )$r->fields->CreatedById;
 $pass_this['lastmodifieddate'] = (string )$r->fields->LastModifiedDate;
 $pass_this['lastmodifiedbyid'] = (string )$r->fields->LastModifiedById;
 $pass_this['systemmodstamp'] = (string )$r->fields->SystemModstamp;
 $pass_this['rsm_project_id_score__c'] = (int)$r->fields->RSM_Original_Project_ID_Score__c;
 $pass_this['lead_fae__c'] = (string )$r->fields->Lead_FAE__c;
 $pass_this['avg_annual_volume__c'] = (int)$r->fields->Avg_Annual_Volume__c;
 $pass_this['priority__c'] = (string )$r->fields->Priority__c;
 $pass_this['design_start_date__c'] = (string )$r->fields->Design_Start_Date__c;
 $pass_this['design_proto_date__c'] = (string )$r->fields->Design_Proto_Date__c;
 $pass_this['production_years__c'] = (int)$r->fields->Production_Years__c;
 $pass_this['production_life_months__c'] = (int)$r->fields->Production_Life_months__c;
 $pass_this['production_months__c'] = (int)$r->fields->Production_Months__c;
 $pass_this['design_freeze_date__c'] = (string )$r->fields->Design_Freeze_Date__c;
 $pass_this['production_proto_date__c'] = (string )$r->fields->Production_Proto_Date__c;
 $pass_this['mass_production_date__c'] = (string )$r->fields->Mass_Production_Date__c;
 $pass_this['fae_status__c'] = (string )$r->fields->FAE_Status__c;
 $pass_this['fae_assigned_date__c'] = (string )$r->fields->FAE_Assigned_Date__c;
 $pass_this['fae_accepted_date__c'] = (string )$r->fields->FAE_Accepted_Date__c;
 $pass_this['project_potential__c'] = (int)$r->fields->Project_Potential__c;
 $pass_this['fae_reject_reason__c'] = (string )$r->fields->FAE_Reject_Reason__c;
 $pass_this['fae_project_complexity__c'] = (string )$r->fields->FAE_Project_Complexity__c;
 $pass_this['design_phase__c'] = (string )$r->fields->Design_Phase__c;
 $pass_this['maxim_id__c'] = (string )$r->fields->maxim_id__c;
 $pass_this['objective_status_next_qtr__c'] = (string )$r->fields->Objective_Status_Next_Qtr__c;
 $pass_this['quality_of_relationship__c'] = (string )$r->fields->Quality_of_Relationship__c;
 $pass_this['targeted_po_date__c'] = (string )$r->fields->Targeted_PO_Date__c;
 $pass_this['part_no_involved__c'] = (string )$r->fields->Part_No_Involved__c;
 $pass_this['first_po_number__c'] = (string )$r->fields->First_PO_Number__c;
 $pass_this['lost_reason__c'] = (string )$r->fields->Lost_Reason__c;
 $pass_this['fae_estimate_of_business__c'] = (string )$r->fields->FAE_Estimate_of_Business__c;
 $pass_this['digital_processor__c'] = (string )$r->fields->Digital_Processor__c;
 $pass_this['project_number__c'] = (string )$r->fields->Project_Number__c;
 $pass_this['active__c'] = (string )$r->fields->Active__c;
 $pass_this['pivotal_created_by__c'] = (string )$r->fields->Pivotal_Created_By__c;
 $pass_this['manufactured_by__c'] = (string )$r->fields->Manufactured_By__c;
 $pass_this['isdeleted'] = (string )$r->fields->IsDeleted;
 $pass_this['lastactivitydate'] = (string )$r->fields->LastActivityDate;
 $pass_this['optocon_id__c'] = (string )$r->fields->OptoCon_ID__c;
 if (strlen($pass_this['description']) == 0)
 $pass_this['description'] = "No Description Posted";
 else
 $pass_this['description'] = $pass_this['description'];
 //echo '<pre>'.print_r($pass_this,true).'</pre>';
 //exit;
 $record_inserted = insert_record($pass_this,$strsql,$db);
 if (!$record_inserted)
 //mail('[email protected]','insert error','There was a proble trying to insert a record into the database');
 else
 echo "Nothing here";
 //exit;
 //add back in once replication is done
 //get deleted records from the Opportunity
 $getDeletedResponse = $client->getDeleted('Opportunity',$startTime,$endTime);
 //echo '<pre>'.print_r($getDeletedResponse,true).'</pre>';
 //exit;
 $deleted_ids = $getDeletedResponse->deletedRecords;
 //echo '<pre>'.print_r($deleted_ids,true).'</pre>';
 if (is_object($deleted_ids))
 $temp_array[] = $deleted_ids;
 unset($deleted_ids);
 $deleted_ids = $temp_array;
 $delete_count = count($deleted_ids);
 //echo $delete_count;
 for ($i = 0; $i < $delete_count; $i++)
 $d_id = $deleted_ids[$i];
 $id = $d_id->id;
 if (query_db($id,$db))
 $delete_sql = "Delete from sforce_opportunity WHERE ID = '{$id}'";
 $oracle_deleted++;
 if ($db->Execute($delete_sql))
 echo "".$id." was removed from the Oracle database ";
 else
 echo $id." is not in the Oracle database ";
 echo $oracle_deleted." records were deleted from Oracle";
 catch (exception $e)
 $error = '<pre>'.print_r($e,true).'</pre>';
 mail('[email protected]','insert error',$error);
$db->CommitTrans();
$db->Close();
exit;
function insert_record($pass_this,$strsql,&$db)
 //Prepares PL/SQL Statement
 $stmt = $db->Prepare($strsql);
 $db->InParameter($stmt,$pass_this['id'],'pm_id');
 $db->InParameter($stmt,$pass_this['accountid'],'pm_accountid');
 $db->InParameter($stmt,$pass_this['name'],'pm_name');
 $db->InParameter($stmt,$pass_this['description'],'pm_description',-1,OCI_B_CLOB);
 $db->InParameter($stmt,$pass_this['stagename'],'pm_stagename');
 $db->InParameter($stmt,$pass_this['amount'],'pm_amount');
 $db->InParameter($stmt,$pass_this['probability'],'pm_probability');
 $db->InParameter($stmt,$pass_this['expectedrevenue'],'pm_expectedrevenue');
 $db->InParameter($stmt,$pass_this['closedate'],'pm_closedate');
 $db->InParameter($stmt,$pass_this['type'],'pm_type');
 $db->InParameter($stmt,$pass_this['nextstep'],'pm_nextstep');
 $db->InParameter($stmt,$pass_this['leadsource'],'pm_leadsource');
 $db->InParameter($stmt,$pass_this['isclosed'],'pm_isclosed');
 $db->InParameter($stmt,$pass_this['iswon'],'pm_iswon');
 $db->InParameter($stmt,$pass_this['forecastcategory'],'pm_forecastcategory');
 $db->InParameter($stmt,$pass_this['campaignid'],'pm_campaignid');
 $db->InParameter($stmt,$pass_this['hasopportunitylineitem'],'pm_hasopportunitylineitem');
 $db->InParameter($stmt,$pass_this['pricebook2id'],'pm_pricebook2id');
 $db->InParameter($stmt,$pass_this['ownerid'],'pm_ownerid');
 $db->InParameter($stmt,$pass_this['createddate'],'pm_createddate');
 $db->InParameter($stmt,$pass_this['createdbyid'],'pm_createdbyid');
 $db->InParameter($stmt,$pass_this['lastmodifieddate'],'pm_lastmodifieddate');
 $db->InParameter($stmt,$pass_this['lastmodifiedbyid'],'pm_lastmodifiedbyid');
 $db->InParameter($stmt,$pass_this['systemmodstamp'],'pm_systemmodstamp');
 $db->InParameter($stmt,$pass_this['rsm_project_id_score__c'],'pm_rsm_project_id_score__c');
 $db->InParameter($stmt,$pass_this['lead_fae__c'],'pm_lead_fae__c');
 $db->InParameter($stmt,$pass_this['avg_annual_volume__c'],'pm_avg_annual_volume__c');
 $db->InParameter($stmt,$pass_this['priority__c'],'pm_priority__c');
 $db->InParameter($stmt,$pass_this['design_start_date__c'],'pm_design_start_date__c');
 $db->InParameter($stmt,$pass_this['design_proto_date__c'],'pm_design_proto_date__c');
 $db->InParameter($stmt,$pass_this['production_years__c'],'pm_production_years__c');
 $db->InParameter($stmt,$pass_this['production_life_months__c'],'pm_production_life_months__c');
 $db->InParameter($stmt,$pass_this['production_months__c'],'pm_production_months__c');
 $db->InParameter($stmt,$pass_this['design_freeze_date__c'],'pm_design_freeze_date__c');
 $db->InParameter($stmt,$pass_this['production_proto_date__c'],'pm_production_proto_date__c');
 $db->InParameter($stmt,$pass_this['mass_production_date__c'],'pm_mass_production_date__c');
 $db->InParameter($stmt,$pass_this['fae_status__c'],'pm_fae_status__c');
 $db->InParameter($stmt,$pass_this['fae_assigned_date__c'],'pm_fae_assigned_date__c');
 $db->InParameter($stmt,$pass_this['fae_accepted_date__c'],'pm_fae_accepted_date__c');
 $db->InParameter($stmt,$pass_this['project_potential__c'],'pm_potential__c');
 $db->InParameter($stmt,$pass_this['fae_reject_reason__c'],'pm_fae_reject_reason__c');
 $db->InParameter($stmt,$pass_this['fae_project_complexity__c'],'pm_fae_project_complexity__c');
 $db->InParameter($stmt,$pass_this['design_phase__c'],'pm_design_phase__c');
 $db->InParameter($stmt,$pass_this['maxim_id__c'],'pm_maxim_id__c');
 $db->InParameter($stmt,$pass_this['project_number__c'],'pm_project_number__c');
 $db->InParameter($stmt,$pass_this['active__c'],'pm_active__c');
 $db->InParameter($stmt,$pass_this['pivotal_created_by__c'],'pm_pivotal_created_by__c');
 $db->InParameter($stmt,$pass_this['manufactured_by__c'],'pm_manufactured_by__c');
 $db->InParameter($stmt,$pass_this['isdeleted'],'pm_isdeleted');
 $db->InParameter($stmt,$pass_this['lastactivitydate'],'pm_lastactivitydate');
 //executes and loads data coming from salesforce into table
 if ($db->Execute($stmt))
 echo $pass_this['id']." was inserted into the database ";
 flush();
 unset($pass_this);
 unset($stmt);
 return true;
 else
 echo $db->ErrorMsg()." ";
 mail('[email protected]','database error',$db->ErrorMsg());
 return false;
//Get the data from Salesforce to populate Oracle
function get_records(&$connection,&$query)
 $queryOptions = new QueryOptions(2000);
 $response = new QueryResult($connection->query($query));
 // if the size is zero, where done
 if ($response->size > 0)
 $products = $response->records;
 // Cycles through additional responses if the number of records
 // exceeds the batch size
 while (!$response->done)
 set_time_limit(100);
 $response = $connection->queryMore($response->queryLocator);
 $products = array_merge($products,$response->records);
 return $products;
function query_db($id,&$db)
 global $db;
 $sql = "SELECT *
 FROM sforce_opportunity
 Where id = '{$id}'";
 $rs = $db->Execute($sql);
 if ($rs && $rs->_numOfRows > 0)
 return true;
 else
 return false;
 exit;
?>the code runs fine and I do not commit my inserts until after I am done retrieving all the records, but I am getting the oracle error: ORA-01000: maximum open cursors exceeded
I am not using any cursors in my PL SQL
CREATE OR REPLACE PROCEDURE MAPSAPP.sforce_opp_insert (
 pm_id IN VARCHAR2,
 pm_accountid IN VARCHAR2,
 pm_name IN VARCHAR2,
 pm_description IN VARCHAR2,
 pm_stagename IN VARCHAR2,
 pm_amount IN NUMBER,
 pm_probability IN NUMBER,
 pm_expectedrevenue IN NUMBER,
 pm_closedate IN VARCHAR2,
 pm_type IN VARCHAR2,
 pm_nextstep IN VARCHAR2,
 pm_leadsource IN VARCHAR2,
 pm_isclosed IN VARCHAR2,
 pm_iswon IN VARCHAR2,
 pm_forecastcategory IN VARCHAR2,
 pm_campaignid IN VARCHAR2,
 pm_hasopportunitylineitem IN VARCHAR2,
 pm_pricebook2id IN VARCHAR2,
 pm_ownerid IN VARCHAR2,
 pm_createddate IN VARCHAR2,
 pm_createdbyid IN VARCHAR2,
 pm_lastmodifieddate IN VARCHAR2,
 pm_lastmodifiedbyid IN VARCHAR2,
 pm_systemmodstamp IN VARCHAR2,
 pm_rsm_project_id_score__c IN VARCHAR2,
 pm_lead_fae__c IN VARCHAR2,
 pm_avg_annual_volume__c IN VARCHAR2,
 pm_priority__c IN VARCHAR2,
 pm_design_start_date__c IN VARCHAR2,
 pm_design_proto_date__c IN VARCHAR2,
 pm_production_years__c IN NUMBER,
 pm_production_life_months__c IN NUMBER,
 pm_production_months__c IN NUMBER,
 pm_design_freeze_date__c IN VARCHAR2,
 pm_production_proto_date__c IN VARCHAR2,
 pm_mass_production_date__c IN VARCHAR2,
 pm_fae_status__c IN VARCHAR2,
 pm_fae_assigned_date__c IN VARCHAR2,
 pm_fae_accepted_date__c IN VARCHAR2,
 pm_potential__c IN NUMBER,
 pm_fae_reject_reason__c IN VARCHAR2,
 pm_fae_project_complexity__c IN VARCHAR2,
 pm_design_phase__c IN VARCHAR2,
 pm_maxim_id__c IN VARCHAR2,
 pm_project_number__c IN VARCHAR2,
 pm_active__c IN VARCHAR2,
 pm_pivotal_created_by__c IN VARCHAR2,
 pm_manufactured_by__c IN VARCHAR2,
 pm_isdeleted IN VARCHAR2,
 pm_lastactivitydate IN VARCHAR2
IS
BEGIN
 INSERT INTO SFORCE_OPPORTUNITY
 (id,
 accountid,
 name,
 description,
 stagename,
 amount,
 probability,
 expectedrevenue,
 closedate,
 type,
 nextstep,
 leadsource,
 isclosed,
 iswon,
 forecastcategory,
 campaignid,
 hasopportunitylineitem,
 pricebook2id,
 ownerid,
 createddate,
 createdbyid,
 lastmodifieddate,
 lastmodifiedbyid,
 systemmodstamp,
 rsm_project_id_score__c,
 lead_fae__c,
 avg_annual_volume__c,
 priority__c,
 design_start_date__c,
 design_proto_date__c,
 production_years__c,
 production_life_months__c,
 production_months__c,
 design_freeze_date__c,
 production_proto_date__c,
 mass_production_date__c,
 fae_status__c,
 fae_assigned_date__c,
 fae_accepted_date__c,
 project_potential__c,
 fae_reject_reason__c,
 fae_project_complexity__c,
 design_phase__c,
 maxim_id__c,
 project_number__c,
 active__c,
 pivotal_created_by__c,
 manufactured_by__c,
 isdeleted,
 lastactivitydate
 VALUES (pm_id,
 pm_accountid,
 pm_name,
 pm_description,
 pm_stagename,
 pm_amount,
 pm_probability,
 pm_expectedrevenue,
 TO_DATE (SUBSTR (REPLACE (pm_closedate, 'T', ' '), 1, 19),'YYYY-MM-DD HH24:MI:SS'),
 pm_type,
 pm_nextstep,
 pm_leadsource,
 pm_isclosed,
 pm_iswon,
 pm_forecastcategory,
 pm_campaignid,
 pm_hasopportunitylineitem,
 pm_pricebook2id,
 pm_ownerid,
 TO_DATE (SUBSTR (REPLACE (pm_createddate, 'T', ' '), 1, 19),'YYYY-MM-DD HH24:MI:SS'),
 pm_createdbyid,
 TO_DATE (SUBSTR (REPLACE (pm_lastmodifieddate, 'T', ' '), 1, 19),'YYYY-MM-DD HH24:MI:SS'),
 pm_lastmodifiedbyid,
 TO_DATE (SUBSTR (REPLACE (pm_systemmodstamp, 'T', ' '), 1, 19),'YYYY-MM-DD HH24:MI:SS'),
 pm_rsm_project_id_score__c,
 pm_lead_fae__c,
 pm_avg_annual_volume__c,
 pm_priority__c,
 TO_DATE (SUBSTR (REPLACE (pm_design_start_date__c, 'T', ' '), 1, 19),'YYYY-MM-DD HH24:MI:SS'),
 TO_DATE (SUBSTR (REPLACE (pm_design_proto_date__c, 'T', ' '), 1, 19),'YYYY-MM-DD HH24:MI:SS'),
 pm_production_years__c,
 pm_production_life_months__c,
 pm_production_months__c,
 TO_DATE (SUBSTR (REPLACE (pm_design_freeze_date__c, 'T', ' '), 1, 19),'YYYY-MM-DD HH24:MI:SS'),
 TO_DATE (SUBSTR (REPLACE (pm_production_proto_date__c, 'T', ' '), 1, 19),'YYYY-MM-DD HH24:MI:SS'),
 TO_DATE (SUBSTR (REPLACE (pm_mass_production_date__c, 'T', ' '), 1, 19),'YYYY-MM-DD HH24:MI:SS'),
 pm_fae_status__c,
 TO_DATE (SUBSTR (REPLACE (pm_fae_assigned_date__c, 'T', ' '), 1, 19),'YYYY-MM-DD HH24:MI:SS'),
 TO_DATE (SUBSTR (REPLACE (pm_fae_accepted_date__c, 'T', ' '), 1, 19),'YYYY-MM-DD HH24:MI:SS'),
 pm_potential__c,
 pm_fae_reject_reason__c,
 pm_fae_project_complexity__c,
 pm_design_phase__c,
 pm_maxim_id__c,
 pm_project_number__c,
 pm_active__c,
 pm_pivotal_created_by__c,
 pm_manufactured_by__c,
 pm_isdeleted,
 TO_DATE (SUBSTR (REPLACE (pm_lastactivitydate, 'T', ' '), 1, 19),'YYYY-MM-DD HH24:MI:SS')
END sforce_opp_insert;
/I was wondering anyone has seen this before
TIA,
Mike

The code below is deleting fine. Check your $id is valid. I wonder if ADOdb has some quirks with binding and variable creation/destruction, similar to #1 in http://www.oracle.com/technology/tech/php/htdocs/php_troubleshooting_faq.html#bindvars
<?php
See ADOdb Tutorial for Oracle: http://phplens.com/lens/adodb/docs-oracle.htm
drop table mytab;
create table mytab (city varchar2(20), country_id varchar2(20));
insert into mytab values ('SF', 'US');
insert into mytab values ('Sydney', 'AU');
insert into mytab values ('London', 'UK');
commit;
require_once("/home/cjones/public_html/php/adodb5/adodb.inc.php");
$db = ADONewConnection("oci8");
$db->Connect("//localhost/XE", "hr", "hrpwd");
echo "Before:\n";
$rs = $db->Execute("select city from mytab");
while ($arr = $rs->FetchRow()) {
 echo $arr['CITY'] . "\n";
$s = $db->Prepare("delete from mytab where country_id = :ci");
$db->Parameter($s, $ci, 'ci');
foreach (array('US', 'AU') as $ci) {
 $db->Execute($s);
echo "After:\n";
$rs = $db->Execute("select city from mytab");
while ($arr = $rs->FetchRow()) {
 echo $arr['CITY'] . "\n";
?>There's another sample in the ADOdb OCI8 driver:
 Usage:
 $stmt = $DB->Prepare("insert into table (col0, col1, col2) values (:0, :1, :2)");
 $DB->Bind($stmt, $p1);
 $DB->Bind($stmt, $p2);
 $DB->Bind($stmt, $p3);
 for ($i = 0; $i < $max; $i++) {
 $p1 = ?; $p2 = ?; $p3 = ?;
 $DB->Execute($stmt);
 }For queries I know this works. I haven't seen any examples that prepare once.
$rs = $db->Execute("select city from mytab where country_id = :ci", array('ci' => 'UK'));
while ($arr = $rs->FetchRow()) {
 echo $arr['CITY'] . " \n";
}

Avg number of open cursors per session

We've been noticing a large number of open cursors open per session in our database, these users being Oracle Forms users. There are quite a few 'bells & whistles' in this vendor-supplied application with many round trips to the database. The warning we were receiving was induced by an alert that we had set up within OEM.
It got me wondering then, what a large number of cursors per process really was. We're seeing between 10-80 open cursors. The init parm OPEN_CURSORS has a default value of 50 upon installation (which is per session), so the max of 80 doesn't seem too much higher.
Are we really experiencing a large # of open cursors per session? Does someone have a means of estimating the max # of cursors that one would expect based upon CPU & memory resources? I can't find anything in the documentation.
Thanks,
Chuck

There is an OPEN_CURSORS parameter in the init.ora file,
I want to know the impact of number of open cursors on performance
(ie., how many open cursors would be appropriate for an instance)There shouldn't be a performance issue here. The value needs to be set based on how many open cursors you want to allow simultaneously. If you set the value too low, applications will get the "too many cursors open" error when they try to open a new cursor. If you're not having problems, or if you don't know how many open cursors you're likely to have, I wouldn't change this parameter.
Justin

Open cursor query - oracle 10g

Could anyone tell me which is the right query for fetching open cursor:
1.
select max(a.value) as highest_open_cur,s.sid, s.username, oc.sql_text, s.logon_time, s.status, s.machine
from v$sesstat a, v$statname b, v$parameter p, v$session s, v$open_cursor oc
where a.statistic# = b.statistic#
and b.name = 'opened cursors current'
and p.name= 'open_cursors'
and username in ('USER_ID')
and s.sid = a.sid
-- and s.status <> 'KILLED'
and oc.sid = s.sid
group by s.sid,s.username, oc.sql_text, s.logon_time, s.status, s.machine
order by s.logon_time desc
2.
SELECT user_name,sid,sql_text,count(1) total,sysdate snap_time
FROM v$open_cursor
WHERE user_name IN ('USER_ID')
GROUP BY user_name,sid,sql_text
HAVING count(1)>0;
The issue is inthe secind query we have had hardly any open cursors and from the first query we are getting quiet a lot.
Would like someone to explain me the the interpretation of both the queries.
Does Oracle 10g has a different interpretation of these tables.
How should we be reading the open cursors? and
Does anyone feel there is a better way to check for open cursors ?

...etc...
How should we be reading the open cursors? and
Does anyone feel there is a better way to check for
open cursors ?Forget cursors, if your purpose is to do some kind of research for performance tuning, just generate either the Enterprise Manager ASH or ADDM reports.

MAX OPEN CURSORS

Similar Messages

Maybe you are looking for