Oracle & .NET: Resolve – Exception calling “Fill” with “1” argument(s): ‘count’ must be non-negative.

This is one of those obscure errors that has no answer on the Web. I ran into this error trying to migrate an Oracle table to SQL Server (one of many). The issue seemed to be only with certain rows of this table as it migrated majority of the data without issues. Below is the … Continue reading Oracle & .NET: Resolve – Exception calling “Fill” with “1” argument(s): ‘count’ must be non-negative.

Advertisements

Oracle – Simple/Reusable Statement Runner Using PL/SQL Table Type (Collection)

In an Oracle anonymous block based script, how many times do you run into situations where what needs to be done remains a constant but what that logic works with, keeps changing? Parameters are a great way to do it too but in the illustration below, we are going to use PL/SQL table type (collection). … Continue reading Oracle – Simple/Reusable Statement Runner Using PL/SQL Table Type (Collection)

Oracle – Easy Date Strings (and NOT)

Whenever I type in a date strings in Oracle, I convert the strings to Date data type in my code as well as my queries without relying on the session setting for date format. I will explain why. Session date format setting: Session date format settings govern how date strings should be converted into dates (the … Continue reading Oracle – Easy Date Strings (and NOT)

Oracle – CLOB vs. VARCHAR2 – When & When Not To Use?

CLOBs Not many tables demand the use of CLOBs (Character Large Objects). CLOB data type columns can store up to 4 GB of text. When designing a new application, developers face a dilemma – I need a column where I need to store a large block of text, should I use multiple VARCHAR2 columns or … Continue reading Oracle – CLOB vs. VARCHAR2 – When & When Not To Use?

Oracle – Find A Needle In The Hay Stack – How To Pinpoint Data Errors Like “ORA-12899: value too large for column”

Nasty data-related errors: If you are looking to resolve one of these types of errors, you are in the right place. Please keep reading. ORA-01400: cannot insert NULL into (string) ORA-01401: inserted value too large for column ORA-02290: check constraint (string.string) violated ORA-02291: integrity constraint (string.string) violated - parent key not found ORA-02292: integrity constraint … Continue reading Oracle – Find A Needle In The Hay Stack – How To Pinpoint Data Errors Like “ORA-12899: value too large for column”