Why do I run out of resources during updates with Oracles database link?
When you use Oracle’s database link to update your database, you may get error “maximum number of temporary table locks exceeded” even if you close your result sets and statements when you finish. The database link is an object in the local database that allows you to access tables, views, and such in a remote database. The database link is controlled by the Oracle server, so the driver has no control over its use of resources. The link appears to perform the commit (since other processes could see the records that were being created), but it doesn’t free any resources until the connection is closed. The solution is to remove the database link and use the JDBC driver to do your selects, inserts, and updates.
When you use Oracle’s database link to update your database, you may get error “maximum number of temporary table locks exceeded” even if you close your result sets and statements when you finish. The database link is an object in the local database that allows you to access tables, views, and such in a remote database. The database link is controlled by the Oracle server, so the driver has no control over its use of resources. The link appears to perform the commit (since other processes could see the records that were being created), but it doesn’t free any resources until the connection is closed. The solution is to remove the database link and use the JDBC driver to do your selects, inserts, and updates.
A. When you use Oracle’s database link to update your database, you may get error “maximum number of temporary table locks exceeded” even if you close your result sets and statements when you finish. The database link is an object in the local database that allows you to access tables, views, and so forth in a remote database. The database link is controlled by the Oracle server, so the driver has no control over its use of resources. The link appears to perform the commit (since other processes could see the records that were being created), but it doesn’t free any resources until the connection is closed. The solution is to remove the database link and use the JDBC driver to do your selects, inserts, and updates.
When you use Oracle’s database link to update your database, you may get error “maximum number of temporary table locks exceeded” even if you close your result sets and statements when you finish. The database link is an object in the local database that allows you to access tables, views, and so forth in a remote database. The database link is controlled by the Oracle server, so the driver has no control over its use of resources. The link appears to perform the commit (since other processes could see the records that were being created), but it doesn’t free any resources until the connection is closed. The solution is to remove the database link and use the JDBC driver to do your selects, inserts, and updates. Source : www.javabeat.
