ORA-1779 when updating a view

Question

Hi and thanks in advance !
i am facing a critical situation.
i have two schema & both are same!
the problem which i am facing is during updating a view of one i am facing above error while the same DML is issuing againt that view in other schema and that works fine.
what's the reason..
The major difference between two schema's is i hav different live and test database i migrate my access database to Oracle test database # 1.here i created a new user name deals . ok
i hav done same migration in my another database but a little difference here user deals is already available here and tables and views are also available i drop all the object but forget to purge recyclebin. now whenever i try to issue DML at this schema i am facing above error while the same tables same data and same view is available in above databae where my update statement executed properly. one more thing i like to add here i hav some unwanted trigger 'BIN$##$$%##$# bla bla bla' on different table. i haven't created that .
here is the view for your kind perusal
CREATE OR REPLACE VIEW QRYREUTER AS
SELECT FXdeals.deal_no,
cparty.name,
cparty.city,
FXdeals.brokbill,
FXdeals.deal_date,
FXdeals.mode_id
FROM FXDeals
JOIN cparty
ON FXdeals.cpcode = cparty.cpcode
WHERE ( ( (FXdeals.mode_id) = 3 ) )
Message was edited by:
Fiz Dosani

Answer 1

but i have sample scenario in other schema which replica of this schema so why i haven't got this error there
one more interesting thing when i query select * from user_updateable_columns where table name ='ABC' in Schema # 1 it return i can modify some columns.
but when issue the data dictionary view in schema # 2, where i was facing ORA-1779 , select * from user_updateable_columns where table name ='ABC' in Schema # 2 it return i can not modify any columns.
Tables name are same in both schema.
Data same in both schema.
Constraint Same in both schema.
Indexes same in both schema.
why facing error in one schema not in other.
one more interesting thing, i had faced questionable object error when importing DMP into schema # 2.