ORA-01401
Hi,
I am getting an error message "ORA-01401: inserted value too large for column" when I try to execute a query which copies data from a table in one database and puts it in a table in another database. Both the tables have similar descriptions (all the row names and datatypes match in both tables). The character set is the same for both databases. Please help.
Thanks in advance.
aks
Below is the query which loads the data :
FOR i IN c_insert_table_subcase(sSperiod, sEperiod) LOOP
icount_insert := icount_insert + 1;
INSERT INTO TABLE_SUBCASE (
objid,
title,
s_title,
-- description,
reopen_flag,
id_number,
required_date,
creation_time,
yank_flag,
behavior,
sub_type,
fcs_cc_notify,
ownership_stmp,
modify_stmp,
dist,
elapsed_time,
warning_time,
dev,
subc_prevq2queue,
subc_currq2queue,
subc_wip2wipbin,
subcase2case,
subc_owner2user,
subc_state2condition,
subc_orig2user,
subc_empl2employee,
subc_priorty2gbst_elm,
subc_svrity2gbst_elm,
subc_casests2gbst_elm,
subc_rip2ripbin,
aux_subcase2act_entry,
subc_gen2cls_factory,
subcase2job,
x_action_details,
x_action_id,
x_appointment_date,
x_auto_allocation,
x_auto_close,
x_child2subcase,
x_child_count,
x_importance_class,
x_job_type,
x_link_delay,
x_link_type,
x_linked_wms_id,
x_parent_id,
x_parent_ind,
x_parent_wm_nfm_id,
x_plan_no,
x_previous_queue,
x_ptw_iofficer,
x_ptw_issued,
x_ptw_itime,
x_ptw_reqd,
x_ptw_tel,
x_required_by,
-- x_scase2x_code_1141,
x_scase2x_dummy,
x_scase2x_mg_route,
x_scase2x_wms_contact,
x_task_jeop_status,
x_wm_access_finish,
x_wm_access_start,
x_wm_acdayname,
x_wm_acfinishdate,
x_wm_acindicator,
x_wm_acstartdate,
x_wm_nodeident1141,
x_wm_reason,
x_wm_replace_notes,
x_wm_responsecode,
x_wm_systemtype,
x_wm_tasktypeid,
x_wmr_actionstatus,
x_wmr_allocatedpin,
x_wmr_expectedfinish,
x_wmr_expectedstart,
x_wmr_failurecode,
x_wmr_failurereason,
x_wmr_personname,
x_wmr_requeststatus,
x_wms_date_ack,
x_wms_id,
x_workforce,
x_wmr_clearcode,
x_wmr_closurecode,
x_wmr_incompletereasoncode
,x_prog_type
,x_wm_earlystrtdt
,x_wm_latestrtdt
,x_wm_seclatefnshdt
,x_wm_targlatefindt
,x_mainworklocation)
VALUES (
i.objid,
i.title,
i.s_title,
-- i.description,
i.reopen_flag,
i.id_number,
i.required_date,
i.creation_time,
i.yank_flag,
i.behavior,
i.sub_type,
i.fcs_cc_notify,
i.ownership_stmp,
i.modify_stmp,
i.dist,
i.elapsed_time,
i.warning_time,
i.dev,
i.subc_prevq2queue,
i.subc_currq2queue,
i.subc_wip2wipbin,
i.subcase2case,
i.subc_owner2user,
i.subc_state2condition,
i.subc_orig2user,
i.subc_empl2employee,
i.subc_priorty2gbst_elm,
i.subc_svrity2gbst_elm,
i.subc_casests2gbst_elm,
i.subc_rip2ripbin,
i.aux_subcase2act_entry,
i.subc_gen2cls_factory,
i.subcase2job,
i.x_action_details,
i.x_action_id,
i.x_appointment_date,
i.x_auto_allocation,
i.x_auto_close,
i.x_child2subcase,
i.x_child_count,
i.x_importance_class,
i.x_job_type,
i.x_link_delay,
i.x_link_type,
i.x_linked_wms_id,
i.x_parent_id,
i.x_parent_ind,
i.x_parent_wm_nfm_id,
i.x_plan_no,
i.x_previous_queue,
i.x_ptw_iofficer,
i.x_ptw_issued,
i.x_ptw_itime,
i.x_ptw_reqd,
i.x_ptw_tel,
i.x_required_by,
-- i.x_scase2x_code_1141,
i.x_scase2x_dummy,
i.x_scase2x_mg_route,
i.x_scase2x_wms_contact,
i.x_task_jeop_status,
i.x_wm_access_finish,
i.x_wm_access_start,
i.x_wm_acdayname,
i.x_wm_acfinishdate,
i.x_wm_acindicator,
i.x_wm_acstartdate,
i.x_wm_nodeident1141,
i.x_wm_reason,
i.x_wm_replace_notes,
i.x_wm_responsecode,
i.x_wm_systemtype,
i.x_wm_tasktypeid,
i.x_wmr_actionstatus,
i.x_wmr_allocatedpin,
i.x_wmr_expectedfinish,
i.x_wmr_expectedstart,
i.x_wmr_failurecode,
i.x_wmr_failurereason,
i.x_wmr_personname,
i.x_wmr_requeststatus,
i.x_wms_date_ack,
i.x_wms_id,
i.x_workforce,
i.x_wmr_clearcode,
i.x_wmr_closurecode,
i.x_wmr_incompletereasoncode
,i.x_prog_type
,i.x_wm_earlystrtdt
,i.x_wm_latestrtdt
,i.x_wm_seclatefnshdt
,i.x_wm_targlatefindt
,i.x_mainworklocation);
and below is the definition of the cursor:
CURSOR c_insert_table_subcase(sSperiod IN VARCHAR2, sEperiod IN VARCHAR2) IS
SELECT /*+RULE */
s.objid
,s.title
,s.s_title
-- ,s.description
,s.reopen_flag
,s.id_number
,s.required_date
,s.creation_time
,s.yank_flag
,s.behavior
,s.sub_type
,s.fcs_cc_notify
,s.ownership_stmp
,s.modify_stmp
,s.dist
,s.elapsed_time
,s.warning_time
,s.dev
,s.subc_prevq2queue
,s.subc_currq2queue
,s.subc_wip2wipbin
,s.subcase2case
,s.subc_owner2user
,s.subc_state2condition
,s.subc_orig2user
,s.subc_empl2employee
,s.subc_priorty2gbst_elm
,s.subc_svrity2gbst_elm
,s.subc_casests2gbst_elm
,s.subc_rip2ripbin
,s.aux_subcase2act_entry
,s.subc_gen2cls_factory
,s.subcase2job
,s.x_action_details
,s.x_action_id
,s.x_appointment_date
,s.x_auto_allocation
,s.x_auto_close
,s.x_child2subcase
,s.x_child_count
,s.x_importance_class
,s.x_job_type
,s.x_link_delay
,s.x_link_type
,s.x_linked_wms_id
,s.x_parent_id
,s.x_parent_ind
,s.x_parent_wm_nfm_id
,s.x_plan_no
,s.x_previous_queue
,s.x_ptw_iofficer
,s.x_ptw_issued
,s.x_ptw_itime
,s.x_ptw_reqd
,s.x_ptw_tel
,s.x_required_by
-- ,s.x_scase2x_code_1141
,s.x_scase2x_dummy
,s.x_scase2x_mg_route
,s.x_scase2x_wms_contact
,s.x_task_jeop_status
,s.x_wm_access_finish
,s.x_wm_access_start
,s.x_wm_acdayname
,s.x_wm_acfinishdate
,s.x_wm_acindicator
,s.x_wm_acstartdate
,s.x_wm_nodeident1141
,s.x_wm_reason
,s.x_wm_replace_notes
,s.x_wm_responsecode
,s.x_wm_systemtype
,s.x_wm_tasktypeid
,s.x_wmr_actionstatus
,s.x_wmr_allocatedpin
,s.x_wmr_expectedfinish
,s.x_wmr_expectedstart
,s.x_wmr_failurecode
,s.x_wmr_failurereason
,s.x_wmr_personname
,s.x_wmr_requeststatus
,s.x_wms_date_ack
,s.x_wms_id
,s.x_workforce
,s.x_wmr_clearcode
,s.x_wmr_closurecode
,s.x_wmr_incompletereasoncode
,s.x_prog_type
,s.x_wm_earlystrtdt
,s.x_wm_latestrtdt
,s.x_wm_seclatefnshdt
,s.x_wm_targlatefindt
,s.x_mainworklocation
FROM TABLE_SUBCASE ms, TABLE_SUBCASE@pew_cl.world s
WHERE s.objid = ms.objid(+)
AND ms.objid IS NULL
AND s.creation_time BETWEEN SYSDATE-sSperiod AND SYSDATE-sEperiod;
This was working fine till yesterday, when it started throwing the error.
Thanks
aks
Similar Messages
-
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
-
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. KGRainer-
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. -
ORA-01401: inserted value too large for column from 9i to 8i
Hi All,
Am trying to get the data from 9.2.0.6.0 to 8.1.7.0.0.
The character sets in both of them are as follows
9i
NLS_NCHAR_CHARACTERSET : AL16UTF16
NLS_CHARACTERSET : AL32UTF8
8i
NLS_NCHAR_CHARACTERSET : UTF8
NLS_CHARACTERSET : UTF8
And the structure of the Table in 9i which am trying to pull is as follows.
SQL> desc xyz
Name Null? Type
PANEL_SITE_ID NOT NULL NUMBER(15)
PANELIST_ID NUMBER
CHECKSUM VARCHAR2(150)
CONTACT_PHONE VARCHAR2(100)
HH_STATUS NUMBER
HH_STATUS_DT DATE
HH_RECRUITMENT_PHONE VARCHAR2(100)
HH_RECRUITMENT_DT DATE
FIRST_NET_USAGE_DT DATE
INSTALL_DT DATE
FNAME VARCHAR2(4000)
LNAME VARCHAR2(4000)
EMAIL_ADDRESS VARCHAR2(200)
EMAIL_VALID NUMBER
PASSWORD VARCHAR2(4000)
And by connecting to one of the 8i schema am running the following script
CREATE TABLE GPMI.GPM_HOUSEHOLDBASE_FRMP AS
SELECT PANEL_SITE_ID,
PANELIST_ID,
LTRIM(RTRIM(CHECKSUM)) CHECKSUM,
LTRIM(RTRIM(CONTACT_PHONE)) CONTACT_PHONE,
HH_STATUS, HH_STATUS_DT,
LTRIM(RTRIM(HH_RECRUITMENT_PHONE)) HH_RECRUITMENT_PHONE,
HH_RECRUITMENT_DT,
FIRST_NET_USAGE_DT,
INSTALL_DT, LTRIM(RTRIM(FNAME)) FNAME,
LTRIM(RTRIM(LNAME)) LNAME,
LTRIM(RTRIM(EMAIL_ADDRESS)) EMAIL_ADDRESS,
EMAIL_VALID,
PASSWORD
FROM [email protected];
Am gettinh the following error.
Can anyone of you fix this one.
PASSWORD
ERROR at line 14:
ORA-01401: inserted value too large for column
Thanks in Advance
SudarshanAdditionally I found this matrix, which explains your problem:
UTF8 (1 to 3 bytes) AL32UTF8 (1 to 4 bytes)
MIN MAX MIN MAX
CHAR 2000 666 2000 500
VARCHAR2 4000 1333 4000 1000 */
For column PASSWORD the maximum length is used (4000). UTF8 uses maximal 3 bytes for a character, while AL32UTF8 may use up to 4 characters. So a column defined in AL32UTF8 may contain characters, which do not fit in a corresponding UTF8 character. -
'ORA-01401 inserted value too large for column' - 9i
I am migrating a java application from 8i to 9i. The application is writing data to a oracle 8i database without any problem.
When the underlying database source is switched to oracle 9i database(same databaseschema as 8i) by pointing to 9i instance , the application is
encountering the error: 'ORA-01401 inserted value too large for column' when trying to insert a particular field. The fileld is declared as varchar2(400) in the both the database.
The debug output from application also shows that the column data being inserted as 10 characters.The insert statement from SQLPLUS works fine. So it's looks like an issue with the JDBC driver for the 9i server. I am wondering if anyone has observed such strange behavior.
Thanks
VijayVijay,
Are you using OCI driver ? There is a known issue with OCI driver when using setFixedCHAR before an INSERT statement. This problem only happens with a string of length zero. There is no known issue with THIN Driver. This is fixed in Oracle9i Release 2.
regards
Debu Panda
Oracle -
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. -
SQL loader error ORA-01401:
I am trying to import a .dat file using SQL loader and
i am getting error:ORA-01401: inserted value too large for column and i tried changing the column length to bigger too.
TABLE STRUCTURE
create table NOTE
NOTE_EFF_DATE NUMBER,
NOTE_NDC_NUMBER NUMBER,
NOTE_PREV_NDC_NUMBER NUMBER,
NOTE_DEA_CLASS_CD VARCHAR2(5),
NOTE_PRODUCT_CTGRY_CD VARCHAR2(5),
NOTE_PRODUCT_NAME VARCHAR2(40),
NOTE_FORM_CODE VARCHAR2(5),
NOTE_PRODUCT_STRENGTH VARCHAR2(35),
NOTE_PRODUCT_MSUR_CD VARCHAR2(5),
NOTE_PRODUCT_PKG_SZ NUMBER,
NOTE_PRODUCT_PKG_QTY_CD VARCHAR2(6),
NOTE_THRPTC_CLS_CD NUMBER,
NOTE_AWP_CRT_PRC_EF_DT NUMBER,
NOTE_AWP_CRT_PRC NUMBER,
NOTE_AWP_UNT_PRC NUMBER,
NOTE_AWP_1ST_PRV_UNT_PRC NUMBER
DATA IN .dat FILE:
093083100002035151 401DARVOCET-N 50 TAB 01000EA 0000000001831780008120000008120000007250
093083100002011104 08SODIUM SALICYLATE CAP10 GR 01000EA 2808020070880920005519000005519000005158
.dat FILE format/structure
01 NOTE-REC.
05 NOTE-KEY.
10 NOTE-EFF-DATE.
15 NOTE-EFF-C PIC X(01).
15 NOTE-EFF-YY PIC X(02).
15 NOTE-EFF-MM PIC X(02).
15 NOTE-EFF-DD PIC X(02).
10 NOTE-NDC-NUMBER.
15 NOTE-NDC-NUM-5 PIC X(05).
15 NOTE-NDC-NUM-4 PIC X(04).
15 NOTE-NDC-NUM-2 PIC X(02).
05 NOTE-PREV-NDC-NUMBER.
10 NOTE-NDC-NUM-5 PIC X(05).
10 NOTE-NDC-NUM-4 PIC X(04).
10 NOTE-NDC-NUM-2 PIC X(02).
05 NOTE-DEA-CLASS-CD PIC X(01).
05 NOTE-PRODUCT-CTGRY-CD PIC X(02).
05 NOTE-PRODUCT-NAME PIC X(35).
05 NOTE-FORM-CODE PIC X(03).
05 NOTE-PRODUCT-STRENGTH PIC X(25).
05 NOTE-PRODUCT-MSUR-CD PIC X(02).
05 NOTE-PRODUCT-PKG-SZ PIC 9(05).
05 NOTE-PRODUCT-PKG-QTY-CD PIC X(03).
05 NOTE-THRPTC-CLS-CD PIC 9(10).
05 NOTE-AWP-CRT-PRC-EF-DT PIC 9(05).
05 NOTE-AWP-CRT-PRC PIC 9(05)V99.
05 NOTE-AWP-UNT-PRC PIC 9(04)V9(05).
05 NOTE-AWP-1ST-PRV-UNT-PRC PIC 9(04)V9(05).
Control FILE:
LOAD DATA
INFILE 'NCD.dat'
BADFILE 'NCD.bad'
DISCARDFILE 'NCD.dsc'
INTO TABLE NOTE
REPLACE
FIELDS TERMINATED BY ' '
TRAILING NULLCOLS
NOTE_EFF_DATE POSITION(1:7) INTEGER EXTERNAL NULLIF(NOTE_EFF_DATE=BLANKS),
NOTE_NDC_NUMBER POSITION(8:18) DECIMAL EXTERNAL NULLIF(NOTE_NDC_NUMBER=BLANKS),
NOTE_PREV_NDC_NUMBER POSITION(19:27) DECIMAL EXTERNAL NULLIF(NOTE_PREV_NDC_NUMBER=BLANKS),
NOTE_DEA_CLASS_CD POSITION(28) CHAR NULLIF (NOTE_DEA_CLASS_CD=BLANKS),
NOTE_PRODUCT_CTGRY_CD POSITION(29:30) CHAR NULLIF (NOTE_PRODUCT_CTGRY_CD=BLANKS),
NOTE_PRODUCT_NAME POSITION(31:65) CHAR NULLIF (NOTE_PRODUCT_NAME=BLANKS),
NOTE_FORM_CODE POSITION(66:68) CHAR NULLIF (NOTE_FORM_CODE=BLANKS),
NOTE_PRODUCT_STRENGTH POSITION(69:93) CHAR NULLIF (NOTE_PRODUCT_STRENGTH=BLANKS),
NOTE_PRODUCT_MSUR_CD POSITION(94:95) CHAR NULLIF (NOTE_PRODUCT_MSUR_CD=BLANKS),
NOTE_PRODUCT_PKG_SZ POSITION(96:100) INTEGER EXTERNAL NULLIF (NOTE_PRODUCT_PKG_SZ=BLANKS),
NOTE_PRODUCT_PKG_QTY_CD POSITION(101:103) CHAR NULLIF (NOTE_PRODUCT_PKG_QTY_CD=BLANKS),
NOTE_THRPTC_CLS_CD POSITION(104:113) INTEGER EXTERNAL NULLIF (NOTE_THRPTC_CLS_CD=BLANKS),
NOTE_AWP_CRT_PRC_EF_DT POSITION(114:118) INTEGER EXTERNAL NULLIF (NOTE_AWP_CRT_PRC_EF_DT=BLANKS),
NOTE_AWP_CRT_PRC POSITION(119:225) DECIMAL EXTERNAL NULLIF (NOTE_AWP_CRT_PRC=BLANKS),
NOTE_AWP_UNT_PRC POSITION(226:234) DECIMAL EXTERNAL NULLIF (NOTE_AWP_UNT_PRC=BLANKS),
NOTE_AWP_1ST_PRV_UNT_PRC POSITION(235:245) DECIMAL EXTERNAL NULLIF (NOTE_AWP_1ST_PRV_UNT_PRC=BLANKS)load data
APPEND into table TBL1
fields terminated by "," optionally enclosed by '"'
TRAILING NULLCOLS
columnname
)Hi!
Brother, pls give the details of your column. Your exact script. Initially, it seems that - your code is ok. But, that is my guess. Please post the complete script. We cannot say anithing - untill we go through the entire code of your script.
Regards.
Satyaki De. -
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 -
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 -
Getting error ORA-01401: inserted value too large for column
Hello ,
I have Configured the scenario IDOC to JDBC .In the SXMB_MONI am getting the succes message .But in the Adapter Monitor am getting the error message as
ORA-01401: inserted value too large for column and the entries also not inserted in to the table.I hope this is because of the date format only.In Oracle table date field has defined in the format of '01-JAN-2005'.I am also passing the date field in the same format only for INVOICE_DATE and INVOICE_DUE_DATE.Please see the target structure .
<?xml version="1.0" encoding="UTF-8" ?>
- <ns:INVOICE_INFO_MT xmlns:ns="http://sap.com/xi/InvoiceIDoc_Test">
- <Statement>
- <INVOICE_INFO action="INSERT">
- <access>
<INVOICE_ID>0090000303</INVOICE_ID>
<INVOICE_DATE>01-Dec-2005</INVOICE_DATE>
<INVOICE_DUE_DATE>01-Jan-2005</INVOICE_DUE_DATE>
<ORDER_ID>0000000000011852</ORDER_ID>
<ORDER_LINE_NUM>000010</ORDER_LINE_NUM>
<INVOICE_TYPE>LR</INVOICE_TYPE>
<INVOICE_ORGINAL_AMT>10000</INVOICE_ORGINAL_AMT>
<INVOICE_OUTSTANDING_AMT>1000</INVOICE_OUTSTANDING_AMT>
<INTERNAL_USE_FLG>X</INTERNAL_USE_FLG>
<BILLTO>0004000012</BILLTO>
<SHIPTO>40000006</SHIPTO>
<STATUS_ID>O</STATUS_ID>
</access>
</INVOICE_INFO>
</Statement>
</ns:INVOICE_INFO_MT>
Please let me know what are all the possible solution to fix the error and to insert the entries in the table.
Thanks in Advance!Hi muthu,
// inserted value too large for column
When your oracle insertion throws this error, it implies that some value that you are trying to insert into the table is larger than the allocated size.
Just check the format of your table and the respective size of each field on your oracle cleint by using the command,
DESCRIBE <tablename> .
and then verify it with the input. I dont think the problem is with the DATE format because if it is not a valid date format, you would have got on error like
String Literal does not match type
Hope this helps,
Regards,
Bhavesh -
Ora-01401 value too large for the column
I am running several sql statements in one transaction in oracle 8.1.7 for redhat linux 7.3. I got the error message ORA-01401 which is the values inserted is too large for the column at the last sql statement. But I copied and pasted the same sql statement through sqlplus, the row was inserted successfully. So, it looks like no value is excessed the length of the column. Is there anybody know what the problem is? Thanks.
HouminI forgot mentioning that I ran those sql statement in java code.
Houmin -
ORA-01401 on execution SQL*Plus Copy command
I looking solution for strange problem :
I having two database created with AL32UTF8 character-set ; current application design are that we loading data throw SQL Loader and than transferring loaded data from one database to another using SQL*Plus copy command.
Now , we having two tables , declared 100% identically , with respect to NLS and CHAR semantics (all varchar fields having CHAR inside length).
At attempt to transfer data , with SQL*Plus Copy command I'm receiving next output :
ERROR:
ORA-01401: inserted value too large for column
If I'm trying to transfer data via DB link , and this succeeds , or throw exp/imp utilities it also works .
Database servers are 9.2 (i tryied with 9.2.0.6 or 9.2.0.8) ; client side were 9.2.0.8 , 10.1.0.5 ...
On client side NLS_LANG variable are set to AMERICAN_AMERICA.AR8MSWIN1256 (we working on project who needs to support arabic language)
Did anyone encountered same problem ? Any One ?it could be that the column of the table that you are trying to insert the data has a small length.
-
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
.............mikelmHi,
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 -
Oracle error message code 1401 op 4, ORA-01401: inserted value too large fo
Hi All
I got this error when I try to run convert tables on our application server. Anyone know why? I am using Oracle 9i
Here is the error message:
Checking Table WORK_INSTRUCTION
Table not in database
Conversion Method - Create Table
Creating Table WORK_INSTRUCTION
Unable to create database table 'WORK_INSTRUCTION'
Oracle error message code 1401 op 4, ORA-01401: inserted value too large for column
WORK_INSTRUCTION definition as followings:
table work_instruction;
field identity
used_for unique_key
datatype identity;
{ APR 31/3/03 - Bug Nr WI4}
field wi_admin
{ links_to personnel . identity;}
{ links_to location . identity;}
links_to lab_section . identity;
{ ARP 31/3/03 - Bug Nr WI5 }
field wi_title
{ datatype text(20); }
datatype text(100);
field version
datatype text ( 4 );
field wi_status
datatype identity
prompt_type choose
choose_type WI_STATUS
default 'I ' ;
field wi_type
datatype identity
prompt_type choose
choose_type WI_TYPE
default '0 ';
field sterlab_status
datatype identity
prompt_type choose
choose_type STER_STAT
default '0 ';
field used_in_lims
datatype boolean
true_word 'Yes'
false_word 'No'
default 'No' ;
{ ARP WI16 28/5/03 - Extend from 10 to 45 }
field method
datatype text(45);
field ref_method
datatype text(100);
field delegate
links_to personnel . identity;
field date_expire
datatype date;
field date_draft
datatype date;
field double_method
datatype boolean
true_word 'Yes'
false_word 'No'
default 'No' ;
field technique
datatype identity
prompt_type choose
choose_type TECHNIQUE
default '0 ';
field date_distribute
datatype date;
field report_date
datatype date;
field group_autho
datatype text ( 16 );
field astm_volume
datatype text ( 6 );
field date_non_active
datatype date;
field translated_in
datatype text(10);
{ ARP WI16 28/5/03 - Extend from 60 to 2000 }
field comments
datatype text(2000);
field doc_path
datatype text ( 300 )
prompt_type user_defined
library 'TEST_SOP_FILE'
routine 'file_browse';
field modified_on
datatype date
used_for modified_on ;
field modified_by
links_to personnel.identity
used_for modified_by;
field modifiable
datatype boolean
used_for modifiable;
field removeflag datatype boolean
used_for remove_flag;
{ MOD TDR - 10/04/03 - Link to livelink document }
field livelink_url
datatype text ( 300 ) ;
Thanks
LiVerbatim from the manual:
ORA-01401: inserted value too large for column
Cause: The value entered is larger than the maximum width defined for the column.
Action: Enter a value smaller than the column width or use the MODIFY option with ALTER TABLE to expand the column width.You should find which value is bein attempted to be inserted into a column with a capacity shorter than the value length.
~ Madrid. -
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
UrosThank 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 -
Hi,
Is there an easy way to avoid ORA-01401 exceptions (inserted value too large for column)?
For instance, is there a OCI connection option to automatically truncate columns which are too long?
Should I use an INSERT statement which looks like:
INSERT INTO table (..., some_long_column) VALUES (..., SUBSTRB(?, 1, 4000))
Thanks,
ERHi,
user10936714 wrote:
Hi,
Is there an easy way to avoid ORA-01401 exceptions (inserted value too large for column)?
For instance, is there a OCI connection option to automatically truncate columns which are too long?A trigger, like Ttt suggested, is the only automatic thing I can think of.
Should I use an INSERT statement which looks like:
INSERT INTO table (..., some_long_column) VALUES (..., SUBSTRB(?, 1, 4000))That's probably what I would do.
It really depends on what the users want. The advantage of a trigger is that it works automatically and quietly, but that can sometimes be a disadvantage. Will users ever be upset because what went into the table was not what they said it should be? For example, the most important part of a long message could be the bottom line. It may actually be better to raise an error in such cases.
Maybe you are looking for
-
Issues with using leapord as a gateway.
I performed a clean install of mac osx server 10.5.1 on our new xserve. I then used the gateway setup assistant to set the xserve up as a router. Ethernet 1 has a static IP which is connected to our dsl line. Ethernet 2 is connected to a switch with
-
Auto font size for textfield by javascript
Hi there. I got the following script for a textfield in a fillabe PDF. Th length of the textfield is 150. It is required that if the text is > 100, the text size will be set to point 8, otherwise it will be point 12. var tf = this.rawValue; if (tf
-
Lightroom 5 Upgrade and Flickr--why have I lost my connection?
I have used, and liked considerably, Lightroom since LR2. I teamed Lightroom 3 to my Flickr account as an experiment and the pair worked so well together I'm lost in my workflow because I am unable to connect to Flickr from Lightroom since I upgraded
-
External Material for Subcontracting
How do you manage material from customer that you just add a process to it? Right now we do not enter the material in our stock and just make a service sales order type? Is there a best practice process for this scenario? Thank you, Carlos
-
IPod is not being recognized in any sort.
I recently updated to Windows XP Service Pack 2 and my iPod is not being recognized in iTunes and My Computer. Before the update, when I connected my iPod to the computer it would be recognized as a device plugged into the USB but not anymore. Right