ORA-01747 when updating a remote table

Hi,
Here is my table :
SQL> desc infolig2.pylone_type
Nom NULL ? Type
PYL_CODE_PYLONE NOT NULL VARCHAR2(32)
OPY_CODE NOT NULL VARCHAR2(32)
NPY_CODE NOT NULL VARCHAR2(32)
PYL_TENS_CONS VARCHAR2(32)
PYL_NB_TERNE FLOAT(126)
PYL_HAUT_TOTAL FLOAT(126)
PYL_HAUT_SS_CONS FLOAT(126)
PYL_POIDS FLOAT(126)
PYL_SURFACE_SOL FLOAT(126)
PYL_SURFACE_PEINTE FLOAT(126)
PYL_DATE_CREAT NOT NULL DATE
PYL_DATE_MODIF DATE
PYL_TYPE_MODIF VARCHAR2(1)
PYL_CODE_UTIL VARCHAR2(20)
PYL_DESIGNATION VARCHAR2(50)
PYL_ETAT VARCHAR2(15)
PYL_INDICE_REV VARCHAR2(3)
I need to update it from a remote database.
So, I run the following procedure :
set serveroutput on
declare
GET_DESIGNATION VARCHAR2(10) := 'AUVERGNE';
OIP_PYL_CODE_PYLONE VARCHAR2(32) := 'TEST1';
OIP_OPY_CODE VARCHAR2(32) := 'ORIG3';
OIP_NPY_CODE VARCHAR2(32) := 'NATPYL2';
OIP_PYL_TENS_CONS VARCHAR2(32) := null;
OIP_PYL_NB_TERNE FLOAT := 1;
OIP_PYL_HAUT_TOTAL FLOAT := null;
OIP_PYL_HAUT_SS_CONS FLOAT := null;
OIP_PYL_POIDS FLOAT := null;
OIP_PYL_SURFACE_SOL FLOAT := null;
OIP_PYL_SURFACE_PEINTE FLOAT := null;
OIP_PYL_DATE_CREAT DATE := SYSDATE;
OIP_PYL_DATE_MODIF DATE := SYSDATE;
OIP_PYL_TYPE_MODIF VARCHAR2(1) := 'M';
OIP_PYL_CODE_UTIL VARCHAR2(20) := 'RTE REFERENCE';
OIP_PYL_DESIGNATION VARCHAR2(50) := 'TEST 1';
OIP_PYL_ETAT VARCHAR2(15) := 'interdit';
OIP_PYL_INDICE_REV VARCHAR2(3) := '23';
OIP_PYL_CODE_PYLONE_SUBST VARCHAR2(32) := 'CODEPYL5';
begin
execute immediate 'UPDATE infolig2.PYLONE_TYPE@'||GET_DESIGNATION||' SET
PYL_CODE_PYLONE = :1,
OPY_CODE = :2,
NPY_CODE = :3,
PYL_TENS_CONS = :4,
PYL_NB_TERNE = :5,
PYL_HAUT_TOTAL = :6,
PYL_HAUT_SS_CONS = :7,
PYL_POIDS = :8,
PYL_SURFACE_SOL = :9,
PYL_SURFACE_PEINTE = :10,
PYL_DATE_CREAT = :11,
PYL_DATE_MODIF = :12,
PYL_TYPE_MODIF = :13,
PYL_CODE_UTIL = :14,
PYL_DESIGNATION = :15,
PYL_ETAT = :16,
PYL_INDICE_REV = :17,
WHERE PYL_CODE_PYLONE = :18'
USING OIP_PYL_CODE_PYLONE,OIP_OPY_CODE,OIP_NPY_CODE,OIP_PYL_TENS_CONS,OIP_PYL_NB_TERNE,OIP_PYL_HAUT_TOTAL,OIP_PYL_HAUT_SS_CONS,OIP_PYL_POIDS,OIP_PYL_SURFACE_SOL,OIP_PYL_SURFACE_PEINTE,OIP_PYL_DATE_CREAT,OIP_PYL_DATE_MODIF,OIP_PYL_TYPE_MODIF,OIP_PYL_CODE_UTIL,OIP_PYL_DESIGNATION,
upper(translate(OIP_PYL_ETAT,'éè','ee')),OIP_PYL_INDICE_REV, OIP_PYL_CODE_PYLONE_SUBST;
exception
when others then
dbms_output.put_line('ERREUR ORACLE DETECTEE ***');
dbms_output.put_line('Message Erreur : '||SUBSTR(SQLERRM,1,245));
end;
I receive the error :
ORA-01747: invalid user.table.column, table.column, or columns specification
What is the problem ?
Regards,
Rachel

