Ora-01401 error on a complex view

I'm getting a ora-01401 error on a view of the following structure.
SQL> desc vu_mat_product_msds_ingred;
Name Null? Type
MSDS_COMMENTS VARCHAR2(500)
MAT_PROD_MSDS_SOURCE VARCHAR2(30)
MISSING_INGRED_IND CHAR(1)
FLASH_POINT_COMMENTS VARCHAR2(100)
MSDS_ENTER_BY_ID NUMBER
CURRENT_AS_OF_DT DATE
MFG_REVISION_DT DATE
GROUP_ID NUMBER
CALC_VAPOR_PRESSURE NUMBER
CALC_VAPOR_PRESSURE_UOM VARCHAR2(5)
CALC_VAPOR_TEMPERATURE NUMBER
CALC_VAPOR_TEMPERATURE_UOM CHAR(1)
MAT_PROD_SPECIFIC_GRAVITY VARCHAR2(15)
CALC_SPECIFIC_GRAVITY NUMBER(6,4)
MAT_PROD_PROD_ID NOT NULL NUMBER
MAT_PROD_MFG_ID NOT NULL NUMBER
CLASS_ID NUMBER
CHEM_INV_IND CHAR(1)
SLED_EXEMPT_IND CHAR(1)
ACTIVE_IND CHAR(1)
WAIVER_REQD_IND CHAR(1)
ITEM_NAME VARCHAR2(60)
TRADE_NAME VARCHAR2(60)
HAZARD_CD CHAR(1)
FLASH_PT_IND CHAR(1)
FLASH_PT NUMBER
FLASH_PT_CMP CHAR(1)
FLASH_PT_SCALE_CD CHAR(1)
FLASH_PT_METHOD VARCHAR2(6)
VOC_QTY_GL NUMBER
VOC_QTY_PG NUMBER
VOC_QTY_OZ NUMBER
DISPOSAL_CD CHAR(1)
PRODUCT_STATE_CD CHAR(1)
TEMPERATURE_CD CHAR(1)
CTS_CD CHAR(1)
MAT_PROD_PPE_CD CHAR(1)
EXEMPTION_CD CHAR(1)
PCT_VOLAT_VOL NUMBER
PCT_VOLAT_WGT NUMBER
VAPOR_PRESSURE NUMBER
VAPOR_PRESSURE_UOM VARCHAR2(5)
VAPOR_TEMPERATURE NUMBER
VAPOR_TEMPERATURE_UOM CHAR(1)
VOC_COMMENTS VARCHAR2(250)
VOLATILE_LBS_GAL NUMBER
ARC1 VARCHAR2(2)
ARC2 VARCHAR2(2)
ARC3 VARCHAR2(2)
ARC4 VARCHAR2(2)
PURE_IND CHAR(1)
SITE_USAGE_IND CHAR(1)
PROPRIETARY_IND CHAR(1)
MSDS_PREP_DT DATE
MSDS_ENTER_DT DATE
HMOTW_ID NUMBER
ITEM_PRICE NUMBER(9,2)
RESTR_PRODUCT_IND CHAR(1)
CONTAINER_ID NOT NULL NUMBER
MAT_PROD_CONT_PROD_ID NOT NULL NUMBER
UPC_CD VARCHAR2(15)
SKU_NR VARCHAR2(60)
NSN VARCHAR2(15)
KIT_PART_CD VARCHAR2(2)
MFG_PART_NR VARCHAR2(60)
CONTAINER_SIZE NUMBER(10,4)
CONTAINER_SIZE_UOM VARCHAR2(3)
CNTAIN_KGRAMS_QTY NUMBER
MFGKIT_IND CHAR(1)
SEPARATE_IND CHAR(1)
TYP_CNTAIN_CD VARCHAR2(2)
CNTAIN_PRES_CD CHAR(1)
PROD_ST_CD CHAR(1)
PRODUCT_NR NOT NULL NUMBER(7)
PRODUCT_UI VARCHAR2(2)
MAT_PROD_MFG_MFG_ID NOT NULL NUMBER
CAGE NOT NULL VARCHAR2(5)
MFG_UPC VARCHAR2(7)
MFG_NAME NOT NULL VARCHAR2(50)
MFG_ADDR1 VARCHAR2(100)
MFG_ADDR2 VARCHAR2(100)
MFG_CITY VARCHAR2(100)
MFG_STATE_PROVINCE VARCHAR2(60)
MFG_POSTAL_CD VARCHAR2(30)
MFG_COUNTRY VARCHAR2(40)
MFG_EMRG_PHONE VARCHAR2(40)
MFG_INFO_PHONE VARCHAR2(40)
WEB_SITE_URL VARCHAR2(500)
PROP_SHIP_NM_ID NUMBER
MAT_PROD_MSDS_PPE_CD CHAR(1)
MSDS_ID NOT NULL NUMBER
MAT_PROD_MSDS_PROD_ID NOT NULL NUMBER
MAT_PROD_MSDS_MSDS_SOURCE VARCHAR2(30)
PUBLICATION_CD CHAR(1)
HEALTH_CD CHAR(1)
CONTACT_CD CHAR(1)
FIRE_CD CHAR(1)
REACT_CD CHAR(1)
PROT_EYE CHAR(1)
PROT_SKIN CHAR(1)
PROT_RESP CHAR(1)
FOCAL_PT_CD VARCHAR2(2)
SUPPLY_IM VARCHAR2(3)
MSDS_PREPR_NAME VARCHAR2(50)
PREP_COMPANY VARCHAR2(40)
PREP_ADD1 VARCHAR2(100)
PREP_ADD2 VARCHAR2(100)
PREP_CITY VARCHAR2(100)
PREP_STATE_PROVINCE VARCHAR2(60)
PREP_POSTAL_CD VARCHAR2(30)
MSDS_SHIP_NAME VARCHAR2(600)
MSDS_PKG_GRP VARCHAR2(3)
MSDS_UN_NA VARCHAR2(2)
MSDS_UN_NA_NR VARCHAR2(5)
MSDS_UN_NA_PAGE VARCHAR2(5)
SPEC_NR VARCHAR2(20)
SPEC_TYP_GR_CLS VARCHAR2(20)
HAZ_STOR_COMP_CD VARCHAR2(5)
HAZ_CATEGORY_1 VARCHAR2(10)
HAZ_CATEGORY_2 VARCHAR2(10)
NRC_LIC_NR VARCHAR2(15)
NET_PROP_WGT_AMMO VARCHAR2(7)
APPEAR_ODOR VARCHAR2(80)
BOIL_PT VARCHAR2(11)
MELT_PT VARCHAR2(11)
VPR_PRESSURE VARCHAR2(30)
VPR_DENSITY VARCHAR2(30)
ONETOONE_ID NUMBER(1)
VPR_TEMP VARCHAR2(30)
MAT_PROD_MSDS_SPECIFIC_GRAVITY VARCHAR2(15)
DECOMP_TEMP VARCHAR2(11)
EVAP_RATE VARCHAR2(25)
SOLUB_WATER VARCHAR2(20)
CHEM_PH VARCHAR2(11)
CORROSION_RATE VARCHAR2(8)
FLASH_POINT VARCHAR2(20)
LOW_EXPL_LTD VARCHAR2(12)
UP_EXPL_LTD VARCHAR2(12)
EXTINGUISH_MEDIA VARCHAR2(500)
SP_FIRE_FGT_PROCD VARCHAR2(800)
UN_FIRE_EXPL_HAZ VARCHAR2(500)
STABILITY VARCHAR2(3)
COND_AVOID_STAB VARCHAR2(120)
MAT_AVOID VARCHAR2(500)
HAZ_DECOMP_PROD VARCHAR2(500)
HAZ_POLY_OCCUR VARCHAR2(3)
COND_AVOID_POLY VARCHAR2(120)
LD50_LC50_MIX VARCHAR2(40)
ROUTE_ENTRY_INHALE VARCHAR2(3)
ROUTE_ENTRY_SKIN VARCHAR2(3)
ROUTE_ENTRY_INGEST VARCHAR2(3)
HLTH_HAZ_ACUTE_CRON VARCHAR2(500)
CARCIN_NTP VARCHAR2(10)
CARCIN_IARC VARCHAR2(10)
CARCIN_OSHA VARCHAR2(10)
STORAGE_TYPE VARCHAR2(10)
EXPL_CARCIN VARCHAR2(500)
SIGN_SYMPT_OVREXPOS VARCHAR2(600)
MED_COND_AGGR_EXPOS VARCHAR2(500)
EMRG_1ST_AID_PROCD VARCHAR2(600)
STEP_MAT_REL_SPILL VARCHAR2(500)
NEUTRAL_AGENT VARCHAR2(80)
WAST_DISP_METHOD VARCHAR2(600)
HAND_STOR_PRECAUT VARCHAR2(600)
OTHER_PRECAUT VARCHAR2(500)
RESP_PROT VARCHAR2(350)
VENTILATION VARCHAR2(120)
PROT_GLOVE VARCHAR2(120)
EYE_PROT VARCHAR2(120)
OTHER_PROT_EQUIP VARCHAR2(500)
WORK_HYG_PRACT VARCHAR2(500)
SUPP_SAFE_HLTH_DATA VARCHAR2(500)
SPEC_HAZ_AND_PREC VARCHAR2(650)
CHRONIC_CD CHAR(1)
CARCINOGEN_CD CHAR(1)
ACUTE_CD CHAR(1)
REPRO_TOXIN_IND CHAR(1)
ROUTE_ENTRY_EYES VARCHAR2(3)
INGREDIENTINFORMATION MAT_PRODUCT_INGRED_LIST
SQL> desc mat_product_ingred_list;
mat_product_ingred_list TABLE OF MAT_PRODUCT_INGRED_TYPE
Name Null? Type
INGRED_ID NUMBER
PRODUCT_ID NUMBER
MCM_CHEM_MSTR_ID NUMBER
CHEM_VAPOR_ID NUMBER
INGRED_SEQ_NR VARCHAR2(2)
INGRED_NIOSH VARCHAR2(9)
PERCNT VARCHAR2(7)
CALC_PERCNT NUMBER
OSHA_PEL VARCHAR2(20)
ACGIH_TLV VARCHAR2(22)
REC_LIMIT VARCHAR2(20)
MCM_EXEMPT_IND CHAR(1)
VOC_REACTIVITY_CD VARCHAR2(2)
STATE_POLLUTANT_CD VARCHAR2(10)
PERCENT_LOW NUMBER
PERCENT_HIGH NUMBER
PROPRIETARY_IND CHAR(1)
MPI_CHEM_MSTR_ID NUMBER
CHEM_CAS_NO VARCHAR2(12)
CHEM_TYPE VARCHAR2(1)
CHEM_NAME VARCHAR2(255)
CHEM_FORMULA VARCHAR2(35)
CHEM_RCRA_CD VARCHAR2(4)
MOLECULAR_WGT NUMBER(7,3)
MOLECULAR_WGT_SOURCE VARCHAR2(100)
VAPOR_PRESSURE NUMBER(8,2)
VAPOR_PRESSURE_UOM VARCHAR2(5)
VAPOR_PRESSURE_SOURCE VARCHAR2(100)
VAPOR_TEMP NUMBER
VAPOR_TEMP_UOM CHAR(1)
IRIS_IND CHAR(1)
RPT_QTY NUMBER
TPQ1 NUMBER
TPQ2 NUMBER
IC VARCHAR2(3)
OZONE_IND CHAR(1)
EHS_IND CHAR(1)
EPCRA_IND CHAR(1)
CARC_IND CHAR(1)
MPI_EXEMPT_IND CHAR(1)
CHEM_NIOSH VARCHAR2(9)
STATE_CAP NUMBER
LOCAL_CAP NUMBER
TYPE_CD CHAR(1)
CHEM_ACTIVE_IND CHAR(1)
any ideas of why the ora-01401?
Thanks in advance.

