Regarding ORA-01406
Hi,
While executing a query we are getting this error ,
ORA-01406: fetched column value was truncated
ORA-01406: fetched column value was truncated
We are getting this error for the first time. Please suggest us how to overcome it.
The database is 10.2.0.1 on HP-UX B11.23
Hi,
We were using this below query when we got the error.
SELECT
LTRIM(RTRIM(STG_PI_EXTRACT.PC_NUM)),
STG_PI_EXTRACT.PI_CREATED_DT,
LTRIM(RTRIM(STG_PI_EXTRACT.PI_ASSIGNED_TO)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_FILE_TYPE)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_MDR_DECISION)), LTRIM(RTRIM(STG_PI_EXTRACT.PI_MDR_DECISION_MAKER)), LTRIM(RTRIM(STG_PI_EXTRACT.PI_MDV_DECISION)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_MDV_DECISION_MAKER)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_PROCEDURE)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_EVENT_DESC)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_STATUS_CD)),
LTRIM(RTRIM(STG_PI_EXTRACT.SR_SALES_REP_LOGIN)),
LTRIM(RTRIM(STG_PI_EXTRACT.PRODUCT_PROD_CODE)),
LTRIM(RTRIM(STG_PI_EXTRACT.ACCOUNT_JJHCS_NUM)),
REPLACE(STG_PI_EXTRACT.ACCOUNT_SITE,' ',''),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_LITIGATION_FLG)),
LTRIM(RTRIM(STG_PI_EXTRACT.ASSET_SERIAL_NUM)),
STG_PI_EXTRACT.PI_CLOSED_DT,
LTRIM(RTRIM(STG_PI_EXTRACT.PI_REASON_FOR_CLOSE)), STG_PI_EXTRACT.PI_INITIAL_REVIEW_DT, LTRIM(RTRIM(STG_PI_EXTRACT.PI_INITIAL_REVIEWER)),
STG_PI_EXTRACT.PI_AGE,
LTRIM(RTRIM(STG_PI_EXTRACT.PRODUCT_ANALYSIS_SITE)), STG_PI_EXTRACT.PI_EXPIRATION_DATE, LTRIM(RTRIM(STG_PI_EXTRACT.PI_DISTRIBUTED_FLG)),
STG_PI_EXTRACT.PI_QTY_INVOLVED, STG_PI_EXTRACT.PI_QTY_TO_BE_RETURNED, STG_PI_EXTRACT.PI_QTY_REPLACED,
STG_PI_EXTRACT.PI_MFG_DT,
LTRIM(RTRIM(STG_PI_EXTRACT.PI_USEAGE_OF_DEVICE)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_LOANER_TYPE)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_WARRANTY_NAME)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_WARRANTY_DESC)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_WARRANTY_TYPE)),
STG_PI_EXTRACT.PI_WARRANTY_END_DT, LTRIM(RTRIM(STG_PI_EXTRACT.PI_SOFTWARE_VERSION)), LTRIM(RTRIM(STG_PI_EXTRACT.PI_HARDWARE_UPGRADE)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_FDA_REPORTABLE_FLG)), STG_PI_EXTRACT.PI_FDA_REPORT_DATE,
LTRIM(RTRIM(STG_PI_EXTRACT.PI_PROTOCOL_NUM)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_MODALITY)),
STG_PI_EXTRACT.PI_ALERT_DT,
STG_PI_EXTRACT.PI_RECEIVED_DT,
LTRIM(RTRIM(STG_PI_EXTRACT.PI_ROW_ID)),
STG_PI_EXTRACT.PI_LAST_UPD_DT,
LTRIM(RTRIM(STG_PI_EXTRACT.SR_PRIMARY_SR_NUM)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_EVENT_DAY)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_EVENT_OCCURED)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_CST_REF_NUM)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_DISP_SERIAL_NUM)),
LTRIM(RTRIM(STG_PI_EXTRACT.ASSET_ASSET_NUM)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_AVAILABLE_CD)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_TT_RESULTS)),
LTRIM(RTRIM(STG_PI_EXTRACT.CONTACT_SALES_REP)), LTRIM(RTRIM(STG_PI_EXTRACT.CONTACT_CUSTOMER_TYPE)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_MDR_OTHER)), LTRIM(RTRIM(STG_PI_EXTRACT.PI_SUBMITTED_TO_AFFILIATE)), LTRIM(RTRIM(STG_PI_EXTRACT.MFG_SITE_NAME)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_FOREIGN_FLG)), LTRIM(RTRIM(STG_PI_EXTRACT.PI_HEALTH_PROFESSIONAL_FLG)), LTRIM(RTRIM(STG_PI_EXTRACT.PI_USER_FACILITY_FLG)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_REPRESENTATIVE_FLG)), LTRIM(RTRIM(STG_PI_EXTRACT.PI_DISTRIBUTOR_FLG)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_A_NDA_NUM)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_IND_NUM)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_STN_NUM)),
LTRIM(RTRIM(STG_PI_EXTRACT.PRODUCT_501K_NUM)),
LTRIM(RTRIM(STG_PI_EXTRACT.PRODUCT_PRE_1938)),
LTRIM(RTRIM(STG_PI_EXTRACT.PRODUCT_OTC_PRODUCT)), LTRIM(RTRIM(STG_PI_EXTRACT.PI_COMBINATION_PRODUCT)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_AE_TERMS)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_PERIODIC_FLG)), STG_PI_EXTRACT.PI_INITIAL_REPORT_DATE, STG_PI_EXTRACT.PI_FOLLOW_UP_DATE, STG_PI_EXTRACT.PI_FINAL_REPORT_DATE,
LTRIM(RTRIM(STG_PI_EXTRACT.PI_LOCK_ACCOUNT_NAME)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_CLOSED_BY)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_REPORTED_BY)),
NVL(LTRIM(RTRIM(STG_PI_EXTRACT.ACCOUNT_ADDRESS_COUNTRY)),LTRIM(RTRIM(STG_PI_EXTRACT.ACCOUNT_ADDRESS_CITY))),
PI_RR_TYPE_CD
FROM
STG_PI_EXTRACT
--where UPPER(LTRIM(RTRIM(STG_PI_EXTRACT.PI_REASON_FOR_CLOSE))) <> 'VOID'
Database driver error...
Function Name : Fetch
SQL Stmt : SELECT
LTRIM(RTRIM(STG_PI_EXTRACT.PC_NUM)),
STG_PI_EXTRACT.PI_CREATED_DT,
LTRIM(RTRIM(STG_PI_EXTRACT.PI_ASSIGNED_TO)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_FILE_TYPE)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_MDR_DECISION)), LTRIM(RTRIM(STG_PI_EXTRACT.PI_MDR_DECISION_MAKER)), LTRIM(RTRIM(STG_PI_EXTRACT.PI_MDV_DECISION)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_MDV_DECISION_MAKER)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_PROCEDURE)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_EVENT_DESC)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_STATUS_CD)),
LTRIM(RTRIM(STG_PI_EXTRACT.SR_SALES_REP_LOGIN)),
LTRIM(RTRIM(STG_PI_EXTRACT.PRODUCT_PROD_CODE)),
LTRIM(RTRIM(STG_PI_EXTRACT.ACCOUNT_JJHCS_NUM)),
REPLACE(STG_PI_EXTRACT.ACCOUNT_SITE,' ',''),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_LITIGATION_FLG)),
LTRIM(RTRIM(STG_PI_EXTRACT.ASSET_SERIAL_NUM)),
STG_PI_EXTRACT.PI_CLOSED_DT,
LTRIM(RTRIM(STG_PI_EXTRACT.PI_REASON_FOR_CLOSE)), STG_PI_EXTRACT.PI_INITIAL_REVIEW_DT, LTRIM(RTRIM(STG_PI_EXTRACT.PI_INITIAL_REVIEWER)),
STG_PI_EXTRACT.PI_AGE,
LTRIM(RTRIM(STG_PI_EXTRACT.PRODUCT_ANALYSIS_SITE)), STG_PI_EXTRACT.PI_EXPIRATION_DATE, LTRIM(RTRIM(STG_PI_EXTRACT.PI_DISTRIBUTED_FLG)),
STG_PI_EXTRACT.PI_QTY_INVOLVED, STG_PI_EXTRACT.PI_QTY_TO_BE_RETURNED, STG_PI_EXTRACT.PI_QTY_REPLACED,
STG_PI_EXTRACT.PI_MFG_DT,
LTRIM(RTRIM(STG_PI_EXTRACT.PI_USEAGE_OF_DEVICE)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_LOANER_TYPE)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_WARRANTY_NAME)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_WARRANTY_DESC)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_WARRANTY_TYPE)),
STG_PI_EXTRACT.PI_WARRANTY_END_DT, LTRIM(RTRIM(STG_PI_EXTRACT.PI_SOFTWARE_VERSION)), LTRIM(RTRIM(STG_PI_EXTRACT.PI_HARDWARE_UPGRADE)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_FDA_REPORTABLE_FLG)), STG_PI_EXTRACT.PI_FDA_REPORT_DATE,
LTRIM(RTRIM(STG_PI_EXTRACT.PI_PROTOCOL_NUM)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_MODALITY)),
STG_PI_EXTRACT.PI_ALERT_DT,
STG_PI_EXTRACT.PI_RECEIVED_DT,
LTRIM(RTRIM(STG_PI_EXTRACT.PI_ROW_ID)),
STG_PI_EXTRACT.PI_LAST_UPD_DT,
LTRIM(RTRIM(STG_PI_EXTRACT.SR_PRIMARY_SR_NUM)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_EVENT_DAY)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_EVENT_OCCURED)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_CST_REF_NUM)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_DISP_SERIAL_NUM)),
LTRIM(RTRIM(STG_PI_EXTRACT.ASSET_ASSET_NUM)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_AVAILABLE_CD)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_TT_RESULTS)),
LTRIM(RTRIM(STG_PI_EXTRACT.CONTACT_SALES_REP)), LTRIM(RTRIM(STG_PI_EXTRACT.CONTACT_CUSTOMER_TYPE)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_MDR_OTHER)), LTRIM(RTRIM(STG_PI_EXTRACT.PI_SUBMITTED_TO_AFFILIATE)), LTRIM(RTRIM(STG_PI_EXTRACT.MFG_SITE_NAME)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_FOREIGN_FLG)), LTRIM(RTRIM(STG_PI_EXTRACT.PI_HEALTH_PROFESSIONAL_FLG)), LTRIM(RTRIM(STG_PI_EXTRACT.PI_USER_FACILITY_FLG)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_REPRESENTATIVE_FLG)), LTRIM(RTRIM(STG_PI_EXTRACT.PI_DISTRIBUTOR_FLG)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_A_NDA_NUM)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_IND_NUM)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_STN_NUM)),
LTRIM(RTRIM(STG_PI_EXTRACT.PRODUCT_501K_NUM)),
LTRIM(RTRIM(STG_PI_EXTRACT.PRODUCT_PRE_1938)),
LTRIM(RTRIM(STG_PI_EXTRACT.PRODUCT_OTC_PRODUCT)), LTRIM(RTRIM(STG_PI_EXTRACT.PI_COMBINATION_PRODUCT)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_AE_TERMS)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_PERIODIC_FLG)), STG_PI_EXTRACT.PI_INITIAL_REPORT_DATE, STG_PI_EXTRACT.PI_FOLLOW_UP_DATE, STG_PI_EXTRACT.PI_FINAL_REPORT_DATE,
LTRIM(RTRIM(STG_PI_EXTRACT.PI_LOCK_ACCOUNT_NAME)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_CLOSED_BY)),
LTRIM(RTRIM(STG_PI_EXTRACT.PI_REPORTED_BY)),
NVL(LTRIM(RTRIM(STG_PI_EXTRACT.ACCOUNT_ADDRESS_COUNTRY)),LTRIM(RTRIM(STG_PI_EXTRACT.ACCOUNT_ADDRESS_CITY))),
PI_RR_TYPE_CD
FROM
STG_PI_EXTRACT
--where UPPER(LTRIM(RTRIM(STG_PI_EXTRACT.PI_REASON_FOR_CLOSE))) <> 'VOID']
Similar Messages
-
Help Needed: Facing the error ORA-01406: fetched column value was truncated
Hi Everyone,
When I run a particular PL/SQL query using Oracle 9i ODBC driver, it is working fine and fetching me the desired results.
However, when I run the same query using the Oracle 10g ODBC driver, I am getting the error: ORA-01406: fetched column value was truncated.
I have checked all the fields of the table and they are well within the allowable limit.
Can you please let us know what needs to be done to resolve this issue?
Thanks and Regards,
SudhindraWell it's obviously a problem with the client software. Doesn't Datastage have some way of configuring these things?
rgds, APC -
ORA-01406 error encountered when using database link
I am moving data between two different databases using a database link on Oracle 8.1.5. The database statement looks like:
insert into TABLE@DATABASELINK
(COLUMNS)
select (COLUMNS) from TABLE
One of the database columns is defined as varchar2(4000) on both the source and target database tables. When the data in this column on the source database is greater than 2000 characters, the database query generates the message:
ORA-01406: fetched column value was truncated
I have verified that the target column is defined as varchar2(4000), and have also verified that it is this varchar2(4000) column that is causing the problem. I have also tested out that this error only occurs when the varchar field is more than 2000 characters; if I remove characters so that the source field is less than or equal to 2000 characters, this error is no longer generated and the data is inserted to the target database table.
Is this a limit with database links or some other database parameter that is not set up correctly?
Thanks...Theresa TucciCould you change the following entry in your 'sqlnet.ora' file and try?
SQLNET.AUTHENTICATION_SERVICES = (NONE) -
Hi all,
11.2.0.3
I am dropping a user with QUEUE objects but I got error
SQL> /
drop user Q_ADMIN
ERROR at line 1:
ORA-00604: error occurred at recursive SQL level 1
ORA-01406: fetched column value was truncated
Please help...
Thanks,
pKNo help is required.
Your posting history shows you have a general inability to Google anything before asking a question and basically you expect this forum to that for you.
I just Googled for 'drop user with queue objects' and got some responses that looked valid, I also noticed this topic has discussed earlier in this forum.
Every single question you have asked here is abuse of this forum!
I would love to see moderators taking appropriate action and remove your account.
Yes, I am quite aware you will create a new account, and you will continue to abuse this forum.
However, people like you have to be stopped somewhere.
I will also address, again, your posting history in the community feedback forum.
Sybrand Bakker
Senior Oracle DBA -
Lobs are often troublesome .
I have to fetch the concatenated result of few long varchar columns(all of them are of over 3888 bytes) over a dblink from my staging schema . I have made a procedure to do this .
Similar to
create or replace function lob (par1 varchar2)return clob
as
l_clob clob;
l_clob2 clob;
l_clob3 clob;
BEGIN
select source_col1,source_col2,source_col3 into l_clob,l_clob2,l_clob3 from source_table_over_db_link where col1=par1;
return (lcob||l_cob2||l_clob3);
END;
when i simply call this function ,it works fine .i.e.
select lob('ABCC') from dual; Returns me result
But when i use this function inside another select statement as below
SELECT TO_CLOB(local_table.col1),to_clob(local_table.col2)||lob('ABCC') from local_table ;
I get the below ora error.
I get ORA-01406 .i.e. the fetched column value was truncated .
I am cluless ? The version is 11.2.0.3.0 Production 64 bit Tns for linus versio 11.2.0.3.0OracleManiac,
This error is environment specific too and it also comes when we are using DB links. Which tool are you using?
If possible try it out from SQL*PLUS as well. If you are on TOAD, use this VIEW:OPTIONS:ORACLE:OCI buffer array size
You need to increase Buffer Array Size to fit your value.
Ishan -
Weird ORA-01406: fetched column value was truncated error for SELECT query
DB version:10gR2
When one of our application fires the below query, we get
ORA-01406: fetched column value was truncatederror.
select trk_dtl,
trk_type,
trk_id,
trk_desc,
from shp_dtl
where shp_type = 'HN'
and shp_type = 828;The documentation says
Cause:In a host language program, a FETCH operation was forced to truncate a character string. The program buffer area for this column was not large enough to contain the entire string. The cursor return code from the fetch was +3.But when the application is pointed to an identical schema in the same instance, we don't get this error. So, this has got nothing to do client application as the documentation says.
Any idea what other possibilities are there?Post description of shp_dtl.
-
How to resolve ORA-01406: fetched column value was truncated
I tried to export with the parameter full=yes....when i did tat i ma gettin ORA-01406: fetched column value was truncated error...
the following gives the sequence
About to export the entire database ...
. exporting tablespace definitions
. exporting profiles
. exporting user definitions
. exporting roles
EXP-00008: ORACLE error 1406 encountered
ORA-01406: fetched column value was truncated
EXP-00000: Export terminated unsuccessfully
pls revert back with an answer....http://www.orafaq.com/forum/t/145219/2/
-
Regarding ORA 02063 : preceding line from dblink
Hi Team,
I am facing one issue, while using the DBlink for fetching data from different Database in PLSql.
**********Query***********
select a.A, b.B
from ABC a,
ABC@ XYZ b
Please suggest and help me in this regards.
Best Regards
Manpreet Singh810148 wrote:
Hi Team,
I am facing one issue, while using the DBlink for fetching data from different Database in PLSql.
**********Query***********
select a.A, b.B
from ABC a,
ABC@ XYZ b
Please suggest and help me in this regards.
Best Regards
Manpreet Singh
bcm@bcm-laptop:~$ oerr ora 2063
02063, 00000, "preceding %s%s from %s%s"
// *Cause: an Oracle error was received from a remote database link.
// *Action: refer to the preceding error message(s)You have a mystery & we have no clues.
How do I ask a question on the forums?
SQL and PL/SQL FAQ -
Regarding ORA-12801,ORA-01843 error
Hi all,
When I am running the mapping I am getting the
ORA-12801: error signaled in parallel query server P079
ORA-01843: not a valid month error
My mapping was validated and deployed suceesfully.
Please give me the suggestions.
Thanks,
VenkatIs the source field a date field or a varchar? Sounds like you are hitting a source data error.
Try grabbing the insert (or merge, or whatever) statement from the mapping and running it on its own. If that fails with the same error, then try running the select portion of the statement to debug for the error.
Assuming that you are using a to_Date function and if you are having real trouble finding the data error, you at least know which table the field is being sourced from. Run a little test - something like:
declare
cursor curs is select the_source_field from the_source_table;
begin
for rec in curs loop
declare
dateval date
begin
dateval := to_Date(rec.the_source_field,'yyyymmdd'); --or whatever format mask it is you are using
exception
when others then
dbms_output.put_line('FAILED TO_DATE ON SOURCEVAL: '||rec.the_source_field||' with error: '||substr(sqlerrm,1,150));
end;
end loop;
end;Once you know the problems with the data then you can consider how best to deal with them.
Cheers,
Mike -
Regarding ORA-01102 ORACLE COULD NOT MOUNT DATABASE IN EXCLUSIVE MODE.
Hellow Friends,
I was testing my recovery strategy for control file. Out of two my control files I deleted one and tried to start when oracle gave me error that could not find so and so file in such and such location. I than copied first member which is in other location to the deleted file location. Since than I could not start my database gving me same error ORA-01102.
Yes I can recreate control file because I am having all my other files intact.
Now is there anybody who share knowledge with me to feel me pride of such honour.
Thanks All.
Your Friend.
Sumeet.Hi all
On this - it had me vexed for a while, I was installing
8.1.7 on Solaris 2.9 - but when I went to prep the db,
kept on getting the error 01102.
Found out that if I shut down the db (immediate),
changed the 'remote_password' param to shared then went back in to svrmgr - reshut the database and redid startup pfile=$ORACLE_HOME/etc it cured the problem.
Suspect this is a hangover from 7, when Oracle kept enforcing defaults on setting up dbs, bit like their catalog and catproc scripts, they still have errors that were there in the
year dot.
Cheers -
Regard ora-01207: How Oracle judge file is more recent than control file - old control file
ORA-00283: recovery session canceled due to errors
ORA-01122: database file 2 failed verification check
ORA-01110: data file 2: '/tmp/auxsys.dbf_rman'
ORA-01207: file is more recent than control file - old control file
How Oracle judge file is more recent than control file - old control file, then it thrown out error ora-01207.
It must compare data file with control file, but what compare?Begin from the beginning.
Did you do a RESTORE DATABASE ?
Or did you selectively restore datafiles ?
Strange datafile name --- looks like it could have been a DATAFILECOPY done using rman.
It is a very bad idea to have a datafile in /tmp On some OSs, /tmp may get cleared of files on a reboot.
Hemant K Chitale -
Regarding ORA-00001: unique constraint violation error
Hi ,
This is Venkat. I am new to OWB.
When I run the mapping I am getting the ORA-00001: unique constraint violation error.
My loading type is Update/Insert.
My target table Primarykey is combination of 3 keys.
Please give me the suggestions. It is very urgent.
Thanks,
Venkat1) If you can disable/drop the indexes on the table, you can load the data and then do a SQL query grouping by the PK/UI to show which rows have a count > 1 i.e. the duplicates.
2) If you can't alter the target table, perhaps create a dummy copy of the table without pk/indexes and load to that and then do above query.
3) Run the mapping via the debugger and set a breakpoint just before your target table and examine the data to see if you can spot the duplicates.
4) Put a deduplicator into the mapping (just before target table), this may allow you to load data but doesn't solve the real problem as to why you have duplicates.
Si -
Doubt regarding ORA-30036: unable to extend segment by 8 in undo tablespace
I am using 11g Release 1 Database .
I have to analyze the performance of two tables of different designs which serve the same purpose and come up with the design which is efficient .
SQL> desc staging_dict
Name Null? Type
SNO NUMBER
CODE_FRAGMENTS CLOB
CODE_FRAGMENTS_U CLOB
CODE_FRAGMENTS_D CLOB
CODE_FRAGMENTS_DO CLOB
SQL> desc staging_dict1
Name Null? Type
SNO NUMBER
CODE_FRAGMENTS CLOB
CODE_FRAGMENTS_UD CLOB
CODE_TYPE VARCHAR2(5 CHAR)Initially I tried inserting a few thousand records into both the tables . Then I did some conversion on one column and I populate the result on other column of the same table . So I update the table in bulk mode and I commit for every thousand records .
I have a undo tablespace of 2G with undo_retention=900 , retention guratantee is not set for the undo tablespace .
When I tried the conversion and update on the first table (STAGING_DICT) it took more time for around 2500 records compared to other table and when I increased the number of records to 10000 it threw an error
ORA-30036: unable to extend segment by 8 in undo tablespace 'UNDOTBS'
But I didn't come across this error when I tried the conversion and update on the table for the same 2500 records (STAGING_DICT1) and it was also 10 times faster .
My doubt is does the error ORA-30036 occur because it is saving the undo image of all the four clob columns though I am doing conversion on one column and updating the other column (using only two columns in the update and only one column is affected by update command) ?
Also how is that having less CLOB rows prove more effective by adding one more VARCHAR column which differentiates the code_frament type in the STAGING_DICT1 table than having it as more CLOB columns as in STAGING_DICT table ?Don't you think the error OP reported is kind of weird?
Because as you said, Oracle stores "undo" of lob in user tablespace not undo tablespace if the lob is stored out-of-line.
1. If the size of lob was small, small size of undo would be stored into undo tablespace,
and OP would'nt have undo tablespace shortage problem.
(How does small lob flood undo tablespace?)
2. If the size of lob was big, OP would have 01555 error on user tablespace not undo tablespace shortage error.
So, i think there are 2 theories that can explain this abnormality.
1. OP hit the bug of massive undo generation.
2. OP is using securefile which is 11g new feature.
Oracle documents says that undo for securefile lob is stored in "undo" tablespace, not user tablespace.
But unfortunately, i'm not sture about this coz i didn't try it myself -
I am trying to install Oracle 11i Release 1 database(dbname : ADTASK) in my Unix machine .
After creating ORACLE_HOME i was trying with installing the database using DBCA . The unix machine already contains a few databases installed in them .
When I started with database creation it gave me the following error
ORA-00119 Invalid Specification for system parameter LOCAL_LISTENER
ORA-00132 : syntax error or unresolved network name 'LISTENER_ADTASK'
ORA-01078 : failure in processing system parameters
The listener.ora file is present at ORACLE_HOME/network/admin
but when i use lsnrctl to start the listener it checks the following directory for the listener.ora file
TNSLSNR for Linux: Version 11.1.0.3.0 - Beta
System parameter file is /etc/listener.ora
What should be done to resolve the same ?
How can i make it look for listener.ora file in the ORACLE_HOME/network/admin directory ?I modified a few entries and then I tried starting the listener
but got this error
TNS-01150: The address of the specified listener name is incorrect
NL-00303: syntax error in NV string
I even tried with tnsping but i got the erro
Used parameter files:
TNS-03505: Failed to resolve name
Listener.ora file
SID_LIST_LISTENER=
(SID_LIST=
(SID_DESC=
(SID_NAME=adorcl)
(ORACLE_HOME=/SLOTS/slot04/appmgr/pramohan/Ora11g_Home))
(SID_DESC=
(SID_NAME=PLSExtProc)
(ORACLE_HOME=/SLOTS/slot04/appmgr/pramohan/Ora11g_Home)
(PROGRAM=extproc)))
LISTENER_ADORCL=
(DESCRIPTION=
(ADDRESS_LIST=
(ADDRESS=(PROTOCOL=TCP)(HOST=ap6305rt.us.oracle.com)(PORT=1522))
(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC))))Let me know what is the error -
Hi ,
In my package i used the following statement for FTPing files.
l_list(l_list.last) := UTL_TCP.get_line(l_conn, TRUE);
But it is giving the following error
"ORA-29259: end-of-input reached"
can anyone explain the meaning of this error?how can i solve this problem?
cheers
RRkJust guessing (since you are too lazy to check the docs, I'm too):
Nothing more to get?
Maybe you are looking for
-
How Do We Find the Latest Version of a Document without its Path?
Does anyone know how to find the latest version of a document in iFS when you don't know the path of the document? I'm using a Selector to search iFS based on a search string for the object's title and am not sure how to find the latest version of th
-
When I send a text, it goes through as a "text message" instead of an "imessage" and the person I am texting has an iPhone. what could be the cause of this problem?
-
Facebook Comments widget will show on Safari only and not on FireFox, Chrome or IE
I even tried on different computers on Win and OS and still no luck. Any idea what am I doing wrong?
-
Will DLSw and 802.1q ever be supported together or are there some technical issues that will always force you to use isl trunking with dlsw instead of 802.1q? problem is that there are switches that don't support isl.
-
I cant get into my iphone it locked me out
help me i cant get into my iphone i enterd the password in to meny times.....