This reply was very useful for me. I have written insert scripts in the package where I had put comma after last_updated_date in the insert statement, I got the error -
ORA-01747: invalid user.table.column, table.column, or column specification . After removing the comma and adding right parenthesis it worked fine
INSERT INTO CPT_ACTIVITY_SALES (
WS_DATE,
ACTIVITY,
WS_ITEM_HEAD,
WS_FLAG,
CREATED_BY,
CREATED_DATE,
LAST_UPDATED_BY,
LAST_UPDATED_DATE,
(SELECT a.ws_date,
b.activity,
C.WS_ITEM_HEAD,
'N',
cUser ,
SYSDATE,
cUser,
SYSDATE
FROM CPT_SALES_LINES a,cpm_category b,CPM_ACTIVITY C
WHERE a.COMPANY=nCompany
AND a.SITE=ln_site
AND a.WS_DATE=ld_ws_date
AND a.SALES_HEADER_KEY=ln_Sales_header_key
and B.company=A.company
and b.category_id=a.category_id
AND C.COMPANY=A.COMPANY
AND C.ACTIVITY=B.ACTIVITY)

Similar Messages

  • Error ORA-01446 when updating a versioned table with SQLDeveloper 1.5.4

    Hi,
    I have been trying out Oracle Workspace Manager to test how versioned tables might work to our advantage. My basic testing process is:
    1. Create a table
    2. Add some data rows
    3. Version enable the table
    4. Create a workspace
    5. Goto the created workspace
    6. Update a row
    7. Commit and I get the following error
    UPDATE "COMSERV"."A_OWM_TEST" SET DESCRIPTION = 'ABCDEFGHIJzzzz' WHERE ROWID = 'AAAThNAAIAAAgwqAAY'
    One error saving changes to table "COMSERV"."A_OWM_TEST":
    Row 10: ORA-01446: cannot select ROWID from view with DISTINCT, GROUP BY, etc.
    The same update works fine from SQLPlus so my question is Does SQL developer support table versioning or have I done something wrong is setting up my versioned tables?
    Any suggestions greatly appreciated.
    Thanks
    Richard Wilkinson

    hye...
    is that any view referring to that table...
    check the code on how u create that view...
    for e.g.
    CREATE OR REPLACE VIEW testview
    (id, name)
    AS
    select * from testing;
    this also will populate that ORA-01446 error.
    just a suggestion cause i also have a similar problem on ORA-01446 and i resolve it by alter the view..
    CREATE OR REPLACE VIEW testview
    (id, name)
    AS
    select id, name from testing;
    correct me if i'm worng...i'm just a newbie..
    thank you...

  • Problem encountered when join two remote tables in a materialized view

    I'm using oracle 9.2.0.6
    1> I have two tables:
    CREATE TABLE TEST
    A VARCHAR2(100 BYTE),
    C DATE
    CREATE TABLE TEST1
    A VARCHAR2(100 BYTE),
    B TIMESTAMP
    2>. I defined a prebuild table:
    CREATE TABLE MV_TEST1
    ID1 ROWID,
    A VARCHAR2(100 BYTE),
    ID2 ROWID,
    B TIMESTAMP(6),
    C DATE
    3> I created mview logs:
    CREATE MATERIALIZED VIEW LOG ON PSI_TEST.TEST
    WITH ROWID
    INCLUDING NEW VALUES;
    CREATE MATERIALIZED VIEW LOG ON PSI_TEST.TEST1
    WITH ROWID
    INCLUDING NEW VALUES;
    4> when I create mview:
    CREATE MATERIALIZED VIEW PSI_TEST.MV_TEST1
    ON PREBUILT TABLE WITH REDUCED PRECISION
    REFRESH FAST ON DEMAND
    WITH PRIMARY KEY
    AS
    select
    test.rowid id1,
    test.a,
    test1.rowid id2,
    test1.b,
    cast(null as date) c
    from test , test1
    where test.a = test1.a(+);
    It is created successfully.
    5> problem:
    when I use remote tables to do the same thing, say test and test1 are in another instance and are connected by a dbLink, I couldn't create the mview successfully:
    CREATE MATERIALIZED VIEW PSI_TEST.MV_TEST1
    ON PREBUILT TABLE WITH REDUCED PRECISION
    REFRESH FAST ON DEMAND
    WITH PRIMARY KEY
    AS
    select
    a.rowid id1,
    a.a,
    b.rowid id2,
    b.b,
    cast(null as date) c
    from test@dbl a, test1@dbl b
    where a.a = b.a(+);
    when run above statement, I got:
    ORA-12015: cannot create a fast refresh materialized view from a complex query
    Any ideas? Or joining two table through a dblink for a mview is not allowed at all?
    Thanks in advance.

    No one has a clue?
    Message was edited by:
    lzhwxy

  • Update openquery remote table with join

    Hi All,
    I have a problem with OPENQUERY update on remote table. I've googled for days, and can't solve the problem.
    Here is the problem:
    Local server MS SQL 2005.
    Remote server: MySQL.
    The linked server is communicating through MySQL ODBC 5.1
    I created the following code for update (tried many other version too, this is the last one):
    update openquery(Remoteserver,'select products_id, products_price, products_last_modified, products_stock from products1')
    set
    products_price=A.products_price,
    products_stock=A.products_stock,
    products_last_modified=getdate()
    FROM
    (select * from vi_products_update) AS A INNER JOIN
    openquery(octopus, 'select products_id from products1')AS B
    ON A.products_id=B.products_id
    When I run the query the columns are updated with the same value, for each record. It looks the value is the first which match the criteria. Each (remote and local) table has as primary key products_id. In this example I used as result set for local a view, but I have the same result if I use a table.
    the products_last_modified column is updated in order, and if I update for e.g. the products_price with a constant that is ok too. The problem should be somewhere with join, but I can' get it where.
    THX for any help
    ab

    Hi
    Did you ever solve this problem
    I have the same issue trying to update many rown in a MySQL table from SQL2005 using the syntax below,
    UPDATE
    openquery(DEV,'select id, `desc` from todLocationGroups')
    SET [desc] = V.Destination_Group FROM
    (select * from VTM_TOD_Rate) as V inner join
    openquery(DEV,'select id, `desc` from todLocationGroups') as K
    ON K.id = V.TOD_LG_ID
    but i get this error
    OLE DB provider "MSDASQL" for linked server "KAYOTE_DEV" returned message "Row cannot be located for updating. Some values may have been changed since it was last read.".
    Msg 7343, Level 16, State 4, Line 1
    The OLE DB provider "MSDASQL" for linked server "KAYOTE_DEV" could not UPDATE table "[MSDASQL]". The rowset was using optimistic concurrency and the value of a column has been changed after the containing row was last fetched or resynchronized.

  • Getting ORA-1013 when attempting to expand tables within connections

    Getting ORA-1013 when attempting to expand tables within connections on new install of Oracle SQL developer 3.1.06.
    Any ideas?

    Hi Steve,
    The ORA-01013 usually means a timeout or, more typically on this forum, an intentional user cancellation. Searching the forum, I do not see any prior references to your exact situation. Some recommendations:
    1. SQL Developer 3.1.0.6 was an early adopter release. Upgrade to the latest and greatest: 3.2.10.09.57
    2. Review this: Re: [SQL Developer 3.0.04] Cannot Drill Down
    3. If it is a true timeout, your privileges might make a difference. If you have access to the DBA views, SQL Developer does look-ups using those and performance is better.
    So for [3], having the SELECT_CATALOG_ROLE privilege may help. I even read of one case in this forum where the poster finally discovered his database's recycle bin had an issue and the DBA needed to do some clean-up to correct the performance issue.
    Hope this helps,
    Gary
    SQL Developer Team

  • ORA-1779 when updating a view

    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

    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.

  • Forall issue when inserting on remote table

    Hi all,
    when I run this code, it works:
    forall i in 1..insCounter
    insert into table_name
    values(
    IdArray(i),
    RefererArray(i),
    UserAgentArray(i),
    LanguageArray(i));
    but when I try to do the same on a remote table(same structure):
    forall i in 1..insCounter
    insert into table_name@DBLINK
    values(
    IdArray(i),
    RefererArray(i),
    UserAgentArray(i),
    LanguageArray(i));
    all inserted values are null...
    Any idea?
    Thanks

    I've got very similar problem some months ago. After some back and forth stage I've realized that the problem was in some expressions in source query that used locally defined PL/SQL functions. It appeared that Oracle tried to execute this local functions on remote server and finalyy I've got an error
    ORA-04052: error occurred when looking up remote object <schema>.<package name>@<local server url>
    When I removed the calls to local functions everything began to work fine.
    What are exact expressions for columns in your
    select col_1,...,col_n
    from local_table
    Are there any function calls there?
    Cheers

  • ORA-02070: Error when updating an informix table through orcl view using HS

    Hello!
    I faced the following problem:
    I have a table in informix, and i want to reach this table through Oracle infromix gateway (Heterogenous Services). I succeeded to set up the gateway, and I created an Oracle view for my table in informix. It is working fine, I can query and modify data, except the following case: If I run the query (from SQL Developer) "UPDATE oracle_view SET float_field = '1.1' WHERE record_id = 1 AND float_field = '1.2'", I receive the following error:
    "SQL Error: ORA-02070: database database_link does not support TO_NUMBER in this context.
    *Cause: The remote database does not support the named capability in the context in which it is used.
    *Action: Simplify the SQL statement."
    If I modify the query as "UPDATE oracle_view SET float_field = '1.1' WHERE record_id = 1", it is running without any error messages. I found, that to_number is not supported by Oracle HS gateway, but I do not use explicitly the to_number Oracle function! But I must use the above version, because of concurrent users.
    Does anybody have an idea how I could get rid of the implicit call of to_number?
    Thanks, Gyula

    user11229789 wrote:
    Yes, float_field is a numeric-type field, which is a 8-byte FLOAT in informix. This field gets automatically FLOAT datatype in the Oracle view, and can not be modified. record_id is some integer unique id field.Well, as the float_field is numeric it makes sense that the SQL issued from Oracle treats it as numeric, so leaving out the quotes can only be the correct thing to do. If you introduce quotes then you are providing strings and the HS is having to do a convertion to numeric (hence where the TO_NUMBER would have been coming into the initial issue.
    If I try the update query without '-s you suggested, like this: "UPDATE oracle_view SET float_field = 1.1 WHERE record_id = 1 AND float_field = 1.2" , i receive the following error message:
    SQL Error: ORA-28534: "Heterogeneous Services preprocessing error"
    *Cause:    One of the things that the Heterogeneous Services can do is
    to preprocess parts of SQL statements that contain implicit
    coercions or calls to explicit coercion functions like TO_CHAR
    TO_NUMBER or TO_DATE. For example, it could convert a call to
    TO_DATE to a bind variable, pre-evaluate the TO_DATE function
    call and pass the resulting value to the non-Oracle system as
    the bind value. This behavior is controlled by some coercion
    related capabilities. If the capabilities are set incorrectly,
    the HS could encounter errors when it attempts to do the
    preprocessing. If it does then this error will be signaled.
    *Action:   The capability table settings are controlled by the agent
    vendor and can be modified by the DBA. Contact your DBA and
    agent vendor and get the correct set of capabilities installed.I can't see why the HS would be trying to do any coercion of anything except to perhaps convert the parts of the where clause to bind variables and pass the actual values in. Does it work ok without the "AND float_field = 1.2" ? If so, I'm guessing there's some configuration issue of the HS required to get it to deal with the floats.... perhaps in the capability settings as the error message "action" indicates.

  • Ora-21700 when updating xmltype column of a table

    Hello,
    Can somebody explain why the following statement gives ora-21700 (object does not exist or is market for delete):
    update translation_message
    set translationxml = XmlType(
    '<NPSREPLY DOMAIN="SWI" OBJECT="SUBSCRIBER" REQUEST="DELETE" RETURNCODE="0" RETURNTYPE="NONE" STATUS="STORED" xmlns="http://saly.bc/nps/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://saly.bc/nps/ NPS_Reply.xsd">
    <SUBREQUEST SEQUENCE="1">
    <ProfileData>
    <ACTION SUBTYPE="PSTN">DEL_CNA_FREE</ACTION>
    <DN>999999999</DN>
    <RETURNCODE>0</RETURNCODE>
    </ProfileData>
    </SUBREQUEST>
    </NPSREPLY>'
    where id = 1926938
    remark:
    when changing
    xsi:schemaLocation="http://saly.bc/nps/ NPS_Reply.xsd
    in
    xsi:schemaLocation="http://saly.bc/nps/NPS_Reply.xsd
    the select is running well.
    I will explain my problem a little bit more:
    The exact oracle error is:
    ora-21700 object does not exist or is marked for delete ORA-06512: at "SYS.XMLTYPE".
    The following peace of xml causes the problem:
    xsi:schemaLocation="http://saly.bc/nps/ NPS_Reply.xsd"
    The statement is running fine if you remove the blank after
    "/nps/ NPS_Repy". So if you use this peace of xml xsi:schemaLocation="http://saly.bc/nps/NPS_Reply.xsd", the statement works fine.
    My question: Wy is the blank not allowed in this peace of xml xsi:schemaLocation="http://saly.bc/nps/ NPS_Reply.xsd"
    The purpose of the blank is to indicate that 'NPS_Reply.xsd' will be located somewhere in "http://saly.bc/nps/". So it can be that 'NPS_Reply.xsd' is found directly under "http://saly.bc/nps/" or some levels lower. According XML standards, the blank is allowed for this purposes.
    regards, Els

    Hi,
    This schema location is only indicative and not used. The xml is generated by an other application and has to be stored in an xmltype column.
    regards, Els

  • How to avoid ORA-3113 when selecting from XMLTYPE table

    Hi,
    If I register an XML-schema, Oracle automatically creates a table xxxxxx_tab of XMLTYPE. (I use Oracle 9.2.0.1)
    When I do a DESCRIBE or a SELECT from this table I get the error: 'ORA-03113:
    end-of-file on communication channel' and my connection is dropped.
    I opened a TAR for this and Oracle says: 'It is an internal bug so cannot be viewed in metalink. This is fixed in release 10i.' (do they mean oracle DB rel 10i, or a new version of XDK?)
    I saw an example in Oracle Magazine (Jan
    2003) "Make XML Native and Relative" about Oracle 9i Rel 2 and XML. As you can see in codeListing 7, the author also does a select from such a
    table (CD331_tab): Why doesn't he have any problems?
    Is there a workaround for this bug? What's the purpose of being able to automatically upload XML-data to a registered schema if you can't do a select of the data?
    Thank you!

    It appears that the XML Schema is not entirely valid. Specifically, the definition of element "DeviceCategory" has two definitions of element "Audio" appearing within a <choice> model i.e. something like :
    <element name="DeviceCategory">
    <choice>
    <sequence>
    <element name="Audio">
    </sequence>
    <sequence>
    <element name="Audio">
    </sequence>
    </choice>
    This is disallowed by XML Schema spec per. the Unique Particle Attribution Constraint. The general idea is that a XML Schema describes a determinstic content model i.e. schema processor can always unambiguosly determine the matching declaration when it encounters an element. However that's not the case with the declaration above. On encoutering "Audio", it could match either the first or the second declaration of the element. Hence the error.
    You will have to rework the schema to avoid this constraint. One mechanism could be to define complexType and their restrictions.
    - Ravi

  • Get error ORA-20505 and ORA-01403 when UPDATING record

    Hi,
    I'm running APEX 3.2.1, on Oracle XE 10.2.0.1, on Sun Ultra20 (Intel-based) running Windows Server 2003.
    I created a small, department database - to keep track of contacts, equipment, etc.
    Initially, I used a NUMBER as the PRIMARY KEY in both the CONTACTS table and EQUIPMENT tables. I created a CONTACTS interactive report and a CONTACT DETAILS form, where the EDIT button on a row in the CONTACTS report brings up the individual record to modify. Same thing for EQUIPMENT - interactive report page and form page.
    This all worked fine!
    Then, I decided to change the PRIMARY KEY for the CONTACTS table to a STRING - with CONTACT_FIRST_NAME and CONTACT_LAST_NAME as the primary key. I figured I this would prevent duplicate entries. After the change, inserts work. Updates work, IF a change is made to ANY field EXCEPT first name or last name.
    UPDATES fail - if user modifies EITHER the first name or last name - in APEX. But, update SUCCEEDS if done in SQL Developer. Obviously, I missing a subtle nuance in APEX, but I can't figure it out.
    I've included DEBUG trace and version information below.
    Thanks,
    Andy
    ORA-20505: Error in DML: p_rowid=Adam1, p_alt_rowid=CONTACT_FIRST_NAME, p_rowid2=Adam, p_alt_rowid2=CONTACT_LAST_NAME. ORA-01403: no data found
    0.02: A C C E P T: Request="SAVE"
    0.02: Metadata: Fetch application definition and shortcuts
    0.02: NLS: wwv_flow.g_flow_language_derived_from=FLOW_PRIMARY_LANGUAGE: wwv_flow.g_browser_language=en-us
    0.02: alter session set nls_language="AMERICAN"
    0.02: alter session set nls_territory="AMERICA"
    0.02: NLS: CSV charset=WE8MSWIN1252
    0.02: ...NLS: Set Decimal separator="."
    0.02: ...NLS: Set NLS Group separator=","
    0.02: ...NLS: Set date format="DD-MON-RR"
    0.02: ...Setting session time_zone to -06:00
    0.02: Setting NLS_DATE_FORMAT to application date format: DD-MON-YYYY
    0.02: ...NLS: Set date format="DD-MON-YYYY"
    0.03: Fetch session state from database
    0.03: ...Check session 1896858759858984 owner
    0.03: Setting NLS_DATE_FORMAT to application date format: DD-MON-YYYY
    0.03: ...NLS: Set date format="DD-MON-YYYY"
    0.03: ...Check for session expiration:
    0.03: ...Metadata: Fetch Page, Computation, Process, and Branch
    0.03: Session: Fetch session header information
    0.03: ...Metadata: Fetch page attributes for application 101, page 21
    0.05: ...Validate item page affinity.
    0.05: ...Validate hidden_protected items.
    0.05: ...Check authorization security schemes
    0.05: Session State: Save form items and p_arg_values
    0.05: ...Session State: Save "P21_CONTACT_FIRST_NAME" - saving same value: "Adam"
    0.06: ...Session State: Saved Item "P21_CONTACT_LAST_NAME" New Value="Adam Jr"
    0.06: ...Session State: Save "P21_CONTACT_COMPANY" - saving same value: "Atempo"
    0.06: ...Session State: Save "P21_CONTACT_JOB_TITLE" - saving same value: "Sr Sw Engr"
    0.06: ...Session State: Save "P21_CONTACT_JOB_ROLE" - saving same value: "Engineering"
    0.06: ...Session State: Save "P21_CONTACT_STATUS" - saving same value: "Active"
    0.06: ...Session State: Save "P21_CONTACT_PRODUCT" - saving same value: ""
    0.06: ...Session State: Save "P21_CONTACT_PHONE" - saving same value: "222-333-4444"
    0.06: ...Session State: Save "P21_CONTACT_MOBILE" - saving same value: ""
    0.06: ...Session State: Save "P21_CONTACT_FAX" - saving same value: ""
    0.06: ...Session State: Save "P21_CONTACT_EMAIL" - saving same value: ""
    0.06: ...Session State: Save "P21_CONTACT_STREET" - saving same value: ""
    0.06: ...Session State: Save "P21_CONTACT_CITY" - saving same value: ""
    0.06: ...Session State: Save "P21_CONTACT_STATE" - saving same value: "CO"
    0.06: ...Session State: Save "P21_CONTACT_ZIP" - saving same value: ""
    0.06: ...Session State: Save "P21_CONTACT_COUNTRY" - saving same value: "United States"
    0.06: ...Session State: Save "P21_CONTACT_NOTES" - saving same value: ""
    0.06: Processing point: ON_SUBMIT_BEFORE_COMPUTATION
    0.06: Branch point: BEFORE_COMPUTATION
    0.06: Computation point: AFTER_SUBMIT
    0.06: Tabs: Perform Branching for Tab Requests
    0.06: Branch point: BEFORE_VALIDATION
    0.06: Perform validations:
    0.08: ...Item in validation equals expression 2: P21_CONTACT_JOB_ROLE
    0.08: ...Item in validation equals expression 2: P21_CONTACT_STATUS
    0.08: ...Item Not Null Validation: P21_CONTACT_PHONE
    0.08: ...Item in validation equals expression 2: P21_CONTACT_STATE
    0.08: ...Item in validation equals expression 2: P21_CONTACT_COUNTRY
    0.08: Branch point: BEFORE_PROCESSING
    0.08: Processing point: AFTER_SUBMIT
    0.08: ...Process "Process Row of ISR_CONTACTS": DML_PROCESS_ROW (AFTER_SUBMIT) #OWNER#:ISR_CONTACTS:P21_CONTACT_FIRST_NAME:CONTACT_FIRST_NAME:P21_CONTACT_LAST_NAME:CONTACT_LAST_NAME|IU
    0.08: Show ERROR page...
    0.08: Performing rollback...
    Oracle Database 10g Express Edition Release 10.2.0.1.0 - Product
    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
    Database     
    NAME     XE
    CREATED     06/08/2010 05:22:50 PM
    RESETLOGS_TIME     07/09/2010 10:09:59 AM
    PRIOR_RESETLOGS_CHANGE#     193066
    PRIOR_RESETLOGS_TIME     06/08/2010 05:22:52 PM
    LOG_MODE     ARCHIVELOG
    CHECKPOINT_CHANGE#     4436025
    ARCHIVE_CHANGE#     4387159
    OPEN_RESETLOGS     NOT ALLOWED
    VERSION_TIME     07/09/2010 10:08:44 AM
    OPEN_MODE     READ WRITE
    PROTECTION_MODE     MAXIMUM PERFORMANCE
    PROTECTION_LEVEL     MAXIMUM PERFORMANCE
    REMOTE_ARCHIVE     ENABLED
    DATABASE_ROLE     PRIMARY
    ARCHIVELOG_CHANGE#     4458138
    SWITCHOVER_STATUS     SESSIONS ACTIVE
    DATAGUARD_BROKER     DISABLED
    GUARD_STATUS     NONE
    FORCE_LOGGING     NO
    CGI Environment     
    PLSQL_GATEWAY     WebDb
    GATEWAY_IVERSION     2
    SERVER_SOFTWARE     Oracle Embedded PL/SQL Gateway/10.2.0.1.0
    GATEWAY_INTERFACE     CGI/1.1
    SERVER_PORT     8080
    SERVER_NAME     XDB HTTP Server
    REQUEST_METHOD     GET
    QUERY_STRING     p=4500:36:1896858759858984:::::
    PATH_INFO     /f
    SCRIPT_NAME     /apex
    REMOTE_ADDR     10.135.65.180
    SERVER_PROTOCOL     HTTP/1.1
    REQUEST_PROTOCOL     tcp
    REMOTE_USER     ANONYMOUS
    HTTP_USER_AGENT     Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.19) Gecko/2010031422 Firefox/3.0.19 (.NET CLR 3.5.30729)
    HTTP_HOST     isr-si-project:8080

    Maybe because you're changing primary key...and then updating record with primary key that doesn't exist.

  • Header data is not cmg in PA30  when updating from backend tables

    Hi Friends
    Am  creating record for an employee in   table  pa0000, pa00001, pa0002   and some other infotype  but when i go to PA30
    tcode  it  shows me green tick for  all these three infotype  even in  0000 action i can click display and see second screen but
    the header data is not coming on pa30  screen  though  pa0001 table has updated with all information except changedate and username .
    Any idea  how  i can  get that header data  ?
    Regards
    Meeta

    Try to create data for one employee directly in PA30 and check the header data. If still the data is not pulling though check the screen header configuration settings.
    SPRO-> Personnel Management -> Personnel Administration -> Customizing User Interfaces -> Change Screen Header
    I hope this will resove your issue.
    all the best....

  • ORA-20001 when Updating Reporting Attributes

    I have a simple SQL report in Apex3.0 - I first created it with standard display just to get the feel of it. I went back to the Report region to change the paging and display attributes of the report -> then I click on "Apply Changes" I get the following error :-
    Report attributes updated.
    ORA-20001: Error in DML: p_rowid=1190707439217628, p_alt_rowid=ID, p_rowid2=, p_alt_rowid2=. ORA-20001: Current version of data in database has changed since user initiated update process. current checksum = "9B5D30FA7EB05EADECC08971D3DA0C73" application checksum = "0"
    ORA-20001: Error in DML: p_rowid=1190707439217628, p_alt_rowid=ID, p_rowid2=, p_alt_rowid2=. ORA-20001: Current version of data in database has changed since user initiated update process. current checksum = "9B5D30FA7EB05EADECC08971D3DA0C73" application checksum = "0"
    Return to application.
    I did not change anything to the table nor the data in the table.
    Does anyone know how to resolve ?

    HI Scott
    NO I did not use the BACK button at all.
    I tried this several times :
    I logout - then login again -
    go the page containg the sql report
    -> click on that report region
    -> click on report attribute tab
    -> make minute changes such as "Show Null Values as : <blank>" ,
    then click on apply changes > I get the same error.

  • How do I avoid ORA-01473 when querying hierarchial on tables with VPD predicates

    My question is how to circumvent what seems to be a limitation i ORACLE, if at all possible. Please read on.
    When using VPD (Virtual Private Database) predictaes on a table and performing a hierarchial query on that table I get the following error message:
    ORA-01473: cannot have subqueries in CONNECT BY CLAUSE
    My query may look like the folwing:
    SELECT FIELD
    FROM TABLE
    START WITH ID = 1
    CONNECT BY PRIOR ID = PARENT
    As my predicate contains a query in it self, I suspect that the implicit augmentation of the predicate results in a query that looks like:
    SELECT FIELD
    FROM TABLE
    START WITH ID = 1
    CONNECT BY PRIOR ID = PARENT
    AND OWNER IN (SELECT OWNER FROM TABLE2 WHERE ...)
    at least, when executing a query like the one above (with the explicit predicate) I get the identical error message.
    So my question is:
    Do you know of any way to force the predicate to augment itslef onto the WHERE-clause? I would be perfectly happy with a query that looks like:
    SELECT FIELD
    FROM TABLE
    START WITH ID = 1
    CONNECT BY PRIOR ID = PARENT
    WHERE OWNER IN (SELECT OWNER FROM TABLE2 WHERE ...)
    or do you know of any fix/patch/release to ORACLE that allows you to include subqueries in the CONNECT BY-clause and eliminates the error message?

    The WHERE clause or AND clause applies to the line directly above it. Please see the examples of valid and invalid queries below, which differ only in the placement of the WHERE or AND clause. If this is not sufficient, please provide some sample data and desired output to clarify what you need.
    -- valid:
    SQL> SELECT     empno,
      2            mgr,
      3            deptno
      4  FROM     emp
      5  WHERE     deptno IN
      6            (SELECT deptno
      7             FROM     dept
      8             WHERE     dname = 'RESEARCH')
      9  START WITH mgr = 7566
    10  CONNECT BY PRIOR empno = mgr
    11  /
         EMPNO        MGR     DEPTNO                           
          7788       7566         20                           
          7876       7788         20                           
          7902       7566         20                           
           800       7902         20                           
    -- invalid:
    SQL>
    SQL> SELECT     empno,
      2            mgr,
      3            deptno
      4  FROM     emp
      5  START WITH mgr = 7566
      6  CONNECT BY PRIOR empno = mgr
      7  WHERE     deptno IN
      8            (SELECT deptno
      9             FROM     dept
    10             WHERE     dname = 'RESEARCH')
    11  /
    WHERE      deptno IN
    ERROR at line 7:
    ORA-00933: SQL command not properly ended
    -- valid:
    SQL>
    SQL> SELECT     empno,
      2            mgr,
      3            deptno
      4  FROM     emp
      5  START WITH mgr = 7566
      6  AND     deptno IN
      7            (SELECT deptno
      8             FROM     dept
      9             WHERE     dname = 'RESEARCH')
    10  CONNECT BY PRIOR empno = mgr
    11  /
         EMPNO        MGR     DEPTNO                           
          7788       7566         20                           
          7876       7788         20                           
          7902       7566         20                           
           800       7902         20                           
    -- invalid:
    SQL>
    SQL> SELECT     empno,
      2            mgr,
      3            deptno
      4  FROM     emp
      5  START WITH mgr = 7566
      6  CONNECT BY PRIOR empno = mgr
      7  AND     deptno IN
      8            (SELECT deptno
      9             FROM     dept
    10             WHERE     dname = 'RESEARCH')
    11  /
    FROM       emp
    ERROR at line 4:
    ORA-01473: cannot have subqueries in CONNECT BY clause

  • ORA-03114 when updating or inserting

    We are testing a forms application that has been 100% generated
    through Designer6, running on version 8.1.5 database.
    In one screen there are several blocks linked to different base
    tables. If you try and update or insert into one block, the app
    crashes with the ora-03114 disconnect error. You get kicked out
    of everything.
    There are pre-update and pre-insert triggers on this block but
    the processes called therein see to run ok. I am a bit stuck on
    why this is happening..it never used to and we havent changed
    the source code! All the permissions seem to be intact.
    Any suggestions?

    Hello,
    There are some information in metalink about error linked to "_intel_fast_memcpy.A+18".
    Mainly information about bugs ;)
    I don't have any Windows Oracle database here, so I can't test, but, don't you have to CONVERT the database in order to switch from 32bits to 64bits? Did you check the Endianness problem against V$TRANSPORTABLE_PLATFORM or V$DB_TRANSPORTABLE_PLATFORM ?
    In fact I'm not sure there's a conversion phase needed.. but the 32 to 64 bits phase might be what tricks you down.
    Yoann.

Maybe you are looking for