Did you by any chance buy a Re: Function will not run (and shows with red cross in SQL Developer) from Re: Calling pipelined table functions

Similar Messages

ORA-01401 error on char column with oracle oci driver

Hello,
We found a potential bug in the kodo.jdbc.sql.OracleDictionary class
shipped as source with Kodo:
In newer Kodo versions (at least in 3.3.4), the method
public void setString (PreparedStatement stmnt, int idx, String
val, Column col)
has the following code block:
// call setFixedCHAR for fixed width character columns to get padding
// semantics
if (col != null && col.getType () == Types.CHAR
&& val != null && val.length () != col.getSize ())
((OraclePreparedStatement) inner).setFixedCHAR (idx, val);
This block seems to be intended for select statements but is called on
inserts/updates also. The latter causes a known problem with the Oracle
oci driver when settings CHAR columns as FixedCHAR, which reports an
ORA-01401 error (inserted value too large for column) when definitely no
column is too long. This does not happen with the thin driver.
We reproduced this with 8.1.7 and 9.2.0 drivers.
For us we solved the problem by subclassing OracleDictionary and removing
the new code block.
Regards,
Rainer Meyer
ELAXY Financial Software & Solutions GmbH & Co. KG

Rainer-
I read at
re:'ORA-01401 inserted value too large for column' - 9i that:
"This is fixed in Oracle9i Release 2"
Can you try that version of the driver? Also, does it fail in the Oracle
10 OCI driver?
Rainer Meyer wrote:
Hello,
We found a potential bug in the kodo.jdbc.sql.OracleDictionary class
shipped as source with Kodo:
In newer Kodo versions (at least in 3.3.4), the method
public void setString (PreparedStatement stmnt, int idx, String
val, Column col)
has the following code block:
// call setFixedCHAR for fixed width character columns to get padding
// semantics
if (col != null && col.getType () == Types.CHAR
&& val != null && val.length () != col.getSize ())
((OraclePreparedStatement) inner).setFixedCHAR (idx, val);
This block seems to be intended for select statements but is called on
inserts/updates also. The latter causes a known problem with the Oracle
oci driver when settings CHAR columns as FixedCHAR, which reports an
ORA-01401 error (inserted value too large for column) when definitely no
column is too long. This does not happen with the thin driver.
We reproduced this with 8.1.7 and 9.2.0 drivers.
For us we solved the problem by subclassing OracleDictionary and removing
the new code block.
Regards,
Rainer Meyer
ELAXY Financial Software & Solutions GmbH & Co. KG
Marc Prud'hommeaux
SolarMetric Inc.

