/explore
|
You are here 
|
www.greenstechnologys.com | ||
| | | | |
traininginchennai.in
|
|
| | | | | PL/SQL Cursors - Learn PL/SQL programming in simple and easy steps starting with PL/SQL syntax, Environment Setup, Operators, Transactions, Date and Time, data types, variables, constants, records, conditional statements, iterative statements, cursors, procedures, functions, exception handling, triggers, packages, collections, external procedures, arrays, strings, dbms output. | |
| | | | |
www.craigpardey.com
|
|
| | | | | I came across an interesting problem recently in some JDBC code that was inserting rows into a Netezza database. The Java code was doing something like this: Statement stmt ... for( SomeObject o : listOfObjects) { String sql = "INSERT INTO tbl(col1, col2) values (?,?)"; ... stmt.addBatch(sql); } stmt.executeBatch(); On the "executeBatch()", a SQLException was being thrown that said "failed to create external table for bulk load". What? But it wasn't a bulk load. There were no external tables involved - it was a batch of vanilla inserts. | |
| | | | |
jonathanlewis.wordpress.com
|
|
| | | | | Here's a simple detail about bind peeking (during optimisation) that makes a big difference to "fetch first/next" queries. The optimizer knows about your bind types, and can peek at the bind values - but that doesn't mean it will do something sensible with them. Here's a little model to demonstrate the problem - starting with... | |
| | | | |
tanelpoder.com
|
|
| | | Snapper used to require access to DBMS_LOCK, so it could sleep for X seconds between the "before" and "after" performance data snapshots. Now it is possible to get away without using DBMS_LOCK. Instead you will run Snapper twice, once for taking the "before" snapshot, then run your workload and then run Snapper again for taking the "after" snapshot and print the output. So, the usual way of running snapper is this: - Linux, Oracle, SQL performance tuning and troubleshooting training & writing. | ||
