ORA-00001
DEV 6I, db 10g, win 8,
Hello
I have a master-details form based on two blocks
1 - purchase_order (order_id pk).
2 - purchase_order_detail (fk order_id).
I want to insert separate 'ITEM_ID' of the secondary table column values in a column in a third table, called 'STOCK. PRODUCT_ID.
SO, I used this code:
DECLARE CURSOR DIS_ITEMS_C IS SELECT DISTINCT ITEM_ID FROM ITEMS ; V_ITEM NUMBER ; BEGIN GO_BLOCK('PURCHASE_ORDER_DETAIL') ; FIRST_RECORD ; GO_ITEM('PURCHASE_ORDER_DETAIL.ITEM_ID') ; LOOP INSERT INTO ITEMS VALUES (:ITEM_ID) ; EXIT WHEN :SYSTEM.LAST_RECORD = 'TRUE'; DOWN ; END LOOP ; COMMIT ; OPEN DIS_ITEMS_C ; LOOP FETCH DIS_ITEMS_C INTO V_ITEM ; INSERT INTO STOCK (PRODUCT_ID) VALUES (V_ITEM) ; EXIT WHEN DIS_ITEMS_C%NOTFOUND ; END LOOP ; COMMIT ; END ;
but I am facing unique ora-00001 "constraint violated", I don't know why?
the main table inserts normally and retail as well, so the rest are the 'STOCK' AND 'ELEMENTS' TABLES,
The 'ELEMENTS' has no. the CONSTRAINTS of TABLE and selects the "DISTINCT" from him I then insert them into the "STOCK"?
I tried to do what the form do this manually with instructions insert and insert it normally, I don't see this error? you have an idea
causes of this error is displayed?
Thank you
The mistake is that your
WHEN THE OUTPUT DIS_ITEMS_C % NOTFOUND;
is this bad place atheist. He should be immediately after EXTRACTION. With your code, the last record has been inserted twice.
Tags: Oracle Development
Similar Questions
-
ORA-00001 violation, always on the 2nd insertion irrespective of the values
Connected to:
Database Oracle 12 c Enterprise Edition Release 12.1.0.2.0 - 64 bit Production
With the options of partitioning, OLAP, advanced analytics and Real Application Testing
I get a UK violation when I shouldn't be, and I'm stuck. Where to look to figure out what is causing the problem? Excerpts below.
I insert only two records. The second insertion always fails, regardless of the value of LOT_NO.
I.E.
- If the first insert is with LOT_NO 1234, the 2nd insertion with LOT_NO 1235 fails.
- If the first insert is with LOT_NO 1235, the 2nd insertion with LOT_NO 1234 fails.
truncate table ppr_lots;
commit;
Select * from ppr_lots; -not return any records
-alter table ppr_lots change the lot_uk disable constraint;
insert into PPR_LOTS (lot_no, lot_id, lot_type_id, lot_status_type_id, cadastral_area_id, land_tenure_type_id, land_use_type_id, lot_demarcation_type_id, the plan_id argument, address_id, lot_building_id, pid, legal_issues_yn, lot_size, area_unit_type_id, gis_data_captured_yn, short_legal_dsc, long_legal_dsc, eff_from_dtm) eff_through_dtm remarks_dsc, section_locator_no, lot_guid, logically_deleted_yn, concurrency_check_ts, log_created_by_user_id, log_created_ts, log_updated_by_user_id, log_updated_ts)
values (1234, 2, 5305, 5201, 23, 4700, 1802, 5000, 1, null, null, 1, 'n', 10, 201, 'Y', 'GAC002001234', null, null, null, null, null, null, 'n', to_timestamp (27 November 2015 09:05:42.517978', 'dd-mm-yyyy hh24:mi:ss.ff'), 1, to_timestamp (27 November 2015 09:05:42.517978', 'dd-mm-yyyy hh24:mi:ss.ff'), null, null);
insert into PPR_LOTS (lot_no, lot_id, lot_type_id, lot_status_type_id, cadastral_area_id, land_tenure_type_id, land_use_type_id, lot_demarcation_type_id, the plan_id argument, address_id, lot_building_id, pid, legal_issues_yn, lot_size, area_unit_type_id, gis_data_captured_yn, short_legal_dsc, long_legal_dsc, eff_from_dtm) eff_through_dtm remarks_dsc, section_locator_no, lot_guid, logically_deleted_yn, concurrency_check_ts, log_created_by_user_id, log_created_ts, log_updated_by_user_id, log_updated_ts)
values (1235, 3, 5304, 5201, 24, 4701, 1802, 5000, 2, null, null, 2, 'n', 104.5, 200, 'Y', 'CEC003001235', null, null, null, null, null, null, 'n', to_timestamp (27 November 2015 09:05:42.538275', 'dd-mm-yyyy hh24:mi:ss.ff'), 1, to_timestamp (27 November 2015 09:05:42.538275', 'dd-mm-yyyy hh24:mi:ss.ff'), null, null);
Error report-
SQL error: ORA-00001: unique constraint (LIS_PPR. LOT_UK) violated
00001 00000 - "forced single (s.%s) violated."
* Cause: An UPDATE or INSERT statement attempted to insert a duplicate key.
For Trusted Oracle configured in DBMS MAC mode, you can see
This message if there is an entry double at a different level.
* Action: Either remove the single restriction or not to insert the key.
BTW, if I turn off the UK, everything is fine.
-Ken
LOT_UK is defined simply as follows.
ALTER TABLE PPR_LOTS
ADD CONSTRAINT LOT_UK UNIQUE
(
LOT_NO
)
USING INDEX
(
CREATE A UNIQUE LOT_UK ON PPR_LOTS (LOT_NO CAD) INDEX
LOGGING
TABLESPACE USERS
PCTFREE 10
INITRANS 2
STORAGE
(
65536 INITIAL
NEXT 1048576
MINEXTENTS 1
MAXEXTENTS UNLIMITED
DEFAULT USER_TABLES
)
NOPARALLEL
)
ENABLE;
Found the problem.
I thought that I had disabled triggers. Turns out I didn't, and a defective trigger is overwhelming as LOT_NO.
It's always the answer is simple.
-Ken
-
Need help with Ora-00001: constraint Unique voilated in catalog synchronization
Hi Experts...
Has got some problem in the catalog... desperately need help...
Oracle: 11 GR 2
Here is a detail of the error.
from full resynchronization of the recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03009: failure of command resync to the default channel on 26/11/2013 18:01:34
ORA-01403: no data found
ORA-00001: unique constraint (DNKF_GRIP. BRL_U1) violated
========================++++++++++++++++=========================
Kind regards
Hei,
Cool... I have also encountered this kind of error long back... Follow and fortunately we it will be solved.
A problem with the constraint or the Index after the upgrade of the catalogue in 11 GR 2
Remove the constraint, if available, otherwise check index, if found the drop... Rest is history...
First, check the BRL_U1... It can be constrained or an index on the catalog database.
May be it's problem... the compulsion was abandoned during the catalog migration process, but the corresponding index has not been abandoned.
The catalog DB:
-Removal of the index
SQL > connect rman.
SQL > select * from user_constraints where constraint_name = "BRL_U1";
SQL > select * from user_indexes where index_name = "BRL_U1";
SQL > drop index BRL_U1;
Once it will be deposited now connect to the production database to connect to the catalog and re-synchronize... It should work like that...
RMAN target / catalog rman/password@catalog_db_name
RMAN > catalog resync;
from full resynchronization of the recovery catalog
full complete Resync
RMAN > exit
======================================
Kind regards
Firdous Shah
-
ORA-00001: unique constraint
Hi all
I use ODI 11.6 and Oracle 11 g.
When executing my interface, I get the error inserting new line below rate
ODI-1228: failed INT_TEMP_TO_MOSA (integration) task on the target of ORACLE EDGE_DEV_OWNER connection.
Caused by: java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (EDGE_DEV_OWNER. SP_MOS_PK) violated
Any ideas how to solve this problem?
Thank you
LonyCheck the separate option in the stream tab. Do not drop the I$ table. Run a group of query keycolumn in Toad cons I$ table and see whether or not duplicate records exist.
Thank you. -
How to solve the error ORA-00001 in SQL Insert?
Hi all, I need your help appreciated.
I do a plsql procedure that inserts a line according to the value of the slider, I have error oracle ORA-00001: unique constraint (constraint_name) violated.
This message may appear if a duplicate entry exists at a different level: in the RDBMS MySQL, I have the syntax IGNORES to solve this error of duplication... and in Oracle?
Thanks for your time and your advice.
Miguelitouser6317803 wrote:
How to solve the error ORA-00001 in SQL Insert?ORA-00001 means table a unique/primary key / index and you attempt to insert a row with the key value already exists in the table. I'll assume table has a primary key on COUNTRY_ID. Then modify SQL for:
SQL = "INSERT INTO COUNTRIES (COUNTRY_ID, COUNTRY_NAME, REGION_ID) SELECT"BZ","BLZ", 3 DOUBLE WHERE DOES NOT EXIST (SELECT 1 FROM COUNTRIES WHERE COUNTRY_ID ="BZ").
There is a good chance COUNTRY table also has unique key/index on COUNTRY_NAME. If so use:
SQL = "INSERT INTO COUNTRIES (COUNTRY_ID, COUNTRY_NAME, REGION_ID) SELECT"BZ","BLZ", 3 DOUBLE WHERE DOES NOT EXIST (SELECT 1 FROM COUNTRIES WHERE COUNTRY_ID = 'BZ' OR 'BLZ' = COUNTRY_NAME).
SY.
-
Insert first in the results of the empty table in ORA-00001: unique constraint
Hi all
We are running Oracle 10 g. I modified an Oracle stored procedure instead of using the cursor for loops or bulk collect for use INSERT with the SELECT statement. When I run this version, I get ORA-00001 on first insertion. ONCE the exception is thrown. I checked that the array is empty. I don't think the ORA-00001 is the real cause of the problem. I have a syntax problem I'm not aware of.
Here's the script:
Thank you for your help,CREATE OR REPLACE PROCEDURE SP_LOAD_TEST (p_rpt_month varchar2) IS --=================================================== -- define exceptions --=================================================== DUP_VAL_ON_INDEX EXCEPTION; --=================================================== -- read the USER data --=================================================== CURSOR c_get_USERS_TBL IS select DIV_CD, WRKR_USER_ID, RPT_MONTH from USERS_TBL WHERE RPT_MONTH = P_RPT_MONTH ORDER BY DIV_CD, WRKR_USER_ID; --=================================================== -- get the location name from the TLOC_DMSN table --=================================================== CURSOR c_wrkr_loc_name ( p_wrkr_user_id varchar2) IS select WRKR_LOC from .TLOC_DMSN WHERE TRIM(wrkr_user_id) = TRIM(p_wrkr_user_id); --=================================================== -- define a place holder for each row fetched from each cursor --=================================================== c_get_USERS_TBL_row c_get_USERS_TBL%ROWTYPE; --=================================================== -- define variables --=================================================== v_elapsed_time VARCHAR2(50); v_elapsed_time_hh FLOAT; v_elapsed_time_mi FLOAT; v_elapsed_time_ss FLOAT; v_mod_ss FLOAT; v_mod_mi FLOAT; v_elapsed_time_minus_ss FLOAT; v_div_cd1 USERS_TBL.div_cd%TYPE; v_wrkr_user_id1 USERS_TBL.wrkr_user_id%TYPE; v_rpt_month1 USERS_TBL.wrkr_user_id%TYPE; v_div_cd2 USERS_TBL.div_cd%TYPE; v_wrkr_user_id2 USERS_TBL.wrkr_user_id%TYPE; V_rpt_month2 USERS_TBL.rpt_month%TYPE; v_usage_hour FACT_TBL.usage_hour%TYPE; v_bytes_sent FACT_TBL.bytes_sent%TYPE; v_bytes_rcvd FACT_TBL.bytes_rcvd%TYPE; v_total_bytes FACT_TBL.total_bytes%TYPE; v_div_nm FACT_TBL.div_nm%TYPE; v_wrkr_loc .TLOC_DMSN.WRKR_LOC%TYPE; v_wrkr_dspl_nm FACT_TBL.wrkr_dspl_nm%TYPE; v_wrkr_ph FACT_TBL.wrkr_ph%TYPE; v_url FACT_TBL.url%TYPE; v_divcd_userid VARCHAR2(12); v_prev_divcd_userid VARCHAR2(12); v_prev_div_cd USERS_TBL.div_cd%TYPE; v_prev_wrkr_user_id FACT_TBL.wrkr_user_id%TYPE; v_date_id NUMBER(10); v_user CHAR(8); v_seq_id NUMBER; v_insert_counter NUMBER; v_mmyyyy VARCHAR2(6); v_mm VARCHAR2(2); BEGIN --=================================================== -- initialize variables --=================================================== v_div_cd1 := ' '; v_prev_div_cd := ' '; v_wrkr_user_id1 := ' '; v_wrkr_loc := ' '; v_rpt_month1 := ' '; v_divcd_userid := ' '; v_prev_divcd_userid := ' '; v_prev_wrkr_user_id := ' '; v_insert_counter := 0; v_seq_id := 0; v_mmyyyy := ' '; --=================================================== -- build run month in mmyyyy format before writing to TLOAD_LOG table --=================================================== CASE WHEN UPPER(SUBSTR(p_rpt_month,1,INSTRB(p_rpt_month,'-',1,1)-1)) = 'JANUARY' THEN v_mm := '01'; WHEN UPPER(SUBSTR(p_rpt_month,1,INSTRB(p_rpt_month,'-',1,1)-1)) = 'FEBRUARY' THEN v_mm := '02'; WHEN UPPER(SUBSTR(p_rpt_month,1,INSTRB(p_rpt_month,'-',1,1)-1)) = 'MARCH' THEN v_mm := '03'; WHEN UPPER(SUBSTR(p_rpt_month,1,INSTRB(p_rpt_month,'-',1,1)-1)) = 'APRIL' THEN v_mm := '04'; WHEN UPPER(SUBSTR(p_rpt_month,1,INSTRB(p_rpt_month,'-',1,1)-1)) = 'MAY' THEN v_mm := '05'; WHEN UPPER(SUBSTR(p_rpt_month,1,INSTRB(p_rpt_month,'-',1,1)-1)) = 'JUNE' THEN v_mm := '06'; WHEN UPPER(SUBSTR(p_rpt_month,1,INSTRB(p_rpt_month,'-',1,1)-1)) = 'JULY' THEN v_mm := '07'; WHEN UPPER(SUBSTR(p_rpt_month,1,INSTRB(p_rpt_month,'-',1,1)-1)) = 'AUGUST' THEN v_mm := '08'; WHEN UPPER(SUBSTR(p_rpt_month,1,INSTRB(p_rpt_month,'-',1,1)-1)) = 'SEPTEMBER' THEN v_mm := '09'; WHEN UPPER(SUBSTR(p_rpt_month,1,INSTRB(p_rpt_month,'-',1,1)-1)) = 'OCTOBER' THEN v_mm := '10'; WHEN UPPER(SUBSTR(p_rpt_month,1,INSTRB(p_rpt_month,'-',1,1)-1)) = 'NOVEMBER' THEN v_mm := '11'; WHEN UPPER(SUBSTR(p_rpt_month,1,INSTRB(p_rpt_month,'-',1,1)-1)) = 'DECEMBER' THEN v_mm := '12'; END CASE; v_mmyyyy := v_mm||substr(p_rpt_month,INSTRB(p_rpt_month,'-',1,1)+1,4); --=================================================== -- get the name of user running this procedure --=================================================== v_user := ' '; select user into v_user from dual; --=================================================== -- get date id for the current date --=================================================== v_date_id := 0; select date_id into v_date_id from .dwtime5 where DWDATE = trunc(sysdate); --=================================================== -- read each ROW IN the users TABLE --=================================================== -- Open the cursor and intialize the active set Open c_get_USERS_TBL; -- Retrieve the first row, to setup for the WHILE loop FETCH c_get_USERS_TBL into c_get_USERS_TBL_row; -- Continue looping while there are more rows to fetch WHILE c_get_USERS_TBL%FOUND LOOP v_div_cd1 := c_get_USERS_TBL_row.div_cd; v_wrkr_user_id1 := c_get_USERS_TBL_row.wrkr_user_id; v_rpt_month1 := c_get_USERS_TBL_row.rpt_month; CASE WHEN v_div_cd1 <> v_prev_div_cd THEN v_prev_divcd_userid := v_divcd_userid; v_divcd_userid := v_div_cd1||v_wrkr_user_id1; WHEN v_wrkr_user_id1 <> v_prev_wrkr_user_id THEN v_prev_divcd_userid := v_prev_div_cd||v_prev_wrkr_user_id; v_divcd_userid := v_div_cd1||v_wrkr_user_id1; END CASE; Open c_wrkr_loc_name(v_wrkr_user_id1); Fetch c_wrkr_loc_name INTO v_wrkr_loc; IF c_wrkr_loc_name%NOTFOUND THEN v_wrkr_loc := NULL; END IF; Close c_wrkr_loc_name ; v_seq_id := 0; select SEQ_USER_ID.nextval into v_seq_id from dual; INSERT INTO DETAIL_TBL_TEST(DETAIL_PK_ID, DIVCD_USERID, WRKR_USER_ID, WRKR_DSPL_NM, RPT_MONTH, USAGE_HOUR, DIV_CD, DIV_NM, WRKR_LOC, BYTES_RCVD, BYTES_SENT, TOTAL_BYTES, WRKR_PH, URL, CREATE_DT, CREATE_USER, CREATE_PGM, UPDATE_DT, UPDATE_USER, UPDATE_PGM ) SELECT v_seq_id, v_divcd_userid, wrkr_user_id, wrkr_dspl_nm, rpt_month, usage_hour, div_cd, div_nm, v_wrkr_loc, bytes_rcvd, bytes_sent, total_bytes, wrkr_ph, url, SYSDATE, v_user, 'SP_LOAD_DETAIL_TBL', SYSDATE, v_user, 'SP_LOAD_DETAIL_TBL' FROM FACT_TBL, DUAL WHERE DIV_CD = v_div_cd1 AND TRIM(wrkr_user_id) = TRIM(v_wrkr_user_id1) AND rpt_month = v_rpt_month1 ORDER BY DIV_CD, WRKR_USER_ID; v_insert_counter := v_insert_counter + 1; IF v_insert_counter >= 500 THEN -- commit changes COMMIT; v_insert_counter := 0; END IF; FETCH c_get_USERS_TBL into c_get_USERS_TBL_row; END LOOP; Close c_get_USERS_TBL; --=================================================== -- final commit --=================================================== COMMIT; EXCEPTION WHEN DUP_VAL_ON_INDEX THEN DBMS_OUTPUT.PUT_LINE('Attempting to insert a row that already exists!!!'); WHEN OTHERS THEN RAISE; --END; --=================================================== -- procedure ended. --=================================================== END;
SeyedHello
I guess that the error you receive notice when you were in that sequence was ORA-02287: unauthorized by sequence number. This is because you had the ORDER BY clause in there. If you get rid of it, you can just use the sequence number in the insert without the need first to select it...
With ORDER BY
XXXX> insert 2 into 3 dt_t1 4 SELECT 5 dt_seq.NEXTVAL, 6 SYSDATE 7 FROM 8 dual 9 CONNECT BY LEVEL 10 <=10 11 ORDER BY 12 1 13 / dt_seq.NEXTVAL, * ERROR at line 5: ORA-02287: sequence number not allowed here
No ORDER OF
XXXX> insert 2 into 3 dt_t1 4 SELECT 5 dt_seq.NEXTVAL, 6 SYSDATE 7 FROM 8 dual 9 CONNECT BY LEVEL 10 <=10 11 / 10 rows created.
Of course, I guess you want a new id for each row, as seems to be the name of the primary key column.
HTH
David
Published by: Bravid on December 19, 2011 16:07
Published by: Bravid on December 19, 2011 16:08
-
ORA-00001: unique constraint (GML. PO_ORDR_DTL_U1)
Hello
I have this error after I start the synchronization of joint purchase OPM. Help, please.
Thank you very much
Kind regards
peopsquik$ oerr ora 00001 00001, 00000, "unique constraint (%s.%s) violated" // *Cause: An UPDATE or INSERT statement attempted to insert a duplicate key. // For Trusted Oracle configured in DBMS MAC mode, you may see // this message if a duplicate entry exists at a different level. // *Action: Either remove the unique restriction or do not insert the key. $
-
icxr12mi. SQL fails on ORA-00001
Dear all,
When applying patch 6678700 upgrade TO 11.5.10.2 to 12.1.1, he failed on icxr12mi.sql and showed more error:
sqlplus s APPS / * @/erpapfs/erpprod/apps/apps_st/appl/icx/12.0.0/patch/115/sql/icxr12mi.sql & un_inv & 4 28 batchsize
DECLARE
*
ERROR on line 1:
ORA-20000: icxr12mi.sql (1700): ORA-00001: unique constraint
(ICX. ICX_CAT_ITEMS_CTX_HDRS_TLP_PK) violated
ORA-06512: at line 215
Help!
Thank you
Jackie
Published by: Jackie Han on July 6, 2011 02:12Hello
Pls solution provided below MOS check;
Spend 11.5.10 at 12.1 failed on ICXR12MI. Constraint Unique SQL [ID 1050849.1]
Errors on Script icxr12mi.sql during the upgrade to version 12.1.1 - ORA-20000 ORA-01403 ORA-06512 [1114603.1 ID]
Icxr12mi.SQL get the Unique constraint error while applying the U4440000 driver. DRV [ID 464798.1]
Thank you
JD -
Hello experts
Can someone help me understand this error please
Unexpected error ORA-00001: unique constraint (LOTTO_BI. DAILY_SALES_IDX01) violated
Thank youWithout knowing your data structure or data your procedure is just a bunch without meaning of the code for me;).
But like you said you do this
text_file-online temporary_table-online primary_tableAnd like you had an error during data pumping in primary_table insert_table I suspect he got some data inserted insert_table the primary_table without remove it from the insert_table (I don't see a deletion of him anywhere).
You can find records in doubles with something like this:
http://asktom.Oracle.com/pls/Apex/f?p=100:11:0:P11_QUESTION_ID:1224636375004
(replace remove it with a select statement)Your data source would be a union with your insert_table and primary_table.
And just out of curiosity:
There are these neat external tables made for this purpose: http://download.oracle.com/docs/cd/B19306_01/server.102/b14220/schema.htm#sthref778If you could just:
-create an external table on the text file you want to load (a schedule)
-load your data into the table withinsert into your_table [...] select [...] from ext_table;
This will save you
-your temporary table
-a lot of time that you will not need to treat your text file line by line
-a lot of PL/SQL codesee you soon
-
Get ORA-00001, but couldn't find the constraint
Hi all
Here's the scenario that I am facing: I have a table which has no constraints, but when trying to insert data into this table, I get some PRA-00001. When I search this constraint, I couldn't find it.
Can you help me solve this mystery?SQL> set long 9999999 SQL> execute dbms_metadata.set_transform_param(dbms_metadata.session_transform,'SEGMENT_ATTRIBUTES', false); PL/SQL procedure successfully completed. SQL> execute dbms_metadata.set_transform_param(dbms_metadata.session_transform,'SQLTERMINATOR', TRUE); PL/SQL procedure successfully completed. SQL> ed Wrote file afiedt.buf 1 select dbms_metadata.get_ddl('TABLE','CRT_CONTRACTOR_PARTNERS_BK',user) DDL 2* from dual SQL> / CREATE TABLE "PROJ"."CRT_CONTRACTOR_PARTNERS_BK" ( "CRR_YEAR" NUMBER(4,0) DEFAULT NULL, "CRR_NO" NUMBER(6,0), "NO" NUMBER(6,0), "NAME" VARCHAR2(60), "OTE_CODE" VARCHAR2(5), "PARTNERSHIP_PERC" NUMBER(5,2), "CNT_CODE" VARCHAR2(5), "PASSPORT_NO" VARCHAR2(15), "FILTERED_NAME" VARCHAR2(60), "APP_ID" NUMBER ) ; SQL> show user USER is "PROJ" SQL> insert into "PROJ"."CRT_CONTRACTOR_PARTNERS_BK" select * from "PROJ"."CRT_CONTRACTOR_PARTNERS_BK"; insert into "PROJ"."CRT_CONTRACTOR_PARTNERS_BK" select * from "PROJ"."CRT_CONTRACTOR_PARTNERS_BK" * ERROR at line 1: ORA-00001: unique constraint (PROJ.PARTS_PK) violated SQL> SELECT constraint_name FROM all_constraints WHERE table_name='CRT_CONTRACTOR_PARTNERS_BK'; no rows selected SQL> ed Wrote file afiedt.buf 1* SELECT constraint_name FROM all_constraints WHERE constraint_name='PARTS_PK' SQL> / no rows selected SQL> select * from v$version; Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod PL/SQL Release 10.2.0.1.0 - Production CORE 10.2.0.1.0 Production TNS for 32-bit Windows: Version 10.2.0.1.0 - Production NLSRTL Version 10.2.0.1.0 - Production
Kind regards
RiazHello
You can also post the output below.
select index_name from all_indexes where table_name = 'CRT_CONTRACTOR_PARTNERS_BK'
Assumption, that you are connected to aid user proj.
Concerning
Anurag -
ORA-00001 on form insert, duplicate value
Hello!
I have 8 fields in my form. The values of 4 of them go in Table1 and Table2 others 4.
Table 1 has a composite unique constraint based on 2 columns (which are filled with the first 2 fields in my form which are the first and last name).
Table2 has no constraints.
I've manually recreated my form that was originally made with the wizard block/layout of data. So now im integration with applications I've written. I have to mention everything works fine as long as im not looking to insert a record for someone who is already in Table1.
The problem: ORA-00001 ("you tried to execute an INSERT or UPDATE statement that created a value duplicated in an area limited by a single index.") when im trying to insert a record for someone who is already in the table 1 (i.e. the name and family name combination is most unique in Table1). In Table1, I say everything is all right, because I don't want to not more than once the same person, but because of this exception ORA INSERT into Table2 also fails. How can I avoid this?
The code is also just that INSERT INTO can get so I won't post.
THX,
IulianIf I understand the problem correctly from what you say,
"So now im integration with applications I've written. The code is also just that INSERT INTO can get so I won't post. »
This means that you have two table insert statements. Wrap the first statement with the Manager of exceptions as noted below. This way nothing will be inserted into table1 when there are duplicate, but you can insert into another table.
Begin
Begin
Insert into table1 values...
Exception when DUP_VAL_ON_INDEX then
Null;
End;
Insert into table2 values...End;
I hope this works.
-
UPDATED MULTI-COLUMN ORA-00001
When I try to update the 3 columns to s_cust with s_upd_fault data I get ORA-00001: unique constraint (DaveyB.FLT_REF) violated.
I'm not sure why this is and how to fix it.
I hope you can help.
Edited by: DaveyB October 8, 2009 12:38CREATE TABLE s_upd_fault AS SELECT 11111 AS s_fault_number, 'David Bryan' AS s_full_name, 'Closed' AS s_fault_status --'' AS t_adv_notes, --'' AS t_adv_fault_status FROM DUAL UNION ALL SELECT 11112, 'James Smith', 'Open' FROM DUAL UNION ALL SELECT 11113, 'Claire Smith', 'Closed' FROM DUAL UNION ALL SELECT 11114, 'Jenny Row', 'Closed' FROM DUAL UNION ALL SELECT 11115, 'Stan Lee', 'Closed' FROM DUAL UNION ALL SELECT 11116, 'John Steves', 'Closed' FROM DUAL UNION ALL SELECT 11117, 'James James', 'Open' FROM DUAL UNION ALL SELECT 11118, 'David David', 'Open' FROM DUAL UNION ALL SELECT 11119, 'Peter Peter', 'Open' FROM DUAL ; /* TEST DATA*/ --INSERTS TODAYS DATA INTO THE TABLE INSERT INTO s_cust (s_fault_number, s_full_name, s_fault_status) ( SELECT s_fault_number, s_full_name, s_fault_status FROM s_fault ) ; /*CREATES A TABLE TEMPLATE TO STORE THE DATA*/ CREATE TABLE s_cust ( s_fault_number VARCHAR(20) CONSTRAINT flt_ref PRIMARY KEY, s_full_name VARCHAR2(15), s_fault_status VARCHAR2(10), t_adv_notes VARCHAR2(20), t_adv_fault_status VARCHAR2(30), CHECK (s_fault_status IN ('Open', 'Closed')) --VALIDATION ); --UPDATE THE COLUMNS WITH NEW DATA UPDATE s_cust SET ( s_fault_number, s_full_name, s_fault_status ) = ( SELECT s_fault_number, s_full_name, s_fault_status FROM s_upd_fault WHERE s_fault_number = '11111' )
Hello
UPDATE s_cust SET ( s_fault_number, s_full_name, s_fault_status ) = ( SELECT s_fault_number, s_full_name, s_fault_status FROM s_upd_fault WHERE s_fault_number = '11111' )
Because the above query is updated all the lines with s_fault_number as '11111', and since it is a primary key, you cannot update this value to more than one line.
I guess you could want to do that
UPDATE s_cust s_cust SET ( s_fault_number, s_full_name, s_fault_status ) = ( SELECT s_fault_number, s_full_name, s_fault_status FROM s_upd_fault suf WHERE s_cust. s_fault_number = suf.s_fault_number ) where s_fault_number = '11111'
If you want to update the entire column and then withdraw where s_fault_number = '11111'
Concerning
Anurag Tibrewal. -
Hello
My version of the database is SQL More: Release 10.2.0.4.0 - Production *.
But I am experiencing an error in my database
Sat Feb 02 15:55:09 2013
WARNING: inbound connections has expired (ORA-3136)
Sat Feb 02 15:55:46 2013
Error caught 3135 trapped in the 2PC on transaction 95.9.36937 Protocol. Cleaning.
Sat Feb 02 15:55:46 2013
Error caught 3135 trapped in the 2PC on transaction 217.30.22297 Protocol. Cleaning.
Sat Feb 02 15:55:46 2013
Error caught 3135 trapped in the 2PC on transaction 218.0.21621 Protocol. Cleaning.
Sat Feb 02 15:55:47 2013
Error caught 3135 trapped in the 2PC on transaction 61.0.73378 Protocol. Cleaning.
Sat Feb 02 15:55:47 2013
Error caught 3135 trapped in the 2PC on transaction 99.45.36824 Protocol. Cleaning.
Sat Feb 02 15:55:47 2013
Error caught 3135 trapped in the 2PC on transaction 103.3.42125 Protocol. Cleaning.
Sat Feb 02 15:55:48 2013
Error caught 3135 trapped in the 2PC on transaction 21.34.383312 Protocol. Cleaning.
Sat Feb 02 15:55:48 2013
Error caught 3135 trapped in the 2PC on transaction 162.42.25904 Protocol. Cleaning.
Sat Feb 02 15:55:49 2013
Error caught 3135 trapped in the 2PC on transaction 190.10.28842 Protocol. Cleaning.
Sat Feb 02 15:55:49 2013
Error caught 3135 trapped in the 2PC on transaction 132.7.33798 Protocol. Cleaning.
Sat Feb 02 15:55:50 2013
Error caught 3135 trapped in the 2PC on transaction 57.31.98874 Protocol. Cleaning.
Sat Feb 02 15:55:50 2013
Error caught 3135 trapped in the 2PC on transaction 116.16.30060 Protocol. Cleaning.
Sat Feb 02 15:55:51 2013
Error caught 3135 trapped in the 2PC on transaction 214.14.26429 Protocol. Cleaning.
Sat Feb 02 15:55:52 2013
Error caught 3135 trapped in the 2PC on transaction 72.23.56805 Protocol. Cleaning.
Sat Feb 02 15:55:53 2013
Error caught 3135 trapped in the 2PC on transaction 3.12.2402246 Protocol. Cleaning.
Sat Feb 02 15:56:53 2013
WARNING: inbound connections has expired (ORA-3136)
Sat Feb 02 15:57:15 2013
ARC2: warning. Wrapped sequence of journal in the name of the file archive
to set specified by %S in LOG_ARCHIVE_FORMAT length.
Sat Feb 02 15:57:15 2013
ARCH: Stopped archiving, error occurred. Will continue to retry
Sat Feb 02 15:57:15 2013
Old archive newspaper with the same name may be replaced.
Sat Feb 02 15:57:15 2013
Errors in the d:\oracle\product\10.2.0\admin\orcl\bdump\orcl_arc1_6976.trc file:
ORA-16038: log sequence 9 # 112096 can be archived
ORA-00001: unique constraint (.) has violated
Sat Feb 02 15:57:15 2013
Errors in the d:\oracle\product\10.2.0\admin\orcl\bdump\orcl_arc2_11104.trc file:
ORA-19504: cannot create the file 'I:\ARCHIVE_LOG\ARC499E66E8_12096_0707337067.001 '.
ORA-27044: cannot write the file header block
OSD-04008: WriteFile() failure, cannot write to the file
S/O-error: (OS 112) there is not enough space on the disk.
ARC2: 19504 error creating archive log file to "I:\ARCHIVE_LOG\ARC499E66E8_12096_0707337067.001".
Sat Feb 02 15:57:32 2013
ARCH: Stopped archiving, error occurred. Will continue to retry
Sat Feb 02 15:57:32 2013
Errors in the d:\oracle\product\10.2.0\admin\orcl\bdump\orcl_arc2_11104.trc file:
ORA-16014: log 9 sequence # 112096 not archived, not available destinations
ORA-00312: wire 9 1 online journal: ' G:\ORADATA\REDO09A. JOURNAL"
ORA-00312: wire 9 1 online journal: ' H:\ORADATA\REDO09B. JOURNAL"
Sat Feb 02 16:01:59 2013
Errors in the d:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_12584.trc file:
[ORA-00600: internal error code, arguments: [krbpwbsz_not_lbszXpbsz], [512], [4096] [] [] [], [],]
Sat Feb 02 16:02:03 2013
Errors in the d:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_12584.trc file:
[ORA-00600: internal error code, arguments: [krbpwbsz_not_lbszXpbsz], [512], [4096] [] [] [], [],]
Sat Feb 02 16:02:06 2013
Errors in the d:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_12584.trc file:
[ORA-00600: internal error code, arguments: [krbpwbsz_not_lbszXpbsz], [512], [4096] [] [] [], [],]
Sat Feb 02 16:02:08 2013
Errors in the d:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_12584.trc file:
[ORA-00600: internal error code, arguments: [krbpwbsz_not_lbszXpbsz], [512], [4096] [] [] [], [],]
Sat Feb 02 16:02:10 2013
Errors in the d:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_12584.trc file:
[ORA-00600: internal error code, arguments: [krbpwbsz_not_lbszXpbsz], [512], [4096] [] [] [], [],]
Sat Feb 02 16:02:13 2013
Errors in the d:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_12584.trc file:
[ORA-00600: internal error code, arguments: [krbpwbsz_not_lbszXpbsz], [512], [4096] [] [] [], [],]
Sat Feb 02 16:02:15 2013
Errors in the d:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_12584.trc file:
[ORA-00600: internal error code, arguments: [krbpwbsz_not_lbszXpbsz], [512], [4096] [] [] [], [],]
Sat Feb 02 16:02:18 2013
Errors in the d:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_12584.trc file:
[ORA-00600: internal error code, arguments: [krbpwbsz_not_lbszXpbsz], [512], [4096] [] [] [], [],]
Sat Feb 02 16:02:20 2013
Errors in the d:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_12584.trc file:
[ORA-00600: internal error code, arguments: [krbpwbsz_not_lbszXpbsz], [512], [4096] [] [] [], [],]
Sat Feb 02 16:02:32 2013
ARC3: warning. Wrapped sequence of journal in the name of the file archive
to set specified by %S in LOG_ARCHIVE_FORMAT length.
Old archive newspaper with the same name may be replaced.
Sat Feb 02 16:02:32 2013
Errors in the d:\oracle\product\10.2.0\admin\orcl\bdump\orcl_arc3_8376.trc file:
ORA-19504: cannot create the file 'I:\ARCHIVE_LOG\ARC499E66E8_12096_0707337067.001 '.
ORA-27044: cannot write the file header block
OSD-04008: WriteFile() failure, cannot write to the file
S/O-error: (OS 112) there is not enough space on the disk.
ARC3: 19504 error creating archive log file to "I:\ARCHIVE_LOG\ARC499E66E8_12096_0707337067.001".
ARCH: Stopped archiving, error occurred. Will continue to retry
Sat Feb 02 16:02:32 2013
Errors in the d:\oracle\product\10.2.0\admin\orcl\bdump\orcl_arc3_8376.trc file:
ORA-16038: log sequence 9 # 112096 can be archived
ORA-19504: cannot create the file «»
ORA-00312: wire 9 1 online journal: ' G:\ORADATA\REDO09A. JOURNAL"
ORA-00312: wire 9 1 online journal: ' H:\ORADATA\REDO09B. JOURNAL"
Sat Feb 02 16:03:32 2013
ARCH: Stopped archiving, error occurred. Will continue to retry
Sat Feb 02 16:03:32 2013
Errors in the d:\oracle\product\10.2.0\admin\orcl\bdump\orcl_arc0_8808.trc file:
ORA-16014: log 9 sequence # 112096 not archived, not available destinations
ORA-00312: wire 9 1 online journal: ' G:\ORADATA\REDO09A. JOURNAL"
ORA-00312: wire 9 1 online journal: ' H:\ORADATA\REDO09B. JOURNAL"
Sat Feb 02 16:05:03 2013
Errors in the d:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_8816.trc file:
[ORA-00600: internal error code, arguments: [krbpwbsz_not_lbszXpbsz], [512], [4096] [] [] [], [],]
Sat Feb 02 16:05:08 2013
Errors in the d:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_8816.trc file:
[ORA-00600: internal error code, arguments: [krbpwbsz_not_lbszXpbsz], [512], [4096] [] [] [], [],]
Sat Feb 02 16:05:10 2013
Errors in the d:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_8816.trc file:
[ORA-00600: internal error code, arguments: [krbpwbsz_not_lbszXpbsz], [512], [4096] [] [] [], [],]
Sat Feb 02 16:05:13 2013
Errors in the d:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_8816.trc file:
[ORA-00600: internal error code, arguments: [krbpwbsz_not_lbszXpbsz], [512], [4096] [] [] [], [],]
Sat Feb 02 16:05:15 2013
Errors in the d:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_8816.trc file:
[ORA-00600: internal error code, arguments: [krbpwbsz_not_lbszXpbsz], [512], [4096] [] [] [], [],]
Sat Feb 02 16:05:42 2013
Errors in the d:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_8816.trc file:
[ORA-00600: internal error code, arguments: [krbpwbsz_not_lbszXpbsz], [512], [4096] [] [] [], [],]
Sat Feb 02 16:05:45 2013
Errors in the d:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_8816.trc file:
[ORA-00600: internal error code, arguments: [krbpwbsz_not_lbszXpbsz], [512], [4096] [] [] [], [],]
Sat Feb 02 16:05:47 2013
Errors in the d:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_8816.trc file:
[ORA-00600: internal error code, arguments: [krbpwbsz_not_lbszXpbsz], [512], [4096] [] [] [], [],]
Sat Feb 02 16:05:49 2013
Errors in the d:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_8816.trc file:
[ORA-00600: internal error code, arguments: [krbpwbsz_not_lbszXpbsz], [512], [4096] [] [] [], [],]
Sat Feb 02 16:08:32 2013
Arc1: warning. Wrapped sequence of journal in the name of the file archive
to set specified by %S in LOG_ARCHIVE_FORMAT length.
Old archive newspaper with the same name may be replaced.
Sat Feb 02 16:08:32 2013
Errors in the d:\oracle\product\10.2.0\admin\orcl\bdump\orcl_arc1_6976.trc file:
ORA-19504: cannot create the file 'I:\ARCHIVE_LOG\ARC499E66E8_12096_0707337067.001 '.
ORA-27044: cannot write the file header block
OSD-04008: WriteFile() failure, cannot write to the file
S/O-error: (OS 112) there is not enough space on the disk.
Arc1: 19504 error creating archive log file to "I:\ARCHIVE_LOG\ARC499E66E8_12096_0707337067.001".
ARCH: Stopped archiving, error occurred. Will continue to retry
Sat Feb 02 16:08:32 2013
Errors in the d:\oracle\product\10.2.0\admin\orcl\bdump\orcl_arc1_6976.trc file:
ORA-16038: log sequence 9 # 112096 can be archived
ORA-19504: cannot create the file «»
ORA-00312: wire 9 1 online journal: ' G:\ORADATA\REDO09A. JOURNAL"
ORA-00312: wire 9 1 online journal: ' H:\ORADATA\REDO09B. JOURNAL"
Sat Feb 02 16:08:41 2013
WARNING: inbound connections has expired (ORA-3136)
Sat Feb 02 16:09:32 2013
ARCH: Stopped archiving, error occurred. Will continue to retry
Sat Feb 02 16:09:32 2013
Errors in the d:\oracle\product\10.2.0\admin\orcl\bdump\orcl_arc2_11104.trc file:
ORA-16014: log 9 sequence # 112096 not archived, not available destinations
ORA-00312: wire 9 1 online journal: ' G:\ORADATA\REDO09A. JOURNAL"
ORA-00312: wire 9 1 online journal: ' H:\ORADATA\REDO09B. JOURNAL"
Sat Feb 02 16:14:11 2013
Error caught 3135 trapped in the 2PC on transaction 58.18.82800 Protocol. Cleaning.
Sat Feb 02 16:14:11 2013
Error caught 3135 trapped in the 2PC on transaction 37.38.128575 Protocol. Cleaning.
Sat Feb 02 16:14:12 2013
Error caught 3135 trapped in the 2PC on transaction 233.38.21737 Protocol. Cleaning.
Sat Feb 02 16:14:12 2013
Error caught 3135 trapped in the 2PC on transaction 60.15.83540 Protocol. Cleaning.
Sat Feb 02 16:14:12 2013
WARNING: inbound connections has expired (ORA-3136)
Sat Feb 02 16:14:13 2013
Error caught 3135 trapped in the 2PC on transaction 203.9.20007 Protocol. Cleaning.
Sat Feb 02 16:14:14 2013
Error caught 3135 trapped in the 2PC on transaction 31.36.132668 Protocol. Cleaning.
Sat Feb 02 16:14:32 2013
ARC3: warning. Wrapped sequence of journal in the name of the file archive
to set specified by %S in LOG_ARCHIVE_FORMAT length.
Old archive newspaper with the same name may be replaced.
kcrrdmx: archiving successful previously failed ORL
Archiver released errors process. Is more interrupted
Sat Feb 02 16:14:39 2013
Arc0: caveat. Wrapped sequence of journal in the name of the file archive
to set specified by %S in LOG_ARCHIVE_FORMAT length.
Old archive newspaper with the same name may be replaced.
Sat Feb 02 16:14:40 2013
Battery error returned to the user:
Sat Feb 02 16:14:40 2013
Battery error returned to the user:
ORA-03135: connection lost contact
Sat Feb 02 16:14:40 2013
Sat Feb 02 16:14:43 2013
Battery error returned to the user:
ORA-03135: connection lost contact
ORA-03135: connection lost contact
Sat Feb 02 16:14:44 2013
Battery error returned to the user:
Sat Feb 02 16:14:44 2013
Battery error returned to the user:
ORA-03135: connection lost contact
ORA-03135: connection lost contact
Sat Feb 02 16:14:45 2013
Thread 1 Advanced to record the sequence 112099 (switch LGWR)
Sat Feb 02 16:14:45 2013
Battery error returned to the user:
Sat Feb 02 16:14:45 2013
Currently journal # 9 seq # 112099 mem # 0: G:\ORADATA\REDO09A. JOURNAL
Currently journal # 9 seq # 112099 mem # 1: H:\ORADATA\REDO09B. JOURNAL
Sat Feb 02 16:14:46 2013
Battery error returned to the user:
ORA-03135: connection lost contact
ORA-03135: connection lost contact
Sat Feb 02 16:14:47 2013
Battery error returned to the user:
Sat Feb 02 16:14:47 2013
Battery error returned to the user:
ORA-03135: connection lost contact
ORA-03135: connection lost contact
Sat Feb 02 16:14:48 2013
Battery error returned to the user:
ORA-03135: connection lost contact
Sat Feb 02 16:14:49 2013
Battery error returned to the user:
Sat Feb 02 16:14:49 2013
Battery error returned to the user:
ORA-03135: connection lost contact
ORA-03135: connection lost contact
ORA-03135: connection lost contact
ORA-03135: connection lost contact
Sat Feb 02 16:21:43 2013
Sat Feb 02 19:59:30 2013
ORA-01555 caused by the following SQL statement (SQL ID: f3udhzjsjkyrg, query term s = 1359815369, SCN: 0x0001.86058adf):
Sat Feb 02 19:59:30 2013
SELECT * FROM RELATIONAL ("ORISSA_TRANSACTION". "BUYER_BIOMETRICS_TBL") "
Sat Feb 02 20:09:35 2013
Thread 1 Advanced to record the sequence 112124 (switch LGWR)
Currently journal # 10, seq # 112124 mem # 0: G:\ORADATA\REDO10A. JOURNAL
Currently journal # 10, seq # 112124 member # 1: H:\ORADATA\REDO10B. JOURNAL
Sat Feb 02 20:09:35 2013
ARC2: warning. Wrapped sequence of journal in the name of the file archive
to set specified by %S in LOG_ARCHIVE_FORMAT length.
Old archive newspaper with the same name may be replaced.
Sat Feb 02 20:26:45 2013
*************************************************************
Impossible to allocate the newspaper flashback to 1946 blocks of
current recovery of 1073741824 bytes size area.
Retention of current database Flashback is lower than the target
due to lack of space in the flash recovery area.
Flashback will continue to use the available space, but the
the flash recovery area size must be increased to reach
the aim of retention of Flashback database
Use ALTER SYSTEM SET db_recovery_file_dest_size command
to add a space. DO NOT manually REMOVE the flashback logs
to create a space.
*************************************************************
Sat Feb 02 20:31:04 2013
The value of MAXTRANS parameter ignored (30).
kupprdp: master the DM00 process started with pid = 56, OS id = 4324
to run - SYS. KUPM$ MCP. HAND ('SYS_EXPORT_SCHEMA_29', 'ORISSA_TRANSACTION', ' KUPC$ C_1_20130202203105', ' KUPC$ S_1_20130202203105', 0);
kupprdp: work DW01 process began with worker id = 1, pid = 30, OS id = 6108
to run - SYS. WORKER OF $ MAIN. HAND ('SYS_EXPORT_SCHEMA_29', 'ORISSA_TRANSACTION');
Sat Feb 02 21:02:43 2013
*************************************************************
Impossible to allocate the newspaper flashback to 1946 blocks of
current recovery of 1073741824 bytes size area.
Retention of current database Flashback is lower than the target
due to lack of space in the flash recovery area.
Flashback will continue to use the available space, but the
the flash recovery area size must be increased to reach
the aim of retention of Flashback database
Use ALTER SYSTEM SET db_recovery_file_dest_size command
to add a space. DO NOT manually REMOVE the flashback logs
to create a space.
*************************************************************
Sun Feb 03 00:12:12 2013
Thread 1 Advanced to record the sequence 112144 (switch LGWR)
Currently journal # 9 seq # 112144 mem # 0: G:\ORADATA\REDO09A. JOURNAL
Currently journal # 9 seq # 112144 member # 1: H:\ORADATA\REDO09B. JOURNAL
Sun Feb 03 00:12:12 2013
ARC2: warning. Wrapped sequence of journal in the name of the file archive
to set specified by %S in LOG_ARCHIVE_FORMAT length.
Old archive newspaper with the same name may be replaced.
Sun Feb 03 00:12:34 2013
Thread 1 cannot allot of new newspapers, sequence 112145
Checkpoint is not complete
Currently journal # 9 seq # 112144 mem # 0: G:\ORADATA\REDO09A. JOURNAL
Currently journal # 9 seq # 112144 member # 1: H:\ORADATA\REDO09B. JOURNAL
Sun Feb 03 00:12:36 2013
Thread 1 Advanced to record the sequence 112145 (switch LGWR)
Currently journal # 10 seq # 112145 mem # 0: G:\ORADATA\REDO10A. JOURNAL
Currently journal # 10 seq # 112145 mem # 1: H:\ORADATA\REDO10B. JOURNAL
Sun Feb 03 00:12:36 2013
ARC3: warning. Wrapped sequence of journal in the name of the file archive
to set specified by %S in LOG_ARCHIVE_FORMAT length.
Old archive newspaper with the same name may be replaced.
Sun Feb 03 00:30:02 2013
*************************************************************
Impossible to allocate the newspaper flashback to 1946 blocks of
current recovery of 1073741824 bytes size area.
Retention of current database Flashback is lower than the target
due to lack of space in the flash recovery area.
Flashback will continue to use the available space, but the
the flash recovery area size must be increased to reach
the aim of retention of Flashback database
Use ALTER SYSTEM SET db_recovery_file_dest_size command
to add a space. DO NOT manually REMOVE the flashback logs
to create a space.
*************************************************************
Sun Feb 03 00:30:47 2013
Thread 1 Advanced to record the sequence 112146 (switch LGWR)
Currently Journal # 8 seq # 112146 mem # 0: G:\ORADATA\REDO08A. JOURNAL
Currently Journal # 8 seq # 112146 member # 1: H:\ORADATA\REDO08B. JOURNAL
Sun Feb 03 00:30:47 2013
Arc0: caveat. Wrapped sequence of journal in the name of the file archive
to set specified by %S in LOG_ARCHIVE_FORMAT length.
Old archive newspaper with the same name may be replaced.
Sun Feb 03 00:37:55 2013
Sun Feb 03 02:12:39 2013
From control autobackup
Sun Feb 03 02:13:26 2013
Errors in the d:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_6744.trc file:
ORA-19815: WARNING: 5368709120 bytes db_recovery_file_dest_size is 100.00% used and has 0 bytes remaining available.
Sun Feb 03 02:13:26 2013
************************************************************************
You have choice to free up space of the flash recovery area:
1 consider changing STRATEGY OF RETENTION of RMAN. If you are using Data Guard
then consider changing POLICY of DELETE ARCHIVELOG RMAN.
2 back up files on a tertiary device such as a tape with RMAN
SAFEGUARDING RECOVERY AREA command.
3. Add space drive and increase the db_recovery_file_dest_size setting to
reflect the new space.
4 remove the unnecessary files using the RMAN DELETE command. If a service
the system control has been used to remove the files, and then use the RMAN DUPLICATION and
Commands DELETE has EXPIRED.
************************************************************************
Automatic backup failed with the following error
ORA-19583: conversation interrupted due to error
ORA-19809: limit exceeded for file recovery
ORA-19804: cannot recover disk 34193408 bytes limit 5368709120 space
Sun 03 Feb 09:32:49 2013
*************************************************************
Impossible to allocate the newspaper flashback to 1946 blocks of
current recovery of 1073741824 bytes size area.
Retention of current database Flashback is lower than the target
due to lack of space in the flash recovery area.
Flashback will continue to use the available space, but the
the flash recovery area size must be increased to reach
the aim of retention of Flashback database
Use ALTER SYSTEM SET db_recovery_file_dest_size command
to add a space. DO NOT manually REMOVE the flashback logs
to create a space.
*************************************************************
Sun Feb 03 10:09:35 2013
*************************************************************
Impossible to allocate the newspaper flashback to 1946 blocks of
current recovery of 1073741824 bytes size area.
Retention of current database Flashback is lower than the target
due to lack of space in the flash recovery area.
Flashback will continue to use the available space, but the
the flash recovery area size must be increased to reach
the aim of retention of Flashback database
Use ALTER SYSTEM SET db_recovery_file_dest_size command
to add a space. DO NOT manually REMOVE the flashback logs
to create a space.
*************************************************************
Sun Feb 03 10:34:44 2013
Thread 1 Advanced to record the sequence 112171 (switch LGWR)
Currently journal # 9 seq # 112171 mem # 0: G:\ORADATA\REDO09A. JOURNAL
Currently journal # 9 seq # 112171 mem # 1: H:\ORADATA\REDO09B. JOURNAL
Sun Feb 03 10:34:44 2013
Arc1: warning. Wrapped sequence of journal in the name of the file archive
to set specified by %S in LOG_ARCHIVE_FORMAT length.
Old archive newspaper with the same name may be replaced.
Sun Feb 03 10:35:10 2013
Thread 1 Advanced to record the sequence 112172 (switch LGWR)
Currently journal # 10, seq # 112172 mem # 0: G:\ORADATA\REDO10A. JOURNAL
Currently journal # 10, seq # 112172 member # 1: H:\ORADATA\REDO10B. JOURNAL
Sun Feb 03 10:35:10 2013
ARC2: warning. Wrapped sequence of journal in the name of the file archive
to set specified by %S in LOG_ARCHIVE_FORMAT length.
Old archive newspaper with the same name may be replaced.
Sun Feb 03 10:35:40 2013
Thread 1 Advanced to record the sequence 112173 (switch LGWR)
Currently Journal # 8 seq # 112173 mem # 0: G:\ORADATA\REDO08A. JOURNAL
Currently Journal # 8 seq # 112173 mem # 1: H:\ORADATA\REDO08B. JOURNAL
Sun Feb 03 10:35:40 2013
ARC3: warning. Wrapped sequence of journal in the name of the file archive
to set specified by %S in LOG_ARCHIVE_FORMAT length.
Old archive newspaper with the same name may be replaced.
Sun Feb 03 10:36:11 2013
Thread 1 Advanced to record the sequence 112174 (switch LGWR)
Currently journal # 9 seq # 112174 mem # 0: G:\ORADATA\REDO09A. JOURNAL
Currently journal # 9 seq # 112174 mem # 1: H:\ORADATA\REDO09B. JOURNAL
Sun Feb 03 10:36:11 2013
Arc0: caveat. Wrapped sequence of journal in the name of the file archive
to set specified by %S in LOG_ARCHIVE_FORMAT length.
Old archive newspaper with the same name may be replaced.
Sun Feb 03 10:36:43 2013
Thread 1 Advanced to record the sequence 112175 (switch LGWR)
Currently journal # 10 seq # 112175 mem # 0: G:\ORADATA\REDO10A. JOURNAL
Currently journal # 10 seq # 112175 mem # 1: H:\ORADATA\REDO10B. JOURNAL
Sun Feb 03 10:36:43 2013
Arc1: warning. Wrapped sequence of journal in the name of the file archive
to set specified by %S in LOG_ARCHIVE_FORMAT length.
Old archive newspaper with the same name may be replaced.
Sun Feb 03 10:37:17 2013
Thread 1 Advanced to record the sequence 112176 (switch LGWR)
Currently Journal # 8 seq # 112176 mem # 0: G:\ORADATA\REDO08A. JOURNAL
Currently Journal # 8 seq # 112176 mem # 1: H:\ORADATA\REDO08B. JOURNAL
Sun Feb 03 10:37:17 2013
ARC2: warning. Wrapped sequence of journal in the name of the file archive
to set specified by %S in LOG_ARCHIVE_FORMAT length.
Old archive newspaper with the same name may be replaced.
Sun Feb 03 12:22:12 2013
*************************************************************
Impossible to allocate the newspaper flashback to 1946 blocks of
current recovery of 1073741824 bytes size area.
Retention of current database Flashback is lower than the target
due to lack of space in the flash recovery area.
Flashback will continue to use the available space, but the
the flash recovery area size must be increased to reach
the aim of retention of Flashback database
Use ALTER SYSTEM SET db_recovery_file_dest_size command
to add a space. DO NOT manually REMOVE the flashback logs
to create a space.
*************************************************************
Sun Feb 03 12:54:02 2013
*************************************************************
Impossible to allocate the newspaper flashback to 1946 blocks of
current recovery of 1073741824 bytes size area.
Retention of current database Flashback is lower than the target
due to lack of space in the flash recovery area.
Flashback will continue to use the available space, but the
the flash recovery area size must be increased to reach
the aim of retention of Flashback database
Use ALTER SYSTEM SET db_recovery_file_dest_size command
to add a space. DO NOT manually REMOVE the flashback logs
to create a space.
*************************************************************
Sun Feb 03 14:10:46 2013
Thread 1 Advanced to record the sequence 112178 (switch LGWR)
Currently journal # 10, seq # 112178 mem # 0: G:\ORADATA\REDO10A. JOURNAL
Currently journal # 10, seq # 112178 member # 1: H:\ORADATA\REDO10B. JOURNAL
Sun Feb 03 14:10:46 2013
Arc0: caveat. Wrapped sequence of journal in the name of the file archive
to set specified by %S in LOG_ARCHIVE_FORMAT length.
Old archive newspaper with the same name may be replaced.
Sun Feb 03 16:12:17 2013
*************************************************************
Impossible to allocate the newspaper flashback to 1946 blocks of
current recovery of 1073741824 bytes size area.
Retention of current database Flashback is lower than the target
due to lack of space in the flash recovery area.
Flashback will continue to use the available space, but the
the flash recovery area size must be increased to reach
the aim of retention of Flashback database
Use ALTER SYSTEM SET db_recovery_file_dest_size command
to add a space. DO NOT manually REMOVE the flashback logs
to create a space.
*************************************************************
Sun Feb 03 16:33:32 2013
Thread 1 Advanced to record the sequence 112179 (switch LGWR)
Currently Journal # 8 seq # 112179 mem # 0: G:\ORADATA\REDO08A. JOURNAL
Currently Journal # 8 seq # 112179 mem # 1: H:\ORADATA\REDO08B. JOURNAL
Sun Feb 03 16:33:32 2013
Arc1: warning. Wrapped sequence of journal in the name of the file archive
to set specified by %S in LOG_ARCHIVE_FORMAT length.
Old archive newspaper with the same name may be replaced.
Sun Feb 03 20:31 2013
The value of MAXTRANS parameter ignored (30).
kupprdp: master the DM00 process started with pid = 52, OS id = 8204
to run - SYS. KUPM$ MCP. HAND ('SYS_EXPORT_SCHEMA_29', 'ORISSA_TRANSACTION', ' KUPC$ C_1_20130203203100', ' KUPC$ S_1_20130203203100', 0);
kupprdp: work DW01 process began with worker id = 1, pid = 39, OS id = 12420
to run - SYS. WORKER OF $ MAIN. HAND ('SYS_EXPORT_SCHEMA_29', 'ORISSA_TRANSACTION');
Sun Feb 03 20:50:07 2013
I increase my db_recovery_file_dest_size but it is again complete in 2 days.
We ensure configured DB but now there is a problem in standby mode so I did
LOG_ARCHIVE_DEST_STATE_2 string DAVID
The following parameters are for sleep...
db_create_online_log_dest_1 string
db_create_online_log_dest_2 string
db_create_online_log_dest_3 string
db_create_online_log_dest_4 string
db_create_online_log_dest_5 string
log_archive_config string DG_CONFIG = (orcl, stdby)
Log_archive_dest chain
Log_archive_dest_1 string LOCATION = I: \archive_log VALID_
FOR (ALL_LOGFILES, ALL_ROLES) = D
B_UNIQUE_NAME = orcl
LOG_ARCHIVE_DEST_10 string
LOG_ARCHIVE_DEST_2 SERVICE string = stdby VALID_FOR = (ONLIN
E_LOGFILES, PRIMARY_ROLE) DB_UN
IQUE_NAME = stdby
log_archive_dest_3 string
log_archive_dest_4 string
log_archive_dest_5 string
log_archive_dest_6 string
log_archive_dest_7 string
log_archive_dest_8 string
log_archive_dest_9 string
allow the chain of log_archive_dest_state_1
allow the chain of log_archive_dest_state_10
LOG_ARCHIVE_DEST_STATE_2 string DAVID
allow the chain of log_archive_dest_state_3
allow the chain of log_archive_dest_state_4
allow the chain of log_archive_dest_state_5
allow the chain of log_archive_dest_state_6
allow the chain of log_archive_dest_state_7
allow the chain of log_archive_dest_state_8
allow the chain of log_archive_dest_state_9
log_archive_duplex_dest string
log_archive_format string ARC%D_%S_%R.%T
log_archive_local_first Boolean TRUE
log_archive_max_processes integer 4
log_archive_min_succeed_dest integer 1
log_archive_start boolean FALSE
log_archive_trace integer 0
log_buffer integer 14246912
log_checkpoint_interval integer 0
log_checkpoint_timeout around 1800
log_checkpoints_to_alert boolean FALSE
log_file_name_convert chain
logmnr_max_persistent_sessions integer 1
Remote_login_passwordfile string EXCLUSIVE
Please give the solution of this problem. I can't ignore this error
Kind regards...
ASIT K. reducingfree space it on disc in particular?
-
I'm creating an application that uses the authentication of the APEX and characteristics (work) registration and forgot password forms (does not work).
My I forgot the password is public (requires authentication). The user provides the user name and a secret answer, which are validated and then provides the new password. I try to use htmldb_util.reset_pw to reset the password of the user, but it does not work.
I have a process on the new password page call a PL/SQL anonymous block that looks like this (see below), where username = P16_ITEM1 and P18_ITEM1 = new password.
BEGIN
apex_040000.htmldb_util.reset_pw (V ('P16_ITEM1'), V ('P18_ITEM1'));
END;
I don't know how to send a message of success/failure of such PL/SQL block to the APEX, but that's a separate issue, I guess.
In any case, during the trial through SQL Developer as the user with APEX_ADMINISTRATOR_ROLE, I get the following error:
ORA-20001: unauthorized access (package for the undefined security group variable).
ORA-06512: at "APEX_040000.WWV_FLOW_FND_USER_API", line 22
ORA-06512: at "APEX_040000.WWV_FLOW_FND_USER_API", line 1220
ORA-06512: at "APEX_040000.HTMLDB_UTIL", line 1253
ORA-06512: at line 8 level
I've searched previous discussions and tried different suggestions with no luck.
I'm on Oracle DB 11g XE and APEX 4.x.
Any help will be appreciated. Thank you
Alex.In any case, during the trial through SQL Developer as the user with APEX_ADMINISTRATOR_ROLE, I get the following error:
ORA-20001: unauthorized access (package for the undefined security group variable).
When executing code outside the Apex which depends on the security defined Apex group, perform the following steps before your own code:
wwv_flow_api.set_security_group_id(apex_util.find_security_group_id('YOUR_SCHEMA_NAME'));
Google "wwv_flow_api.set_security_group_id" for more details, like this blog:
http://www.easyapex.com/index.php?p=502
-Morten
http://ORA-00001.blogspot.com
-
I need help to know why we have this problem. I try an insert statement and get ORA-01536 on a table to which my user (BLF) has an unlimited quota on default tablespace of the table.
The problem is solved when I give you unlimited quota for the owner of the table (XXPCK), which was previously no quotas of any kind granted to it. Note, that it worked without error for months and now it does not work. This table has a few hundred lines added each month (not a ton of data goes). It's on Oracle 11.2.0.1.
********************
Error encountered below:
DBNAME > show user
The USER is "BLF".
DBNAME > insert into xxpck.xxpck_package_lines (package_line_id, line_num package_id, line_status, created_by, creation_date, last_updated_by, last_update_date, entity_id) values (111,10,873, 'NEW',-1, sysdate-1, sysdate, 37);
insert into xxpck.xxpck_package_lines
*+
ERROR on line 1:
ORA-01536: space quota exceeded for tablespace "INTFD".
********************
DBNAME > show user
The USER is 'SYSTEM '.
DBNAME > select MAX_BYTES, MAX_BLOCKS, nom_tablespace, BYTES, BLOCKS of dba_ts_quotas where USERNAME = "BLF";
NOM_TABLESPACE BLOCKS MAX_BLOCKS MAX_BYTES BYTES
------------------------------ ---------- ---------- ---------- ----------
INTFD 1536128 - 1 1.2584E10-1
DBNAME > @quotaupdate XXPCK INTFD UNLIMITED
old 1: change user & 1 quota & 2 3 & on
new 1: change the quota UNLIMITED on INTFD user XXPCK
Modified user.
********************
Ignore the unique constraint error below, just to note, we meet is no longer the error ORA-01536. Why is this?
DBNAME > show user
The USER is "BLF".
DBNAME > insert into xxpck.xxpck_package_lines (package_line_id, line_num package_id, line_status, created_by, creation_date, last_updated_by, last_update_date, entity_id) values (111,10,873, 'NEW',-1, sysdate-1, sysdate, 37);
insert into xxpck.xxpck_package_lines
*+
ERROR on line 1:
ORA-00001: unique constraint (XXPCK. XXPCK_PACKAGE_LINES_U1) violated
********************
We now have the value quota 0 to XXPCK see if that makes a difference.
DBNAME > @quotaupdate xxpck 0 INTFD
old 1: change user & 1 quota & 2 3 & on
new 1: change the xxpck user quota 0 on INTFD
Modified user.
********************
Is, we get the error ORA-01536 even after the owner of the quota (XXPCK) 0 table setting.
DBNAME > insert into xxpck.xxpck_package_lines (package_line_id, line_num package_id, line_status, created_by, creation_date, last_updated_by, last_update_date, entity_id) values (111,10,873, 'NEW',-1, sysdate-1, sysdate, 37);
insert into xxpck.xxpck_package_lines
*+
ERROR on line 1:
ORA-00001: unique constraint (XXPCK. XXPCK_PACKAGE_LINES_U1) violated
Published by: Aldrich on January 24, 2012 09:49That's because quotas are for the OWNERS of the objects schema, not users operating on these objects.
Because XXPCK is the owner of the table, it is the user who needs to have a quota on the tablespace that she is.
Maybe you are looking for
-
split screen iOS on iPad keyboard 10 distorts
I use the screen shared on a landscape iPAD 2 Air... Now with iOS 10 keyboard screen is all jumbled up and unusable... Does anyone else have this problem?
-
"' I want that the old" see all bookmarks "so that I can copy / paste
In my bookmark menu folders for the different categories of bookmarks and favorites that have not been categorized there. You people has changed the user interface. I want to 'see all bookmarks' before I can move the bookmarks not classified in their
-
Elitedesk 800 G2: PCI serial port (s) for Elitedesk 800 G2
I recently reinstalled Windows7 professional 32-bit, and now the following shows no driver in Device Manager: PCI serial port PCI Simple Simple Communications controller Should which driver I?
-
Acquisition of data in LabVIEW FPGA
Hello I'm working on LabVIEW FPGA where I need to acquire data from a source and take the average. One way to do that is to continue to add each new signal to the oldest f sum and then averaged. However, I would like to keep all of the incoming value
-
My report was accidentlly deleted. Can it be retrieved, if so how? I get help on how to get back my report that has been saved as a document? It was on Microsoft Word.