EXEC SQL Error: ORA-01401: Inserted value too large for column

Getting this SQL Error: ORA-01401: Inserted value too large for column..on an EXEC SQL Insert statement when writing to an
external Oracle DB from SAP.
On further analysis..it appears that this happens to the fields..when the string length matches the field length.
Example: Plant field is defined as char(4) on the SAP side and it is a Varchar2(4) on the Oracle side.
When a value like '1015' is passed thru a variable in the insert statement then this ORA-01401 error pops up.
No error:
   - if the value '1015' is passed directly in the insert statement to the external table (or)
   - when a value with 3 chars or less(like the first three chars..101) is passed thru a variable defined as 'Plant(4) type c'.
   - when using EXEC sql within SAP
   - when reading from the external db table
This was working ok until the Oracle Patch P9147110 was installed recently.
Any suggestions !

Hello Dvas,
what's the characterset of your external database?
What's the column definition in your external database (byte or character based)?
If you use a characeterset like UTF8 it is possible, that one character needs more than one byte and then you will run into such kind of issues if the definition is too small.
Regards
Stefan

ORA-01401 select error when using NLS_COMP=LINGUISTIC ?

Hello All.
I observed a strange thing regarding case insensitive search in XE 11.2.0-1.0 and would like to know, if I am doing someting wrong, or if XE behaves wrong.
I have tables with columns of type NVARCHAR2. If I do a simple select with a simple "like" whereclause, I get the ORA-01401 error, without having a single idea, where this error comes from. Here is my sceanrio:
1) Create a simple table
     CREATE TABLE TTEST
          ID NUMBER,
          SYM NVARCHAR2(30)
