ORA-22816 with INSERT, UPDATE URGENT!!!!!
=8-)
HI.
I have a big problem.
With a forms, 6.0.4.10, i am connetting with 8.0.5,
during UPDATE or INSERT, in this table ther are 18000 rows,
i recive ORA-22816.
The parameter DML Returning Value , is setting NO.
Now, next week i'll install this system, and i have a
big problem ....
PLEASE HELP ME !!!!!!!!!!!
Luca
null
Luca (guest) wrote:
: =8-)
: HI.
: I have a big problem.
: With a forms, 6.0.4.10, i am connetting with 8.0.5,
: during UPDATE or INSERT, in this table ther are 18000 rows,
: i recive ORA-22816.
: The parameter DML Returning Value , is setting NO.
: Now, next week i'll install this system, and i have a
: big problem ....
: PLEASE HELP ME !!!!!!!!!!!
: Luca
I have resolve the problem.
In my table is here a LONG ROW.
But, why the form using returnin in a table with LONG.
null
Similar Messages
-
Hi everyone,
I am getting an ORA-00933 error while executing this code :
UPDATE type_composant
set nom='RE',
libelle='Réglementaire',
process_export='YIYZD',
lien='0',
lien_technique='0',
lien_reglementaire='1',
lien_squelette='0',
lien_demande='0',
lien_pj='0',
id_type_comp_rattach=null,
id_type_comp_grp=null,
imp_comp=0,
imp_lien=0,
is_spec=1,
imp_sque=0,
spec_table='reglementaire',
spec_req='SELECT A.CDREGL AS CDREGL,
A.CDSTCO AS REPERTOIRE,
C.LILONG AS LIB_REP,
A.CDCODE AS CODE,
B.LIBLON AS LIB_CODE
FROM HR.ZD00 A,
HR.ZD01 B,
HR.DI31 C
WHERE A.NUDOSS = B.NUDOSS
AND A.CDSTCO = C.VACDST
AND C.CDLANG = 'F'
AND B.CDLANG = 'F'
AND CDSTCO IN ('DS9','UPA','WS0','UGQ','UHU','DSJ','WF0','DRX','G01','DS3',
'GCP','UAA','G02','G00','DRH','DRB','WAA','DRE','WR2','DRC','DRJ','GPR','DRM',
'WA0','GCO','UIG','UIQ','DRF','WG2','XXX','UCB')',
comp_web='0'
where id_type_comp='36';And here is the error I got :
AND C.CDLANG = 'F'
ERROR at line 28:
ORA-00933: SQL command not properly endedI don't know if it comes from the SELECT, and I think the syntax is good.
Any help would be nice !
Guich
Edited by: Guich on May 11, 2011 11:04 AM
Edited by: Guich on May 11, 2011 11:04 AMAnd with tabs, it would be much readable :
UPDATE type_composant
set nom='RE',
libelle='Réglementaire',
process_export='YIYZD',
lien='0',
lien_technique='0',
lien_reglementaire='1',
lien_squelette='0',
lien_demande='0',
lien_pj='0',
id_type_comp_rattach=null,
id_type_comp_grp=null,
imp_comp=0,
imp_lien=0,
is_spec=1,
imp_sque=0,
spec_table='reglementaire',
spec_req='SELECT A.CDREGL AS CDREGL,
A.CDSTCO AS REPERTOIRE,
C.LILONG AS LIB_REP,
A.CDCODE AS CODE,
B.LIBLON AS LIB_CODE
FROM HR.ZD00 A,
HR.ZD01 B,
HR.DI31 C
WHERE A.NUDOSS = B.NUDOSS
AND A.CDSTCO = C.VACDST
AND C.CDLANG = 'F'
AND B.CDLANG = 'F'
AND CDSTCO IN ('DS9','UPA','WS0','UGQ','UHU','DSJ','WF0','DRX','G01','DS3',
'GCP','UAA','G02','G00','DRH','DRB','WAA','DRE','WR2','DRC','DRJ','GPR','DRM',
'WA0','GCO','UIG','UIQ','DRF','WG2','XXX','UCB')',
comp_web='0'
where id_type_comp='36';According to this, you are using quotes (') in quotes, you need to use two to make it work :
UPDATE type_composant
set nom='RE',
libelle='Réglementaire',
process_export='YIYZD',
lien='0',
lien_technique='0',
lien_reglementaire='1',
lien_squelette='0',
lien_demande='0',
lien_pj='0',
id_type_comp_rattach=null,
id_type_comp_grp=null,
imp_comp=0,
imp_lien=0,
is_spec=1,
imp_sque=0,
spec_table='reglementaire',
spec_req='SELECT A.CDREGL AS CDREGL,
A.CDSTCO AS REPERTOIRE,
C.LILONG AS LIB_REP,
A.CDCODE AS CODE,
B.LIBLON AS LIB_CODE
FROM HR.ZD00 A,
HR.ZD01 B,
HR.DI31 C
WHERE A.NUDOSS = B.NUDOSS
AND A.CDSTCO = C.VACDST
AND C.CDLANG = ''F''
AND B.CDLANG = ''F''
AND CDSTCO IN (''DS9'',''UPA'',''WS0'',''UGQ'',''UHU'',''DSJ'',''WF0'',''DRX'',''G01'',''DS3'',
''GCP'',''UAA'',''G02'',''G00'',''DRH'',''DRB'',''WAA'',''DRE'',''WR2'',''DRC'',''DRJ'',''GPR'',''DRM'',
''WA0'',''GCO'',''UIG'',''UIQ'',''DRF'',''WG2'',''XXX'',''UCB'')',
comp_web='0'
where id_type_comp='36';Nicolas. -
How can perform insert /update /delete in one single mapping.
Hi,
I want to is there any logic by which we can create 2-3 pipeline in a mappings like pipelines will work for insert / update /delete or storing soem rejected data according to conditional flag.
I tried it in a mapping but problem is that when target load order is like ins then upd then delete/reject . if new rec will come then control will pass through ins target . but if rec needs to update or delete then again control is going to ins target not update / delete target.
We have already given the all conditional flags in filter after lookup and before target .
all possibilities we checked but didnt got success.
last option is separate the mappings for insert / update/delete.....etc.
Is there any solution for this type of problem.
reply plz if any body have solutions.
---UmeshHi Umesh,
I understand from your query that you want to load target with insert, update and delete rows after runnng the mappping...
If you are looking for the same then you can use one of the Oracle fetures Oracle Streams: Change Data Capture.
the Url is:
http://www.oracle.com/technology/products/bi/db/10g/pdf/twp_cdc_cookbook_0206.pdf
If any other help required do reply.
Regards
Tarang Jain -
How to insert/update Date field in Oracle with java code
Dear All
I have to insert/update a date column while creating a new item, but the problem is i am able to insert/update only date but i need both date and time along with AM/PM.
By using these 3 lines i am able to insert/update only date.
java.util.Date date = new java.util.Date();
long dateLong = date.getTime();
stmtPrep.setDate(33, new java.sql.Date(dateLong));
Below code retrives the date exactly what i need but unable to pass in the statement:
DateFormat formatter = new SimpleDateFormat("dd-MM-yyyy HH:mm:ss a");
java.util.Date d = (Date) new java.util.Date();
String stringdate = formatter.format(d);
String tmpdate = dateFormat();
stmtPrep.setString(33, tmpdate); -- I tried with setObject as well but same error coming.
Error is:
ORA-01830: date format picture ends before converting entire input string
Can u guide me how to get full date time with AM/PM?sasikrishna wrote:
Dear All
I have to insert/update a date column while creating a new item, but the problem is i am able to insert/update only date but i need both date and time along with AM/PM.
By using these 3 lines i am able to insert/update only date.
java.util.Date date = new java.util.Date();
long dateLong = date.getTime();
stmtPrep.setDate(33, new java.sql.Date(dateLong));That's by design. A java.sql.Date object matches an SQL DATE column (which doesn't include a time component). If you want something which matches an SQL TIMESTAMP colum (which includes both date and time components) then you should use a java.sql.Timestamp object. -
OAF Update of Custom Table causing ORA-600 with database block corruption?
Using OA Framework 12.1.3, running under EBusiness Suite 12.1.3
Created Custom Web page operating against Custom Tables
ISSUE
On about 2% of new records, when OAF is UPDATING a record in a certain table, it is failing with
java.sql.SQLException: ORA-00607: Internal error occurred while making a change to a data block
ORA-00600: internal error code, arguments: [kddummy_blkchk], [815], [26412], [6110], [], [], [], []
ORA-06512: at line 1
Before the DBA turned on 10.2.0.4.0 DB_BLOCK_CHECKING parameter, this actually
resulted in corrupted data blocks in the database and corrupted indexes that
eventually crashed the database and we had to do a full recovery with 2 days downtime.
Now that we have turned on DB_BLOCK_CHECKING, it simply errors out and puts things
in the alert log, but the records still fail to update as the writes are blocked.
Then oddly, a few days later.. the records become editable. And others fail.
This is ONLY happening on the one particular table being updated by OAF. Other custom pages
posting to other custom tables are having no problems. We've CTAS'd the table back and
forth and recreated the indexes, and that did not help.
Support says to post to the Forum ( So I am! ) or hire Oracle consulting.. which doesn't make
much sense given the error. The Recovery Team that helped us in a separate SR ( we had
to do db_repairs not just recovery ) felt it was an important problem the OAF team needed to
strongly review.
Anyone else encounter this already and know of a solution?
TIA
KarlAfter MANY hours of trial and error and research, we've identified ONE use case that seems to apply to 90% of the issue we have encountered.
YMMV.
The BC4J generated SQL which is generating the ORA-600 is
BEGIN UPDATE XXRETURNHEADER ReturnHeaderEO SET INTERNAL_TEXT=?,LAST_MOD_USERNAME=?,OBJECT_VERSION_NUMBER=?,LAST_UPDATE_DATE=?,LAST_UPDATED_BY=?,LAST_UPDATE_LOGIN=? WHERE RMA_NUMBER=? AND ORGANIZATION_ID=? RETURNING TROUBLESHOOT_DATE, FAA_TAG_DATE, FAILURE_ANALYSIS_DATE, LAST_MOD_DATE, FAA_REVISED_DATE, TTE_TECH_SEND_DATE, TTE_REP_RESPONSE_DATE, TTE_REP_APPROVED, TTE_RMA_RANDOM_KEY, OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN INTO ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?; END;".
We determined that if TTE_RMA_RANDOM_KEY was not a null value, we would get an ORA-600 error whenever we did an APPLY from the OAF Page to update the record.
If we set that table attribute to NULL for the record using SQL.. then used the OAF Page to APPLY.. it worked fine and the record saved without error.
We then modified the EO to NOT "Refresh After Update" ( thus removing it from the RETURNING clause generated )... and even if the TTE_RMA_RANDOM_KEY
had a value... the OAF Page APPLY worked and the record saved without error.
I cannot identify anything from the User programming side that is wrong ( and neither could Oracle ), and it REALLY should be in the RETURNING clause list of
attributes.. but this is the only workaround I've found that doesn't crash the Page and irritate the user to no end.
I have reported my findings via the SR back to Oracle to do with it what they may... but it looks strongly ,to me, to be an error in the BC4J/JDBC/Database
coordination and passing data between those black boxes. -
ORA-22816: unsupported feature with RETURNING clause
My database is: 10g 10.2.0.3.0
Sorry this is a little long but I need some help!
The insert is being done in PLSQL with SQL.
I am trying to Insert a row into a view the view has 3 Instead of triggers. (insert, update, delete)
I have looked up this error and have seen that you cannot use a RETURNING clause on view with INSTEAD OF triggers
because it is not supported?
My issue is, I cannot find any code around this view where a RETURNING clause is being used.
Does anyone have any idea what else this could be??
1. The trigger populates old and new values based on wether it is an insert update or delete,
and then calls a procedure to do the insert, update or delete.
2. Then calls another procedure that builds an XML string to pass into oracle queueing.
They are all new triggers and procedures I have written.
I searched for "RETURNING" in all other dependent objects for this view and could not find anything.
Thats why I was wondering if it could be anything else?
Another FYI. This whole procedure is actually on some other tables as well. It works fine with no issue on the tables.
It wasn't until I started testing the VIEW that I started getting this error.
I commented out the procedure calls and I still have an issue. I disabled the trigger and the issue went away.
Another FYI to make it more interesting, The instead of update and the instead of delete triggers on this view
work just fine with the package calls and everything. They are written exactly as the instead of insert trigger.
It is only the instead of insert trigger that it is getting this error.
Can someone help??? See Instead of Insert trigger below.
{CREATE OR REPLACE TRIGGER TRIIBTF97A
INSTEAD OF INSERT ON RTI_BUS_TA_FORM97A_VW
FOR EACH ROW
DECLARE
old_rec RTI_BUS_TA_FORM97A_VW%ROWTYPE;
new_rec RTI_BUS_TA_FORM97A_VW%ROWTYPE;
v_change_type VARCHAR2(8);
v_event_source VARCHAR2(20) := 'TRIIBTF97A';
BEGIN
-- only new values on inserts
new_rec.DOC_LOC_NBR := :new.DOC_LOC_NBR ;
new_rec.TRAN_ID := :new.TRAN_ID ;
new_rec.RPTD_ADJ_SUBTOT_AMT := :new.RPTD_ADJ_SUBTOT_AMT ;
new_rec.CALC_ADJ_SUBTOT_AMT := :new.CALC_ADJ_SUBTOT_AMT ;
new_rec.RPTD_ADJ_SUBTOT2_AMT := :new.RPTD_ADJ_SUBTOT2_AMT ;
new_rec.CALC_ADJ_SUBTOT2_AMT := :new.CALC_ADJ_SUBTOT2_AMT ;
new_rec.RPTD_AGI_PRENOL_AMT := :new.RPTD_AGI_PRENOL_AMT ;
new_rec.CALC_AGI_PRENOL_AMT := :new.CALC_AGI_PRENOL_AMT ;
new_rec.RPTD_BAL_DUE_AMT := :new.RPTD_BAL_DUE_AMT ;
new_rec.CALC_BAL_DUE_AMT := :new.CALC_BAL_DUE_AMT ;
new_rec.RPTD_CC_CRED_AMT := :new.RPTD_CC_CRED_AMT ;
new_rec.CALC_CC_CRED_AMT := :new.CALC_CC_CRED_AMT ;
new_rec.RPTD_CHAR_CONTRIB_AMT := :new.RPTD_CHAR_CONTRIB_AMT ;
new_rec.CALC_CHAR_CONTRIB_AMT := :new.CALC_CHAR_CONTRIB_AMT ;
new_rec.RPTD_DIV_DEDUC_AMT := :new.RPTD_DIV_DEDUC_AMT ;
new_rec.CALC_DIV_DEDUC_AMT := :new.CALC_DIV_DEDUC_AMT ;
new_rec.RPTD_EST_PMT_AMT := :new.RPTD_EST_PMT_AMT ;
new_rec.CALC_EST_PMT_AMT := :new.CALC_EST_PMT_AMT ;
new_rec.RPTD_EZ_EMP_CRED_AMT := :new.RPTD_EZ_EMP_CRED_AMT ;
new_rec.CALC_EZ_EMP_CRED_AMT := :new.CALC_EZ_EMP_CRED_AMT ;
new_rec.RPTD_FED_INCM_AMT := :new.RPTD_FED_INCM_AMT ;
new_rec.CALC_FED_INCM_AMT := :new.CALC_FED_INCM_AMT ;
new_rec.RPTD_FRGN_GROSS_UP_AMT := :new.RPTD_FRGN_GROSS_UP_AMT ;
new_rec.CALC_FRGN_GROSS_UP_AMT := :new.CALC_FRGN_GROSS_UP_AMT ;
new_rec.RPTD_LREPT_AMT := :new.RPTD_LREPT_AMT ;
new_rec.CALC_LREPT_AMT := :new.CALC_LREPT_AMT ;
new_rec.RPTD_HRSJT_AMT := :new.RPTD_HRSJT_AMT ;
new_rec.CALC_HRSJT_AMT := :new.CALC_HRSJT_AMT ;
new_rec.RPTD_RELST_TAX_AMT := :new.RPTD_RELST_TAX_AMT ;
new_rec.CALC_RELST_TAX_AMT := :new.CALC_RELST_TAX_AMT ;
new_rec.RPTD_GOVT_INT_AMT := :new.RPTD_GOVT_INT_AMT ;
new_rec.CALC_GOVT_INT_AMT := :new.CALC_GOVT_INT_AMT ;
new_rec.RPTD_IN_AGI1_AMT := :new.RPTD_IN_AGI1_AMT ;
new_rec.CALC_IN_AGI1_AMT := :new.CALC_IN_AGI1_AMT ;
new_rec.RPTD_LRSJT_AMT := :new.RPTD_LRSJT_AMT ;
new_rec.CALC_LRSJT_AMT := :new.CALC_LRSJT_AMT ;
new_rec.RPTD_IN_NOL_AMT := :new.RPTD_IN_NOL_AMT ;
new_rec.CALC_IN_NOL_AMT := :new.CALC_IN_NOL_AMT ;
new_rec.RPTD_INCM_SUBTOT_AMT := :new.RPTD_INCM_SUBTOT_AMT ;
new_rec.CALC_INCM_SUBTOT_AMT := :new.CALC_INCM_SUBTOT_AMT ;
new_rec.RPTD_INT_DUE_AMT := :new.RPTD_INT_DUE_AMT ;
new_rec.CALC_INT_DUE_AMT := :new.CALC_INT_DUE_AMT ;
new_rec.RPTD_IRECV_CRED_AMT := :new.RPTD_IRECV_CRED_AMT ;
new_rec.CALC_IRECV_CRED_AMT := :new.CALC_IRECV_CRED_AMT ;
new_rec.RPTD_LATE_PEN_AMT := :new.RPTD_LATE_PEN_AMT ;
new_rec.CALC_LATE_PEN_AMT := :new.CALC_LATE_PEN_AMT ;
new_rec.RPTD_LIC_CRED_AMT := :new.RPTD_LIC_CRED_AMT ;
new_rec.CALC_LIC_CRED_AMT := :new.CALC_LIC_CRED_AMT ;
new_rec.RPTD_MODIF_AMT := :new.RPTD_MODIF_AMT ;
new_rec.CALC_MODIF_AMT := :new.CALC_MODIF_AMT ;
new_rec.RPTD_NAC_CRED_AMT := :new.RPTD_NAC_CRED_AMT ;
new_rec.CALC_NAC_CRED_AMT := :new.CALC_NAC_CRED_AMT ;
new_rec.RPTD_NONBUS_DISTA_AMT := :new.RPTD_NONBUS_DISTA_AMT ;
new_rec.CALC_NONBUS_DISTA_AMT := :new.CALC_NONBUS_DISTA_AMT ;
new_rec.RPTD_LTOT_AMT := :new.RPTD_LTOT_AMT ;
new_rec.CALC_LTOT_AMT := :new.CALC_LTOT_AMT ;
new_rec.RPTD_OTH_ADJ_AMT := :new.RPTD_OTH_ADJ_AMT ;
new_rec.CALC_OTH_ADJ_AMT := :new.CALC_OTH_ADJ_AMT ;
new_rec.RPTD_OTH_CRED_AMT := :new.RPTD_OTH_CRED_AMT ;
new_rec.CALC_OTH_CRED_AMT := :new.CALC_OTH_CRED_AMT ;
new_rec.RPTD_OTH_PMT_AMT := :new.RPTD_OTH_PMT_AMT ;
new_rec.CALC_OTH_PMT_AMT := :new.CALC_OTH_PMT_AMT ;
new_rec.RPTD_OVERPMT_CRED_AMT := :new.RPTD_OVERPMT_CRED_AMT ;
new_rec.CALC_OVERPMT_CRED_AMT := :new.CALC_OVERPMT_CRED_AMT ;
new_rec.RPTD_PRIOR_EXT_PMT_AMT := :new.RPTD_PRIOR_EXT_PMT_AMT ;
new_rec.CALC_PRIOR_EXT_PMT_AMT := :new.CALC_PRIOR_EXT_PMT_AMT ;
new_rec.RPTD_HRNTX_AMT := :new.RPTD_HRNTX_AMT ;
new_rec.CALC_HRNTX_AMT := :new.CALC_HRNTX_AMT ;
new_rec.RPTD_LRNTX_AMT := :new.RPTD_LRNTX_AMT ;
new_rec.CALC_LRNTX_AMT := :new.CALC_LRNTX_AMT ;
new_rec.RPTD_REFUND_DUE_AMT := :new.RPTD_REFUND_DUE_AMT ;
new_rec.CALC_REFUND_DUE_AMT := :new.CALC_REFUND_DUE_AMT ;
new_rec.RPTD_RELST_PP_TAX_AMT := :new.RPTD_RELST_PP_TAX_AMT ;
new_rec.CALC_RELST_PP_TAX_AMT := :new.CALC_RELST_PP_TAX_AMT ;
new_rec.RPTD_STATE_TAX_AMT := :new.RPTD_STATE_TAX_AMT ;
new_rec.CALC_STATE_TAX_AMT := :new.CALC_STATE_TAX_AMT ;
new_rec.RPTD_SU_TAX_AMT := :new.RPTD_SU_TAX_AMT ;
new_rec.CALC_SU_TAX_AMT := :new.CALC_SU_TAX_AMT ;
new_rec.RPTD_HREPT_AMT := :new.RPTD_HREPT_AMT ;
new_rec.CALC_HREPT_AMT := :new.CALC_HREPT_AMT ;
new_rec.RPTD_SUPP_NI_TAX1_AMT := :new.RPTD_SUPP_NI_TAX1_AMT ;
new_rec.CALC_SUPP_NI_TAX1_AMT := :new.CALC_SUPP_NI_TAX1_AMT ;
new_rec.RPTD_TAX_BUS_INC_AMT := :new.RPTD_TAX_BUS_INC_AMT ;
new_rec.CALC_TAX_BUS_INC_AMT := :new.CALC_TAX_BUS_INC_AMT ;
new_rec.RPTD_TOT_REL_TAX_AMT := :new.RPTD_TOT_REL_TAX_AMT ;
new_rec.CALC_TOT_REL_TAX_AMT := :new.CALC_TOT_REL_TAX_AMT ;
new_rec.RPTD_TAX_SUBTOT_AMT := :new.RPTD_TAX_SUBTOT_AMT ;
new_rec.CALC_TAX_SUBTOT_AMT := :new.CALC_TAX_SUBTOT_AMT ;
new_rec.RPTD_TCSP_CRED_AMT := :new.RPTD_TCSP_CRED_AMT ;
new_rec.CALC_TCSP_CRED_AMT := :new.CALC_TCSP_CRED_AMT ;
new_rec.RPTD_TOT_CRED_AMT := :new.RPTD_TOT_CRED_AMT ;
new_rec.CALC_TOT_CRED_AMT := :new.CALC_TOT_CRED_AMT ;
new_rec.RPTD_TOT_DUE_AMT := :new.RPTD_TOT_DUE_AMT ;
new_rec.CALC_TOT_DUE_AMT := :new.CALC_TOT_DUE_AMT ;
new_rec.RPTD_TOT_OVERPMT_AMT := :new.RPTD_TOT_OVERPMT_AMT ;
new_rec.CALC_TOT_OVERPMT_AMT := :new.CALC_TOT_OVERPMT_AMT ;
new_rec.RPTD_TOT_PMT_AMT := :new.RPTD_TOT_PMT_AMT ;
new_rec.CALC_TOT_PMT_AMT := :new.CALC_TOT_PMT_AMT ;
new_rec.RPTD_HTOT_AMT := :new.RPTD_HTOT_AMT ;
new_rec.CALC_HTOT_AMT := :new.CALC_HTOT_AMT ;
new_rec.RPTD_TAX_DUE_AMT := :new.RPTD_TAX_DUE_AMT ;
new_rec.CALC_TAX_DUE_AMT := :new.CALC_TAX_DUE_AMT ;
new_rec.RPTD_TAX_DUE2_AMT := :new.RPTD_TAX_DUE2_AMT ;
new_rec.CALC_TAX_DUE2_AMT := :new.CALC_TAX_DUE2_AMT ;
new_rec.RPTD_UNDERPMT_PEN_AMT := :new.RPTD_UNDERPMT_PEN_AMT ;
new_rec.CALC_UNDERPMT_PEN_AMT := :new.CALC_UNDERPMT_PEN_AMT ;
new_rec.RFND_1_INT_RATE := :new.RFND_1_INT_RATE ;
new_rec.RFND_1_AMT := :new.RFND_1_AMT ;
new_rec.RFND_2_INT_RATE := :new.RFND_2_INT_RATE ;
new_rec.RFND_2_AMT := :new.RFND_2_AMT ;
new_rec.RFND_3_INT_RATE := :new.RFND_3_INT_RATE ;
new_rec.RFND_3_AMT := :new.RFND_3_AMT ;
new_rec.RFND_4_INT_RATE := :new.RFND_4_INT_RATE ;
new_rec.RFND_4_AMT := :new.RFND_4_AMT ;
new_rec.RPTD_HRAMT_AMT := :new.RPTD_HRAMT_AMT ;
new_rec.CALC_HRAMT_AMT := :new.CALC_HRAMT_AMT ;
new_rec.RPTD_LRAMT_AMT := :new.RPTD_LRAMT_AMT ;
new_rec.CALC_LRAMT_AMT := :new.CALC_LRAMT_AMT ;
new_rec.RPTD_CMBTX_AMT := :new.RPTD_CMBTX_AMT ;
new_rec.CALC_CMBTX_AMT := :new.CALC_CMBTX_AMT ;
new_rec.RPTD_HRSUB_AMT := :new.RPTD_HRSUB_AMT ;
new_rec.CALC_HRSUB_AMT := :new.CALC_HRSUB_AMT ;
new_rec.RPTD_LRSUB_AMT := :new.RPTD_LRSUB_AMT ;
new_rec.CALC_LRSUB_AMT := :new.CALC_LRSUB_AMT ;
new_rec.RPTD_FUEL_CRED_AMT := :new.RPTD_FUEL_CRED_AMT ;
new_rec.CALC_FUEL_CRED_AMT := :new.CALC_FUEL_CRED_AMT ;
new_rec.RPTD_ADJUST_AMT := :new.RPTD_ADJUST_AMT ;
new_rec.CALC_ADJUST_AMT := :new.CALC_ADJUST_AMT ;
new_rec.RPTD_CARRY_YR_NBR := :new.RPTD_CARRY_YR_NBR ;
new_rec.CALC_CARRY_YR_NBR := :new.CALC_CARRY_YR_NBR ;
new_rec.RPTD_APPORT_PCNT := :new.RPTD_APPORT_PCNT ;
new_rec.CALC_APPORT_PCNT := :new.CALC_APPORT_PCNT ;
new_rec.RPTD_IN_APPORT_AMT := :new.RPTD_IN_APPORT_AMT ;
new_rec.CALC_IN_APPORT_AMT := :new.CALC_IN_APPORT_AMT ;
new_rec.RPTD_AGI_TAX_AMT := :new.RPTD_AGI_TAX_AMT ;
new_rec.CALC_AGI_TAX_AMT := :new.CALC_AGI_TAX_AMT ;
new_rec.RPTD_NONBUS_DISTB_AMT := :new.RPTD_NONBUS_DISTB_AMT ;
new_rec.CALC_NONBUS_DISTB_AMT := :new.CALC_NONBUS_DISTB_AMT ;
new_rec.RPTD_TOT_INC_AMT := :new.RPTD_TOT_INC_AMT ;
new_rec.CALC_TOT_INC_AMT := :new.CALC_TOT_INC_AMT ;
new_rec.REMIT_AMT := :new.REMIT_AMT ;
new_rec.RFND_1_DT := :new.RFND_1_DT ;
new_rec.PPIS_NAME := :new.PPIS_NAME ;
new_rec.RFND_2_DT := :new.RFND_2_DT ;
new_rec.EXT_FILED_INDC := :new.EXT_FILED_INDC ;
new_rec.RFND_3_DT := :new.RFND_3_DT ;
new_rec.INIT_RET_INDC := :new.INIT_RET_INDC ;
new_rec.RFND_4_DT := :new.RFND_4_DT ;
new_rec.FINAL_RET_INDC := :new.FINAL_RET_INDC ;
new_rec.INT_PD_TO_DT := :new.INT_PD_TO_DT ;
new_rec.UNITARY_COMB_INDC := :new.UNITARY_COMB_INDC ;
new_rec.PPIS_ST_3_ADDR := :new.PPIS_ST_3_ADDR ;
new_rec.PPIS_ST_1_ADDR := :new.PPIS_ST_1_ADDR ;
new_rec.PPIS_CHK_BOX := :new.PPIS_CHK_BOX ;
new_rec.PPIS_PHN_NMBR := :new.PPIS_PHN_NMBR ;
new_rec.INTERNAL_ID := :new.INTERNAL_ID ;
new_rec.PPIS_ST_2_ADDR := :new.PPIS_ST_2_ADDR ;
new_rec.PPIS_CTRY_CD := :new.PPIS_CTRY_CD ;
new_rec.PPIS_CTY_ADDR := :new.PPIS_CTY_ADDR ;
new_rec.PPIS_CTRY_OLD := :new.PPIS_CTRY_OLD ;
new_rec.PPIS_STATE_CD := :new.PPIS_STATE_CD ;
new_rec.EXT_ATT_INDC := :new.EXT_ATT_INDC ;
new_rec.PPIS_ZIP := :new.PPIS_ZIP ;
new_rec.SCORP_INDC := :new.SCORP_INDC ;
new_rec.PPIS_ID := :new.PPIS_ID ;
new_rec.PPIS_ID_TP_CD := :new.PPIS_ID_TP_CD ;
new_rec.APPORT_METHOD_CD := :new.APPORT_METHOD_CD ;
new_rec.INS_CO_INDC := :new.INS_CO_INDC ;
new_rec.PER_BEGIN_DT := :new.PER_BEGIN_DT ;
new_rec.PER_END_DT := :new.PER_END_DT ;
new_rec.FORM_DT := :new.FORM_DT ;
new_rec.FORM_TYPE_ID := :new.FORM_TYPE_ID ;
new_rec.NOL_CARRYBACK_CD := :new.NOL_CARRYBACK_CD ;
new_rec.FARM_COOP_INDC := :new.FARM_COOP_INDC ;
new_rec.ADD_DT := :new.ADD_DT ;
new_rec.ADD_ID := :new.ADD_ID ;
new_rec.UPD_DT := :new.UPD_DT ;
new_rec.UPD_ID := :new.UPD_ID ;
new_rec.VENDOR_CD := :new.VENDOR_CD ;
new_rec.RPTD_HLTHINSASN_CR_AMT := :new.RPTD_HLTHINSASN_CR_AMT ;
new_rec.CALC_HLTHINSASN_CR_AMT := :new.CALC_HLTHINSASN_CR_AMT ;
new_rec.RPTD_GIT_FINAL_AMT := :new.RPTD_GIT_FINAL_AMT ;
new_rec.CALC_GIT_FINAL_AMT := :new.CALC_GIT_FINAL_AMT ;
new_rec.FISCAL_YR_CD := :new.FISCAL_YR_CD ;
new_rec.RPTD_BONUS_DEPR_AMT := :new.RPTD_BONUS_DEPR_AMT ;
new_rec.CALC_BONUS_DEPR_AMT := :new.CALC_BONUS_DEPR_AMT ;
new_rec.RPTD_PREV_CRYFWD_AMT := :new.RPTD_PREV_CRYFWD_AMT ;
new_rec.CALC_PREV_CRYFWD_AMT := :new.CALC_PREV_CRYFWD_AMT ;
new_rec.RPTD_DOM_PROD_DED_AMT := :new.RPTD_DOM_PROD_DED_AMT ;
new_rec.CALC_DOM_PROD_DED_AMT := :new.CALC_DOM_PROD_DED_AMT ;
new_rec.RPTD_XS_IRC_DED_AMT := :new.RPTD_XS_IRC_DED_AMT ;
new_rec.CALC_XS_IRC_DED_AMT := :new.CALC_XS_IRC_DED_AMT ;
new_rec.RPTD_COAL_CR_AMT := :new.RPTD_COAL_CR_AMT ;
new_rec.CALC_COAL_CR_AMT := :new.CALC_COAL_CR_AMT ;
new_rec.SCHD_M_INDC := :new.SCHD_M_INDC ;
new_rec.INTANG_EXP_INDC := :new.INTANG_EXP_INDC ;
new_rec.RPTD_INTANGEXP_ADJ_AMT := :new.RPTD_INTANGEXP_ADJ_AMT ;
new_rec.CALC_INTANGEXP_ADJ_AMT := :new.CALC_INTANGEXP_ADJ_AMT ;
new_rec.AGIT_CONSOL_INDC := :new.AGIT_CONSOL_INDC ;
new_rec.INCRP_DT := :new.INCRP_DT ;
new_rec.INCRP_STATE_CD := :new.INCRP_STATE_CD ;
new_rec.COMMERCIAL_ST_CD := :new.COMMERCIAL_ST_CD ;
new_rec.INIT_IN_RTN_YR := :new.INIT_IN_RTN_YR ;
new_rec.REC_LOC_ADDR := :new.REC_LOC_ADDR ;
new_rec.EST_TAX_OTH_FID_INDC := :new.EST_TAX_OTH_FID_INDC ;
new_rec.FED_1120_CONSOL_INDC := :new.FED_1120_CONSOL_INDC ;
new_rec.UNTRY_MTRL_CHG_INDC := :new.UNTRY_MTRL_CHG_INDC ;
new_rec.FED_ELEC_CONF_NBRV := :new.FED_ELEC_CONF_NBRV ;
new_rec.RTN_SRC_CD := :new.RTN_SRC_CD ;
new_rec.BANKRPT_INDC := :new.BANKRPT_INDC ;
new_rec.FIT_FILER_INDC := :new.FIT_FILER_INDC ;
new_rec.NAME_CHG_INDC := :new.NAME_CHG_INDC ;
new_rec.REMIC_INDC := :new.REMIC_INDC ;
new_rec.INPUT_SRC_METH_CD := :new.INPUT_SRC_METH_CD ;
new_rec.ANNULZN_INDC := :new.ANNULZN_INDC ;
new_rec.RPTD_REIT_DIV_DED_AMT := :new.RPTD_REIT_DIV_DED_AMT ;
new_rec.CALC_REIT_DIV_DED_AMT := :new.CALC_REIT_DIV_DED_AMT ;
new_rec.RPTD_PAT_INCM_AMT := :new.RPTD_PAT_INCM_AMT ;
new_rec.CALC_PAT_INCM_AMT := :new.CALC_PAT_INCM_AMT ;
new_rec.RPTD_MDA_PROD_CR_AMT := :new.RPTD_MDA_PROD_CR_AMT ;
new_rec.CALC_MDA_PROD_CR_AMT := :new.CALC_MDA_PROD_CR_AMT ;
IF inserting THEN
v_change_type := 'INSERT';
ELSIF updating THEN
v_change_type := 'UPDATE';
ELSIF deleting THEN
v_change_type := 'DELETE';
END IF;
--call to do base table insert, update or delete
RSDGP004.bus_ta_form_97A(in_event_user => user,
in_event_source => v_event_source,
in_change_type => v_change_type,
in_old_rec => old_rec,
in_new_rec => new_rec);
-- call to build xml for rti_table_audits and queues --xdbaud
RSDGP001.bus_ta_form_97A(in_event_user => user,
in_event_source => v_event_source,
in_change_type => v_change_type,
in_old_rec => old_rec,
in_new_rec => new_rec);
END;}
Edited by: SDL on Feb 17, 2009 4:54 AM
Edited by: SDL on Feb 17, 2009 5:09 AM
Edited by: SDL on Feb 17, 2009 5:14 AMHere is the insert code that is in the package RSDGP004 that does the insert into the base table for the view.
I think maybe this is what you meant, when you asked for the code that does the insert?
{ELSIF in_change_type = 'INSERT' THEN
levent := 'INSERT';
INSERT INTO rti_bus_ta_forms(
add_dt
, add_id
, tran_id
, doc_loc_nbr
, field_009_amt
, field_01_txt
, field_010_amt
, field_015_amt
, field_016_amt
, field_02_txt
, field_029_amt
, field_03_txt
, field_030_amt
, field_039_amt
, field_04_txt
, field_040_amt
, field_041_amt
, field_042_amt
, field_05_txt
, field_053_amt
, field_054_amt
, field_06_txt
, field_063_amt
, field_064_amt
, field_067_amt
, field_068_amt
, field_07_txt
, field_079_amt
, field_08_txt
, field_080_amt
, field_085_amt
, field_086_amt
, field_09_txt
, field_091_amt
, field_092_amt
, field_095_amt
, field_096_amt
, field_10_txt
, field_101_amt
, field_102_amt
, field_103_amt
, field_104_amt
, field_105_amt
, field_106_amt
, field_11_txt
, field_111_amt
, field_112_amt
, field_12_txt
, field_125_amt
, field_126_amt
, field_127_amt
, field_128_amt
, field_13_txt
, field_131_amt
, field_132_amt
, field_137_amt
, field_138_amt
, field_139_amt
, field_14_txt
, field_140_amt
, field_141_amt
, field_142_amt
, field_143_amt
, field_144_amt
, field_147_amt
, field_148_amt
, field_149_amt
, field_15_txt
, field_150_amt
, field_151_amt
, field_152_amt
, field_153_amt
, field_154_amt
, field_16_txt
, field_165_amt
, field_166_amt
, field_167_amt
, field_168_amt
, field_169_amt
, field_170_amt
, field_171_amt
, field_172_amt
, field_181_amt
, field_182_amt
, field_175_amt
, field_176_amt
, field_177_amt
, field_178_amt
, field_179_amt
, field_180_amt
, field_193_amt
, field_194_amt
, field_195_amt
, field_196_amt
, field_197_amt
, field_198_amt
, field_199_amt
, per_begin_dt
, per_end_dt
, form_dt
, form_type_id
, field_31_txt
, field_201_amt
, upd_dt
, upd_id
, field_27_txt
, field_006_amt
, field_007_amt
, field_008_amt
, field_005_amt
, field_21_txt
, field_22_txt
, field_23_txt
, field_020_amt
, field_021_amt
, field_022_amt
, field_023_amt
, field_024_amt
, field_025_amt
, field_026_amt
, field_027_amt
, field_028_amt
, field_031_amt
, field_183_amt
, field_184_amt
, field_034_amt
, field_035_amt
, field_036_amt
, field_191_amt
, field_192_amt
, field_188_amt
, field_189_amt
, field_17_txt
, field_18_txt
, field_33_txt
, field_19_txt
, field_39_txt
, field_20_txt
, field_185_amt
, field_186_amt
, field_24_txt )
VALUES(
in_new_rec.ADD_DT,
in_new_rec.ADD_ID,
in_new_rec.TRAN_ID,
in_new_rec.DOC_LOC_NBR,
in_new_rec.RPTD_BAL_DUE_AMT,
in_new_rec.EXT_ATT_INDC,
in_new_rec.CALC_BAL_DUE_AMT,
in_new_rec.RPTD_REL_TAX_AMT,
in_new_rec.CALC_REL_TAX_AMT,
in_new_rec.EXT_FILED_INDC,
in_new_rec.RPTD_EST_PMT_AMT,
in_new_rec.PPIS_CTRY_CD,
in_new_rec.CALC_EST_PMT_AMT,
in_new_rec.RPTD_HRAMT_AMT,
in_new_rec.PPIS_ST_3_ADDR,
in_new_rec.CALC_HRAMT_AMT,
in_new_rec.RPTD_CMBTX_AMT,
in_new_rec.CALC_CMBTX_AMT,
in_new_rec.INTERNAL_ID,
in_new_rec.RPTD_LTOT_AMT,
in_new_rec.CALC_LTOT_AMT,
in_new_rec.PPIS_ID,
in_new_rec.RPTD_INT_DUE_AMT,
in_new_rec.CALC_INT_DUE_AMT,
in_new_rec.RPTD_LATE_PEN_AMT,
in_new_rec.CALC_LATE_PEN_AMT,
in_new_rec.PPIS_ID_TP_CD,
in_new_rec.RPTD_HRNTX_AMT,
in_new_rec.PPIS_NAME,
in_new_rec.CALC_HRNTX_AMT,
in_new_rec.RPTD_OTH_PMT_AMT,
in_new_rec.CALC_OTH_PMT_AMT,
in_new_rec.PPIS_ST_1_ADDR,
in_new_rec.RPTD_OVERPMT_CRED_AMT,
in_new_rec.CALC_OVERPMT_CRED_AMT,
in_new_rec.RPTD_PRIOR_EXT_PMT_AMT,
in_new_rec.CALC_PRIOR_EXT_PMT_AMT,
in_new_rec.PPIS_ST_2_ADDR,
in_new_rec.RPTD_HREPT_AMT,
in_new_rec.CALC_HREPT_AMT,
in_new_rec.RPTD_HRSUB_AMT,
in_new_rec.CALC_HRSUB_AMT,
in_new_rec.RPTD_REFUND_DUE_AMT,
in_new_rec.CALC_REFUND_DUE_AMT,
in_new_rec.PPIS_CTY_ADDR,
in_new_rec.RPTD_RENT_AMT,
in_new_rec.CALC_RENT_AMT,
in_new_rec.PPIS_STATE_CD,
in_new_rec.RPTD_SU_TAX_AMT,
in_new_rec.CALC_SU_TAX_AMT,
in_new_rec.RPTD_HRSJT_AMT,
in_new_rec.CALC_HRSJT_AMT,
in_new_rec.PPIS_ZIP,
in_new_rec.RPTD_SUPP_NI_TAX1_AMT,
in_new_rec.CALC_SUPP_NI_TAX1_AMT,
in_new_rec.RPTD_TAX_DUE_AMT,
in_new_rec.CALC_TAX_DUE_AMT,
in_new_rec.RPTD_TOT_DUE_AMT,
in_new_rec.PPIS_PHN_NMBR,
in_new_rec.CALC_TOT_DUE_AMT,
in_new_rec.RPTD_TOT_OVERPMT_AMT,
in_new_rec.CALC_TOT_OVERPMT_AMT,
in_new_rec.RPTD_TOT_PMT_AMT,
in_new_rec.CALC_TOT_PMT_AMT,
in_new_rec.RPTD_TOT_REL_TAX_AMT,
in_new_rec.CALC_TOT_REL_TAX_AMT,
in_new_rec.RPTD_UNDERPMT_PEN_AMT,
in_new_rec.PPIS_CHK_BOX,
in_new_rec.CALC_UNDERPMT_PEN_AMT,
in_new_rec.RPTD_HTOT_AMT,
in_new_rec.CALC_HTOT_AMT,
in_new_rec.RPTD_HRBAL_AMT,
in_new_rec.CALC_HRBAL_AMT,
in_new_rec.PPIS_CTRY_OLD,
in_new_rec.RPTD_LRNTX_AMT,
in_new_rec.CALC_LRNTX_AMT,
in_new_rec.RPTD_LRBAL_AMT,
in_new_rec.CALC_LRBAL_AMT,
in_new_rec.RPTD_LREPT_AMT,
in_new_rec.CALC_LREPT_AMT,
in_new_rec.RPTD_LRSUB_AMT,
in_new_rec.CALC_LRSUB_AMT,
in_new_rec.RPTD_LRSJT_AMT,
in_new_rec.CALC_LRSJT_AMT,
in_new_rec.RPTD_LRAMT_AMT,
in_new_rec.CALC_LRAMT_AMT,
in_new_rec.RPTD_AGI_TAX_AMT,
in_new_rec.CALC_AGI_TAX_AMT,
in_new_rec.RPTD_TOT_UNREL_TAX_AMT,
in_new_rec.CALC_TOT_UNREL_TAX_AMT,
in_new_rec.RPTD_GI_TAX_AMT,
in_new_rec.CALC_GI_TAX_AMT,
in_new_rec.RPTD_TAX_DUE2_AMT,
in_new_rec.CALC_TAX_DUE2_AMT,
in_new_rec.RPTD_TOT_URL_AMT,
in_new_rec.CALC_TOT_URL_AMT,
in_new_rec.REMIT_AMT,
in_new_rec.PER_BEGIN_DT,
in_new_rec.PER_END_DT,
in_new_rec.FORM_DT,
in_new_rec.FORM_TYPE_ID,
in_new_rec.NOL_CARRYBACK_CD,
in_new_rec.CALC_IN_NOL_AMT,
in_new_rec.UPD_DT,
in_new_rec.UPD_ID,
in_new_rec.VENDOR_CD,
in_new_rec.RPTD_PREV_CRYFWD_AMT,
in_new_rec.CALC_PREV_CRYFWD_AMT,
in_new_rec.RPTD_TOT_CRED_AMT,
in_new_rec.CALC_TOT_CRED_AMT,
in_new_rec.FISCAL_YR_CD,
in_new_rec.INIT_RET_INDC,
in_new_rec.FINAL_RET_INDC,
in_new_rec.RPTD_FED_INCM_AMT,
in_new_rec.CALC_FED_INCM_AMT,
in_new_rec.RPTD_BONUS_DEPR_AMT,
in_new_rec.CALC_BONUS_DEPR_AMT,
in_new_rec.RPTD_SPF_DEDUCT_AMT,
in_new_rec.CALC_SPF_DEDUCT_AMT,
in_new_rec.RPTD_GOVT_INT_AMT,
in_new_rec.CALC_GOVT_INT_AMT,
in_new_rec.RPTD_URL_SUBTOT_AMT,
in_new_rec.CALC_URL_SUBTOT_AMT,
in_new_rec.RPTD_APPORT_PCNT,
in_new_rec.CALC_APPORT_PCNT,
in_new_rec.RPTD_IN_INCM_AMT,
in_new_rec.CALC_IN_INCM_AMT,
in_new_rec.RPTD_IN_NOL_AMT,
in_new_rec.RPTD_TOT_URL_INCM_AMT,
in_new_rec.CALC_TOT_URL_INCM_AMT,
in_new_rec.RPTD_TOT_MOD_AMT,
in_new_rec.CALC_TOT_MOD_AMT,
in_new_rec.SCHD_M_INDC,
in_new_rec.FED_ELEC_CONF_NBRV,
in_new_rec.RTN_SRC_CD,
in_new_rec.BANKRPT_INDC,
in_new_rec.NAME_CHG_INDC,
in_new_rec.INPUT_SRC_METH_CD,
in_new_rec.RPTD_PAT_INCM_AMT,
in_new_rec.CALC_PAT_INCM_AMT,
in_new_rec.ANNULZN_INDC) ;} -
Flat file to tables (insert/update/delete) using utl file.--urgent
Hi all,
Scenorio s here ...
ex : emp
EMPNO
ENAME
JOB
MGR
HIREDATE
SAL
COMM
DEPTNO
STATUS -- i/U/d
flat file records willbe like this ....
I^001^name^job^manager^10-dec-2002^90000^900^^
I^001^name^job^manager^10-dec-2002^90000^900^343^
U,002^name^job^manager^10-dec-2002^90000^900^899^900
U,002^name^job^manager^10-dec-2002^90000^900^899^900
The first record indicator show I , so need to insert into the table emp.The second record indicator show U , so need to update the table emp.like this i've 5 tables(different structure and large data ).
How do i upload data into concern tables using procedures using UTL_file.
Needs to generalised the processing (for each table specific)..........
(me right now doing this way...in a pakage with UTL_FILE using pl/sql tables,parsing the record by record ,
storeing the values in a pl/sql table then insert/updates....)
any sugg'n ? idea? sample code ?
Thanx OTN members.Hi Ganesan,
Hope it will help.
Best Regards
CREATE OR REPLACE PROCEDURE TEST_UTL
loc_input_file varchar2(30) ;
loc_input_path varchar2(30) ;
loc_utl_file UTL_FILE.FILE_TYPE;
loc_get_data varchar2(500);
BEGIN
loc_utl_file := UTL_FILE.FOPEN(loc_input_path, loc_input_file, R');
BEGIN
LOOP
UTL_FILE.GET_LINE(loc_utl_file,loc_get_data);
IF SUBSTR(loc_get_data,1,1) = 'I' THEN
INSERT INTO ..........
-- USE SUBSTR function for columng break
ELSIF SUBSTR(loc_get_data,1,1) = 'U' THEN
UPDATE ....................
END IF;
EXCEPTION
WHEN NO_DATA_FOUND THEN
UTL_FILE.FCLOSE(loc_utl_file);
END ;
EXCEPTION
END; -
Why should avoid OLTP compression on tables with massive update/insert?
Dear expert,
We are planning oracle OLTP compression on a IS-U system, could you tell me
Why should avoid OLTP compression on tables with massive update/insert?
What kind of impact on the performance in the worst case?
Best regards,
KateHi
When updating compressed data Oracle has to read it, uncompress it and update it.
The compression is then performed again later asynchronously. This does require a lot more CPU than for a simple update.
An other drawback is that compression on highly modified tables will generate a major increase in redo / undo log generation. I've experienced it on an DB where RFC tables where by mistake compressed, the redo increase was over 15%.
Check the remark at the end of Jonathan Lewis post.
Regards
http://allthingsoracle.com/compression-in-oracle-part-3-oltp-compression/
Possibly this is all part of the trade-off that helps to explain why Oracle doesn't end up compressing the last few rows that get inserted into the block.
The effect can be investigated fairly easily by inserting about 250 rows into the empty table - we see Oracle inserting 90 rows, then generating a lot of undo and redo as it compresses those 90 rows; then we insert another 40 rows, then generate a lot of undo and redo compressing the 130 rows. Ultimately, by the time the block is full we have processed the first 90 rows into the undo and redo four or five times. -
Impdp errors with ORA-01400: cannot insert NULL into
Hi Experts,
I have very intresting situation when I use impdp to import table back to DB.
Environment:
Database Server: 10.2.0.4 Enterprise
OS: RHEL 5.5 64-bit
We have a table and it's size is 350+ GB and so to reclaim space I want to perform expdp/impdp operation. When I following below steps:
1) expdp table
2) drop table
3) impdp full table
It works like a charm and I am able to reclaim 83% space and table size shows about 20GB.
But when I follow below method:
1) expdp table
2) truncate table (To save some time not to import indexes, stats, constraints , etc)
3) impdp table
I get following error:
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Master table "SYS"."SYS_IMPORT_TABLE_01" successfully loaded/unloaded
Starting "SYS"."SYS_IMPORT_TABLE_01": sys/******** tables=<schema>.<table_name> directory=test_dir dumpfile=<table_name>_%u.dmp logfile=impdp_<table_name>.log parallel=16 CONTENT=DATA_ONLY
Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
ORA-31693: Table data object "<schema"."table_name" failed to load/unload and is being skipped due to error:
ORA-01400: cannot insert NULL into ("schema"."table_name"."ID")
Job "SYS"."SYS_IMPORT_TABLE_01" completed with 1 error(s) at 16:12:28
Please advise how to proceed further, it seems like I am hitting some sort of Bug but metalink does not show any.
Regards,
MS
Edited by: user10651321 on Nov 9, 2012 4:38 PMexpdp and impdp operations should not be executed as SYS - try SYSTEM account instead. See first Note section here - http://docs.oracle.com/cd/B19306_01/server.102/b14215/dp_import.htm#sthref243
Pl post the complete expdp and impdp commands used, along with a description of the table for which you encounter this error.
HTH
Srini -
Help with inserting values -- ORA-00984 error
Hello!
This time we have a problem with inserting values and we really can't find what's wrong!
The table was created as such
CREATE TABLE PASSAGER
(NO_PERSONNE INTEGER,
NO_PASSAGER INTEGER NOT NULL,
NO_PASSEPORT INTEGER NOT NULL,
NATIONALITE VARCHAR2(30) NOT NULL,
LIEU_EMISSION VARCHAR2(30) NOT NULL,
DATE_EMISSION DATE NOT NULL,
NO_TEL INTEGER,
NO_CC INTEGER,
NO_VENTE INTEGER NOT NULL,
CONSTRAINT PK_PASSAGER PRIMARY KEY (NO_PERSONNE),
CONSTRAINT FK_PASSAGER_PERSONNE FOREIGN KEY (NO_PERSONNE) REFERENCES PERSONNE (NO_PERSONNE),
CONSTRAINT FK_PASSAGER_VENTE FOREIGN KEY (NO_VENTE) REFERENCES VENTE (NO_VENTE));
We created a sequence..
CREATE SEQUENCE NOPASS_SEQ
START WITH 1
INCREMENT BY 1
NOCACHE
NOCYCLE;
for inserting the values, we did...
INSERT INTO PASSAGER VALUES (500,NOPASS_SEQ.NEXTVAL, WT456789,'CANADIENNE', 'CANADA', to_date('2007/10/12','YYYY/MM/DD'),5142348756,5157981500126734,1);
but it won't work, it's our last table and all the other worked perfectly!
Thanks a ton!In your table creation, you got third column as
NO_PASSEPORT INTEGER NOT NULL,
where as you are passing varchar values (see bold)
INSERT INTO PASSAGER VALUES (500,NOPASS_SEQ.NEXTVAL, WT456789,+'CANADIENNE', 'CANADA', to_date('2007/10/12','YYYY/MM/DD'),5142348756,5157981500126734,1);
Should be like this I suppose
INSERT INTO PASSAGER VALUES (500,NOPASS_SEQ.NEXTVAL, *456789*,'CANADIENNE', 'CANADA', to_date('2007/10/12','YYYY/MM/DD'),5142348756,5157981500126734,1); -
Master data attributes with direct update...its very urgent
Hi all,
Could anyone tell me how to laod the master data attributes with direct update in the infopackge..
provide steps to create master data attributes and how to load..
Thanks,
ManjulaHi Manjula,
Flexible Uploading
Transaction code RSA1LEAD YOU TO MODELLING
1. Creation of Info Objects
In left panel select info object
Create info area
Create info object catalog ( characteristics & Key figures ) by right clicking the created info area
Create new characteristics and key figures under respective catalogs according to the project requirement
Create required info objects and Activate.
2. Creation of Data Source
In the left panel select data sources
Create application component(AC)
Right click AC and create datasource
Specify data source name, source system, and data type ( Transaction data )
In general tab give short, medium, and long description.
In extraction tab specify file path, header rows to be ignored, data format(csv) and data separator( , )
In proposal tab load example data and verify it.
In field tab you can you can give the technical name of info objects in the template and you not have to map during the transformation the server will automatically map accordingly. If you are not mapping in this field tab you have to manually map during the transformation in Info providers.
Activate data source and read preview data under preview tab.
Create info package by right clicking data source and in schedule tab click star to load data to PSA.( make sure to close the flat file during loading )
3. Creation of data targets
In left panel select info provider
Select created info area and right click to create ODS( Data store object ) or Cube.
Specify name fro the ODS or cube and click create
From the template window select the required characteristics and key figures and drag and drop it into the DATA FIELD and KEY FIELDS
Click Activate.
Right click on ODS or Cube and select create transformation.
In source of transformation , select object type( data source) and specify its name and source system Note: Source system will be a temporary folder or package into which data is getting stored
Activate created transformation
Create Data transfer process (DTP) by right clicking the master data attributes
In extraction tab specify extraction mode ( full)
In update tab specify error handling ( request green)
Activate DTP and in execute tab click execute button to load data in data targets.
4. Monitor
Right Click data targets and select manage and in contents tab select contents to view the loaded data. There are two tables in ODS new table and active table to load data from new table to active table you have to activate after selecting the loaded data . Alternatively monitor icon can be used
honor with points if this helps,
Sudhakar -
Insert / update data to a table through DBLINK (oracle)
I try to insert / update a table from one instance of oracle database to another one through oracle dblink, get following error:
java.sql.SQLException: ORA-01008: not all variables bound
ORA-02063: preceding line from MYLINK
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:289)
at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:582)
at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1986)
at oracle.jdbc.ttc7.TTC7Protocol.parseExecuteFetch(TTC7Protocol.java:1144)
at oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.java:2152)
at oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.java:2035)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:2876)
at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:609)
The same code to insert / update the exact same table in local instance works fine.No any binding problem. So i am pretty sure all ? mark in SQL are set with some value before sending to Oracle.
Someone please advise what is possible problem. Db link is not set correctly? or we can not update remote table by dblink.
By the way i can do insert / update from TOAD to the remote table through DBLINK. Problem happens only in Java code.
thanks!
Garydblink links from one database instance to another.
So it is certainly a source of possible problems when it works on one database and not another.
You should start by looking at the dblink and it possible testing it in the database not via java.
Note as well that that error suggests that it is coming from the Oracle database. I believe if you had a bind parameter problem in your java code that the error would come from the driver. But that is a guess on my part. -
Insert/update japanese langunage data in a column of datatype varchar2(..)
Hello,
I am using ORACLE DATABASE 11g (EE) and RHEL 5.
I want to insert/update japanese language data in a column which has the datatype as varchar2(256).
I tried to change the NLS_LANGUAGE and NLS_TERRITORY parameters with 'ALTER SESSION set ...' command but no effect.
I tried to bounce back ( shutdown and startup ) the DB but still no effect.
I tried to inset the NLS_LANGUAGE and NLS_TERRITORY in init.ora file but still no use.
If anybody knows the detail steps which i have mentioned above .... let me know. Might be that i am wrong in my method.
Can you please guide me how to change the language of DB for a perticular session to japanese ???
Thanks in advance...
Edited by: VJ4 on May 9, 2011 6:21 PMVJ4 wrote:
Thanks for the info.
Yes i tried with UNISTR function and was able to insert the data successfully.
but the point is that we can't remember unicode for each of the letter. It's their any method that we can directly insert japanese character using an insert.
As you said :-
Note that changing database character set is something complicated that requires many steps.
Can you please provide me some links or some stuffs to study about the detail steps of chaining database character set.
I have gone through the Oracle online documentation.. if you can pin point any good link in it you can else provide me some other stuff.
Thanks .You will need to convert your database characterset to AL32UTF8. This is not a trivial exercise if your database already has data in it. See these MOS Docs
Changing the NLS_CHARACTERSET to AL32UTF8 / UTF8 (Unicode) (Doc ID 260192.1)
AL32UTF8 / UTF8 (Unicode) Database Character Set Implications (Doc ID 788156.1)
http://download.oracle.com/docs/cd/E11882_01/server.112/e10729/ch11charsetmig.htm#g1011430
HTH
Srini -
JBO-26030 and ORA-00054 error when updating a certain row
I have a page that saves data when you leave a cell in a table. Everything seems to work fine, but when you get to some cells the JBO-26030 error pops up and then no matter what you do you can't ever save anything on that cell. You can close everything down and reopen and change other cells, but when you go back to that cell the error message always pops up. I think it's mainly happening on the cell that is a drop down with 3 values (P, F, and NT). P is the value and key for the drop down.
Then when I go into the database through Toad I try to change the value just so see what happens and that's when I get the ORA-00054: resource busy and acquire with NOWAIT specified error. This again only happens when editing that row.
Any help is appreciated...Thanks!
Edited by: user10942416 on Aug 6, 2009 6:16 AMThis error is caused when the block property 'DML returning values' equals YES. This property was introduced as of forms 6. What does it do ? As per the on-line help of Forms, "A database update or insert action may initiate server-side triggers that cause alterations or additional changes in the data. In Release 6, when using an Oracle8 database server, Forms uses the DML Returning clause to immediately bring back any such changes. When this property is set to Yes, Forms will automatically update the client-side version of the data, and the user will not need to re-query the database to obtain the changed values". When this property is switched to yes the generated insert/update statement will contain the 'returning clause' and this clause is causing the error.
As far as I have tested, the only way at present, to get rid of this error is to set 'DML returing values' to NO. So, not to use this functionality.
See also:
http://support.oracle.co.uk/metalink/plsql/ml2_documents.showFrameDocument?p_database_id=NOT&p_id=143395.1
Please respond if this solution works for you.
Greets,
Guido Zeelen -
Insert/update - merge apex items
hello =)
i want to insert data into a table and if the table has already the "List_id" i want to update values:
begin
FOR i IN 1..APEX_APPLICATION.G_F01.COUNT LOOP
MERGE INTO list_values
USING dual
ON (list_values.list_id = to_number(APEX_APPLICATION.G_F02(i))
WHEN MATCHED THEN
UPDATE
SET
list_values.product_fk=:P900_PRODUCT_NAME,
ist_values.attribute=APEX_APPLICATION.G_F04(i),
list_values.value=APEX_APPLICATION.G_F05(i)
WHEN NOT MATCHED THEN
INSERT
list_values.product_fk,list_values.attribute,list_values.value
VALUES
*:P900_PRODUCT_NAME,APEX_APPLICATION.G_F04(i),APEX_APPLICATION.G_F05(i)*
end loop;
end;
got a lot of sql errors...
+1+ error has occurred
ORA-06550:line 6, column 65: PL/SQL: ORA-00907: missing right parenthesis ORA-06550: line 4, column 1: PL/SQL: SQL Statement ignored
Maybe someone can help me with the syntax of the merge statement or maybe merge doesn't work in this case. because of the apex_items.
also got seperated insert/update process. they work perfect, if i use the processes singly:
Begin
FOR i IN 1..APEX_APPLICATION.G_F01.COUNT LOOP
insert into List_values (product_fk,attribute,value)
values (:P900_PRODUCT_NAME,APEX_APPLICATION.G_F04(i),APEX_APPLICATION.G_F05(i));
END LOOP;
end;
begin
FOR i IN 1..APEX_APPLICATION.G_F01.COUNT LOOP
update List_values
set
product_fk=:P900_PRODUCT_NAME,
attribute=APEX_APPLICATION.G_F04(i),
value=APEX_APPLICATION.G_F05(i)
where list_id=to_number(APEX_APPLICATION.G_F02(i));
END LOOP;
end;
Maybe someone can help me to combine them.
Thank u =)You were missing a right parenthesis at the end of line 7.
BEGIN
FOR i IN 1 .. APEX_APPLICATION.g_f01.COUNT
LOOP
MERGE INTO LIST_VALUES
USING DUAL
ON (LIST_VALUES.list_id =
TO_NUMBER (APEX_APPLICATION.g_f02 (i)))
WHEN MATCHED
THEN
UPDATE SET
LIST_VALUES.product_fk = :p900_product_name,
ist_values.attribute = APEX_APPLICATION.g_f04 (i),
LIST_VALUES.VALUE = APEX_APPLICATION.g_f05 (i)
WHEN NOT MATCHED
THEN
INSERT (LIST_VALUES.product_fk,
LIST_VALUES.attribute,
LIST_VALUES.VALUE)
VALUES (
:p900_product_name,
APEX_APPLICATION.g_f04 (i),
APEX_APPLICATION.g_f05 (i));
END LOOP;
END;Jeff
Maybe you are looking for
-
The battery for my macbook pro 13 says "service battery". Now I want to get a replacement but the reviews for it are horrible! Does anybody have any suggestions? I don't want to spend 130 dollars on something I'm going to have to replace in less tha
-
Should I be able to see networked computers in Finder?
Forgive me if this is totally obvious. Should I be able to click on Network in Finder and see networked PCs on my LAN? I can share and transfer files from a laptop to this iMac, but I don't have the laptop with me right now. I'm trying to see a diffe
-
Can't Copy Files to Remote External Hard Drive
I have two Macs, a Macbook Pro, and an iMac, both running 10.5.5. Whenever I'm logged into one and connected to the other via saved credentials from Keychain, I get the following error when trying to copy files from the local machine to the remote ma
-
Hi, We have a scenario whereby we are performing a HTTP post to a service. The problem is that the service expects a raw/plain text body. So we need to remove the XML and just out put the content of one field. I know that it is possible to do this us
-
PLANNEDORDER_GETDETAIL Msg type how to create IDOC TYpe
I have copied the BO BUS2004 to a ZBUS2004 along with Messagt type ZPLANNEDORDER_GETDETAIL, FM ZBAPI_PLANNEDORDER_GET_DETAIL, what I cannot do if create a copy of the required IDOC TYPE. PLANNEDORDER_GETDETAIL01 does not exist, I want to make a ZPL