2) change your NLS_SORT and NLS_COMP settings to provide case insensitve search capabilities
     ALTER SESSION SET NLS_SORT=BINARY_CI;
     ALTER SESSION SET NLS_COMP=LINGUISTIC;
3) do a simple select on this table:
     SELECT * FROM TTEST WHERE SYM LIKE N'm%';
You will get the "ORA-01401 : inserted value to large for column" error.
If you change your NLS_COMP setting to BINARY, the select is working fine again.
Any idea what's going on here?
Thanks for help and kind regards
.............mikelm

Hi,
looks like you hit "Bug 7335665 : WRONG RESULTS WHEN NLS_COMP=LINGUISTIC AND NLS_SORT=BINARY_CI ON NVARCHAR2".
Workaround can be to not use NVARCHAR2 but varchar2
Another is to use for your query 3:
SELECT ID FROM People WHERE Lastname >= 'do' and Lastname < 'dp';The bug is stated to be patched for 12.1
Herald ten Dam
http://htendam.wordpress.com

ORA-01401 in SELECT statement !

Hi all,
We are facing a Strange problem.
Oracle Database 10.2.0.1 on Fedora Core6
AL32UTF8 Charset, NLS_LENGTH_SEMANTICS = CHAR
In a particular select statement, the database gives out ORA-01401 error:
ORA-01401: inserted value too large for column
Here is the select statement:
SELECT   a.loc_nbr AS loc_nbr, a.loc_type_code AS loc_type_code,
         TO_CHAR (a.loc_eff_dt, 'yyyy-mm-dd') AS loc_eff_dt,
         TO_CHAR (a.loc_end_dt, 'yyyy-mm-dd') AS loc_end_dt,
         a.loc_nm AS loc_nm, a.loc_city AS loc_city,
         a.loc_st_prov AS loc_st_prov, b.acct_loc_nbr AS acct_loc_nbr,
         c.noofres AS routes
    FROM loc a,
         (SELECT   c.acct_loc_nbr AS acct_loc_nbr,
                   a.loc_sys_nbr AS loc_sys_nbr_loc
              FROM loc a, loc_attr c
             WHERE a.loc_ctry_code = '040'
               AND a.loc_co_code = '001'
               AND a.loc_type_code LIKE '03%'
               AND a.loc_eff_dt <= TO_DATE ('2008-02-22', 'yyyy-mm-dd')
               AND a.loc_end_dt >= TO_DATE ('2008-02-22', 'yyyy-mm-dd')
               AND a.loc_nm > '%'
               AND LPAD (a.loc_nbr, 38, '0') LIKE '%'
               AND a.loc_short_nm LIKE '%'
               AND a.loc_city LIKE '%'
               AND NVL (a.loc_st_prov, '     ') LIKE '%'
               AND c.loc_ctry_code = a.loc_ctry_code
               AND c.loc_co_code = a.loc_co_code
               AND c.loc_nbr = a.loc_nbr
               AND c.loc_type_code = a.loc_type_code
               AND c.loc_attr_eff_dt <= a.loc_eff_dt
               AND c.loc_attr_end_dt >= a.loc_eff_dt
          ORDER BY a.loc_nbr) b,
         (SELECT   COUNT (b.loc_nbr) AS noofres,
                   a.loc_sys_nbr AS loc_sys_nbr_rt
              FROM loc a, rt_loc_assgn b
             WHERE a.loc_ctry_code = '040'
               AND a.loc_co_code = '001'
               AND a.loc_type_code LIKE '03%'
               AND a.loc_eff_dt <= TO_DATE ('2008-02-22', 'yyyy-mm-dd')
               AND a.loc_end_dt >= TO_DATE ('2008-02-22', 'yyyy-mm-dd')
               AND a.loc_nm > '%'
               AND LPAD (a.loc_nbr, 38, '0') LIKE '%'
               AND a.loc_short_nm LIKE '%'
               AND a.loc_city LIKE '%'
               AND NVL (a.loc_st_prov, '     ') LIKE '%'
               AND b.ctry_code = a.loc_ctry_code
               AND b.co_code = a.loc_co_code
               AND b.loc_nbr = a.loc_nbr
               AND (   a.loc_eff_dt BETWEEN b.rt_loc_eff_dt AND b.rt_loc_end_dt
                    OR a.loc_end_dt BETWEEN b.rt_loc_eff_dt AND b.rt_loc_end_dt
               AND b.loc_svc_type_code = 'S'
          GROUP BY a.loc_sys_nbr) c
   WHERE a.loc_sys_nbr = b.loc_sys_nbr_loc(+)
     AND a.loc_sys_nbr = c.loc_sys_nbr_rt(+)
     AND a.loc_ctry_code = '040'
     AND a.loc_co_code = '001'
     AND a.loc_type_code LIKE '03%'
     AND a.loc_eff_dt <= TO_DATE ('2008-02-22', 'yyyy-mm-dd')
     AND a.loc_end_dt >= TO_DATE ('2008-02-22', 'yyyy-mm-dd')
     AND a.loc_nm > '%'
     AND LPAD (a.loc_nbr, 38, '0') LIKE '%'
     AND a.loc_short_nm LIKE '%'
     AND a.loc_city LIKE '%'
     AND NVL (a.loc_st_prov, '     ') LIKE '%'
ORDER BY a.loc_nmWorkarounds:
- If we comment ORDER BY clause, the query works fine
- On line 49, if we surround loc_sys_nbr with TRIM() function, the query works fine
- On line 60, if we use NVL (a.loc_st_prov, '' ) LIKE '%', the query works fine
All these fields are CHAR() datatype.
Any idea what is happening here?
Thanks in advance :)

Thanks Satish,
We are hit by the bug 5874989 relating to impdp tool.

ORA-01401 with export/import

Hi!
I'm trying to migrate database from from version 8.0 on novell to 9.2 on Linux.
I have precreated all tablespaces and all tables are succesfully created. In data import stage I got lot of "ORA-01401 inserted value too large for column" errors.
Any hints would be very welcome.
Thanks
Uros

Thank you for your answer, but I'm aware of what this error means.
Lets go through the procedure one more time:
1. Export form old database (8.0) is done with exp
2. Tablespaces are manually created in new database (9.2)
3. Import of tables, users, data, etc is done with dump from step 1. During import I get a lot of ORA-01401 errors, although I didn't change dump file and data in it.
I have found somewhere on the net that this could be from characterset conversion, but I'm not shure how to set charactersets to avoid this errors.
Regards
Uros

ORA-12008:ERR OCCCURS WHEN MATERIALIZED VIEW IS REFRESHED FROM OTHER SCHEMA

Hi,
ORA-12008: Error occcurs when materialized view is refreshed from another schema, Following the output of the trace file when error occured.
/u01/app/oracle/admin/orcl92/bdump/orcl92_j000_23729.trc
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
ORACLE_HOME = /u01/app/oracle/product/10.2.0/db_1
System name: Linux
Node name: newdbserver
Release: 2.6.9-5.ELsmp
Version: #1 SMP Wed Jan 5 19:30:39 EST 2005
Machine: i686
Instance name: orcl92
Redo thread mounted by this instance: 1
Oracle process number: 164
Unix process pid: 23729, image: oracle@newdbserver (J000)
*** SERVICE NAME:(SYS$USERS) 2008-05-23 10:30:51.848
*** SESSION ID:(462.21166) 2008-05-23 10:30:51.848
*** 2008-05-23 10:30:51.848
ORA-12012: error on auto execute of job 766
ORA-12008: error in materialized view refresh path
ORA-00942: table or view does not exist
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2255
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2461
ORA-06512: at "SYS.DBMS_IREFRESH", line 683
ORA-06512: at "SYS.DBMS_REFRESH", line 195
ORA-06512: at line 1
Regards,
Abhishek

Hi Damorgan,
As i said, when refresh materialized view from another schema, mentioned error occurs.
I have also granted accees explicitely still following error occurs.
ORA-12008: error in materialized view refresh path
ORA-00942: table or view does not exist
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2255
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2461
ORA-06512: at "SYS.DBMS_IREFRESH", line 683
ORA-06512: at "SYS.DBMS_REFRESH", line 195
ORA-06512: at line 1
Regards,
Abhishek
Message was edited by:
AbhishekRathod(user559364)

Switch back from ORA-12899 to old ORA-01401 handling?

Hi,
we are using a 4GL language which uses its own native OCI-based SQL router to connect to ORACLE. After upgrading to 10g we no longer get ORA-01401 error, when inserting values which are too long to fit in database column. Even worse this native router fails to report the new ORA-12899 error, so that the failing INSERT cannot be trapped by the calling application.
Is there a way to configure ORACLE10g to use the old 1401 error handling untill the vendor will fix their SQL router to be compatible with 10g?
TIA,
Stefan

We have the same problem. With our application, we are locked to the Oracle 9 client, because the Oracle Router of Gupta Team Developer (3.1) ignores ORA-12899 so the error happens unnoticed by the user. Any chance to get error ORA-01401 reported in Oracle 10 client instead of ORA-12899?
Some time next year we plan to move on to Team Developer 5.1 where the problem should be solved, but at the moment, we do not have a certified client for Vista (requieres Oracle 10 client or higher).

Snapshot refresh error: ora-01401 inserted value too large for column

I have an error ora-01401 "Inserted value too large for column" when I try to do a refresh on a group at the materialized view site.
My model is 1 master replicating to a readonly materialized view site. I have 2 refresh groups for separate sets of tables. 1 refresh group work fine...the other I got the above error.
I have doubled the rbs and system tablespace without any help thinking that I must be running out of default rollback segment space.
Anyone has this before?

The error is related to a field, not to any tablespace. This normaly happens to me when I change the lenght or resolution of a field in the base tables. The structure changes don't "flow" to the materialized view! I must "regenerate" them. Normally droping and creating it again to make them receive the new lenght of that field.
Sometimes, when the field changed is not part of any primary key I have changes directly the field in the materialized view as if it was a normal table.
Hope this helps
Luis

ORA-00604: error occurred at recursive SQL level 1 (Call to a Oracle View)

I have created a view that refers to a package function within the sql select.
Like
E.x
CREATE OR REPLACE VIEW VW_TAX
as select
test_pkg.fn_get_gl_value(acct_id) desired_col1,
test_pkg.fn_get_gl_desc_value(acct_id) desired_col2
From tables a, b
a.col= b.col
The sample function( fn_get_gl_value) is embedded into a package (test_pkg).
Function fn_get_gl_value:
It earlier referred to table A1, B1, C1 and this query took really long, Therefore I used object type tables and stored the values required once within the package when it is invoked. Later I used the Tables A1, B1 and C1(table Cast from the type Table Loaded in Package Memory)
The query was fast and fine, but now when I try to re-use the view
select * from VW_TAX
where acct_id = '02846'
It fails with this message
09:32:35 Error: ORA-00604: error occurred at recursive SQL level 1
ORA-01000: maximum open cursors exceeded
Note: The database is Oracle8i Enterprise Edition Release 8.1.7.4.0.
Maximum cursors database is 500
Please let me know if there is any known solution,
Appreciate all your help
Thanks
RP

Seems like your OPEN_CURSORS init.ora parameter is set too low.
See Metalink Note:1012266.6 for details.
   ORA-01000: "maximum open cursors exceeded"
        Cause: A host language program attempted to open too many cursors.
               The initialization parameter OPEN_CURSORS determines the
               maximum number of cursors per user.
       Action: Modify the program to use fewer cursors. If this error occurs
               often, shut down Oracle, increase the value of OPEN_CURSORS,
               and then restart Oracle.

ORA-01033 Error cannot be traced in the alert log or v$views

Hello There,
I'm hoping you can shed some light on what seems a rather odd occurrence on our Production Oracle Instance.
Before i elaborate on the nature of the problem, I must confess that i am not an Oracle DBA and have been compelled to post this query since i have no joy from the in house DBA community on the origins of this error.
We've had an ORA-01033 error being issued by our ETL installation (deployed on a Linux machine) a couple of days ago whence trying to extract some data from the Oracle instance (during overnight DataWarehouse loads) which has consequently aborted the loads necessitating a cleanup.
This event has already occurred twice before, the first time being a month ago when the event was captured in the v$instance (using the Startup time column where the timestamp corroborates to the first time we experienced this issue and also ackowledged by the DBA team) and also in the V$Dataguard_status.
Since then, This error has been generated twice although there seems to be no evidence of this in either the Oracle alert log(as confirmed by DBA team) or in any of the v$views (as pointed out by Tom in an earlier post) such as DBA_LOGSTDBY_HISTORY, v$logstdby_state, $logstdby_stats, dba_logstdby_log, dba_logstdby_events,v$dataguard_status, v$dataguard_stats, v$dataguard_config,v$database,v$database_incarnation, v$managed_standby, v$standby_log, v$instance. I searched these views since i suspected a latency issue during a failover which could be the reason for the
ORA-01033 but found nothing.
The DBA team have pretty much disowned this issue since they claim to not have any actual evidence of this from the logs and this is the crux of the matter here.
The Problem i have as the downstream "recepient" of this error is to prove to the DBA team that this is indeed a genuine issue with the Oracle instance affecting it's availability and concomittantly affecting the DW loads.
FYI, The Oracle instance is in Failover mode, so it's swiftly back online after bombing out for a few seconds.
Also, I don't have access to the Alert log as it's a Production environment and employs restricted access policy to the server.
Having said that, Is there anything else besides the obvious ORA errors that should be looked for in the Alert log?
Where else can ORA-01033 errors be traced/traced in the Dictionary besides the Alert Log?
Thoughts??
Regards

Thank You John for that query, but i'm on V10.2 and this view is relevant for 11g and beyond i believe.
Perhaps there is an equivalent for V10g?
I am also a bit bemused by the comment earlier about no trace being left behind if the DBA's performed a manual restart, surely it doesn't matter how the DB is restarted, the event is captured in the dictionary?
In the meantime, I've got a copy of the Alert log and have found redo log issues (DBWR/LGWR) very close to the time (a min after ORA-01033) of the shutdown event.
ALTER SYSTEM ARCHIVE LOG
Thread 1 cannot allocate new log, sequence 117732
Checkpoint not complete
I've looked into this a fair bit and this error apparently causes Oracle to suspend all processing on the database until the log switch is made.
Is this the causal link for my issue?
Does " suspend all processing on the database " actually translate into an actual ORA-01033 error (or some form of) when the ETL application is trying to connect to and extract data from the Oracle database at that time?
Edited by: shareeman on 16-Oct-2012 03:50

ORA-12008: error in materialized view refresh path with ORA-01652

I have a temp tablespace with 2 tempfiles of 2GB each (total 4GB) but still refresh of materialized view is failing with following error:
5646690 - BIS Materialized View Refresh Program
ORA-12008: error in materialized view refresh path
ORA-01652: unable to extend temp segment by 128 in tablespace TEMP1
I checked and temp ts is completly filled
SQL> select TABLESPACE_NAME, BYTES_USED, BYTES_FREE from V$TEMP_SPACE_HEADER;
TABLESPACE_NAME BYTES_USED BYTES_FREE
TEMP1 2147483648 0
TEMP1 2147483648 0
My question is how do I find out how much space I need for temp tablespace. what 's the best practise to size temp tablespace when running refresh. refresh is done by client who is submitting a request thru ebiz apps so I 'd like to size it correctly without having to keep guessing.
Thanks so much in advance for any help

Hello,
Temp tablespace size depends how much sort by , order by operation your application performing. You can create new temp tablespace and drop old one with bigger file size
CREATE TEMPORARY TABLESPACE TEMP02 TEMPFILE '\mypath_to_temp\TEMP02' SIZE 256M REUSE AUTOEXTEND ON NEXT 256M MAXSIZE 8192M EXTENT MANAGEMENT LOCAL;
ALTER DATABASE DEFAULT TEMPORARY TABLESPACE TEMP02;
Drop tablespace temp including contents; -- Make sure you delete on temp data files.Here is link for your reading purpose
http://www.idevelopment.info/data/Oracle/DBA_tips/Tablespaces/TBS_3.shtml
Regards
Edited by: OrionNet on Mar 6, 2009 6:15 PM

Materialized View, ORA-12008: error in materialized view refresh path

I want to refresh a materialized view, but I get an ORA-12008 error.
Does anybody have an idea? I do not find any errors in my refresh statement.
CREATE MATERIALIZED VIEW scott.dummy_mv
TABLESPACE test
BUILD IMMEDIATE
USING INDEX TABLESPACE idx_test
REFRESH
     START WITH sysdate
     NEXT ROUND(SYSDATE)+5/24
     WITH PRIMARY KEY
ENABLE QUERY REWRITE
AS
SELECT KM.ID ID
          ,KM.USERNAME USERNAME
       ,KM.ABTID ABTID
FROM my_table KM
scott@orcl>desc dummy_mv
Name                                      Null?    Typ
ID                                        NOT NULL NUMBER(4)
USERNAME                                  NOT NULL VARCHAR2(30)
ABTID                                     NOT NULL NUMBER(4)
scott@orcl>
BEGIN
SYS.DBMS_JOB.REMOVE(6579);
COMMIT;
END;
DECLARE
X NUMBER;
BEGIN
SYS.DBMS_JOB.SUBMIT
( job       => X
   ,what      => 'dbms_refresh.refresh(''"scott"."dummy_mv"'');'
   ,next_date => to_date('07.01.2009 05:00:00','dd/mm/yyyy hh24:mi:ss')
   ,interval => 'ROUND(SYSDATE)+5/24              '
   ,no_parse => FALSE
SYS.DBMS_OUTPUT.PUT_LINE('Job Number is: ' || to_char(x));
COMMIT;
END;
scott@orcl>exec dbms_refresh.refresh('dummy_mv');
BEGIN dbms_refresh.refresh('dummy_mv'); END;
FEHLER in Zeile 1:
ORA-12008: error in materialized view refresh path
ORA-00947: not enough values
ORA-06512: in "SYS.DBMS_SNAPSHOT", Zeile 820
ORA-06512: in "SYS.DBMS_SNAPSHOT", Zeile 877
ORA-06512: in "SYS.DBMS_IREFRESH", Zeile 683
ORA-06512: in "SYS.DBMS_REFRESH", Zeile 195
ORA-06512: in Zeile 1
scott@orcl>

crupper wrote:
I get the same error:
scott@orcl>exec dbms_mview.refresh('dummy_mv','c');
BEGIN dbms_mview.refresh('dummy_mv','c'); END;
FEHLER in Zeile 1:
ORA-12008: error in materialized view refresh path
ORA-00947: not enough values
ORA-06512: in "SYS.DBMS_SNAPSHOT", Zeile 820
ORA-06512: in "SYS.DBMS_SNAPSHOT", Zeile 877
ORA-06512: in "SYS.DBMS_SNAPSHOT", Zeile 858
ORA-06512: in Zeile 1
I would first check the "query" information of the DBA_SNAPSHOTS/DBA_MVIEWS dictionary views if it reveals anything obvious.
But it looks more like an internal error while processing the refresh. You can get more information about the error by tracing the session. A "alter session set sql_trace = true;" before running the refresh should be sufficient. Disconnect afterwards and check the generated trace file for errors either using "tkprof" and checking the output or by manually searching for "err=" in the trace file.
Which 4-digit version of Oracle are you using?
Regards,
Randolf
Oracle related stuff blog:
http://oracle-randolf.blogspot.com/
SQLTools++ for Oracle (Open source Oracle GUI for Windows):
http://www.sqltools-plusplus.org:7676/
http://sourceforge.net/projects/sqlt-pp/

ORA-12008: error in materialized view refresh path... Bug?

SQL> select * from v$version;
BANNER
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
PL/SQL Release 11.2.0.3.0 - Production
CORE    11.2.0.3.0      Production
TNS for Linux: Version 11.2.0.3.0 - Production
NLSRTL Version 11.2.0.3.0 - Production
SQL> drop materialized view log on test_tbl;
Materialized view log dropped.
SQL> drop materialized view mv_test_tbl;
Materialized view dropped.
SQL> drop table test_tbl;
Table dropped.
SQL> create table test_tbl(
2   test_id   number(10)   primary key,
3   test_name varchar2(10) not null)
4 ;
Table created.
SQL> insert into test_tbl values (1,'bob');
1 row created.
SQL> insert into test_tbl values (2,'joe');
1 row created.
SQL> insert into test_tbl values (3,'john');
1 row created.
SQL> commit;
Commit complete.
SQL> create materialized view log on test_tbl
2 with primary key , rowid, sequence
3 (
4   test_name
5 )
6 including new values;
Materialized view log created.
SQL> create materialized view mv_test_tbl
2 refresh fast on commit
3 as
4 select test_id,
5         test_name
6 from   test_tbl;
Materialized view created.
SQL> update test_tbl set test_name = 'hello' where test_id = 1000;
0 rows updated.
SQL> commit;
Commit complete.Ok, so that's all good. Now if I create the materialized view log with the COMMIT SCN option:
SQL> drop materialized view log on test_tbl;
Materialized view log dropped.
SQL> drop materialized view mv_test_tbl;
Materialized view dropped.
SQL> create materialized view log on test_tbl
2 with primary key , rowid, sequence
3 (
4   test_name
5 ),
6 commit scn
7 including new values;
Materialized view log created.
SQL> create materialized view mv_test_tbl
2 refresh fast on commit
3 as
4 select test_id,
5         test_name
6 from   test_tbl;
Materialized view created.
SQL> update test_tbl set test_name = 'hello' where test_id = 1000;
0 rows updated.
SQL> commit;
commit
ERROR at line 1:
ORA-12008: error in materialized view refresh path
ORA-01006: bind variable does not exist
SQL>Committing an update that updates no rows against a master table for a single table fast refreshable materialized view results in the error above when the materialized view log on the master table is created with the COMMIT SCN option. I'm guessing that this isn't how things are supposed to work. Or am I missing something here? Anyone else encountered this before?
Cheers.
Edited by: Stain on Jan 25, 2013 1:27 PM

Query Rewrite is an option for a Materialized View, not a Materialized View Log. Also, query rewrite is used as an optimization technique which "transforms a SQL statement expressed in terms of tables or views into a statement accessing one or more materialized views that are defined on the detail tables". I don't think it plays any role in the refresh path.
Regardless, it made no difference.
SQL> create materialized view mv_test_tbl
2 refresh fast on commit
3 ENABLE QUERY REWRITE
4 as
5 select test_id,
6         test_name
7 from   test_tbl
8 ;
Materialized view created.
SQL> update test_tbl set test_name = 'hello' where test_id = 1000;
0 rows updated.
SQL> commit;
commit
ERROR at line 1:
ORA-12008: error in materialized view refresh path
ORA-01006: bind variable does not exist
SQL>Edited by: Stain on Jan 25, 2013 2:06 PM

ORA-12096: error in materialized view log

Hi All,
I had created a fast refresh materialized view. Log was also created.
Now i dropped the mv and the logs.
But now every time i update or insert into this customer table i get error message.
ORA-12096: error in materialized view log on Customer
ORA-00942: table or view does not exist
There are entries in the DBA_MVIEW_LOGS for customer table.
Please suggest.

Hi,
What database version are you on?
And do you have access to Metalink/My Oracle Support?
Found this, by the way:
ORA-12096: error in materialized view log on <table>
If problems occur when you try to access a log file for a materialized view, the system issues an ORA-12096 error message which is followed by the actual error. If the ORA-12096 error message is accompanied by an ORA-00942 message, the problem may be due to an online reorganization that was only partially undone. In this case, you can drop the log file for the materialized view manually (after you have verified that it is no longer required):
DROP MATERIALIZED VIEW LOG ON <table>;
Edited by: hoek on Jul 29, 2009 2:15 PM

Ora-01401 error on a complex view

Similar Messages

Maybe you are looking for