Change Notifications error "ORA-29973: unsupported query or operation."

I'm trying to use of unnecessary change with ODP.NET Notifications and get the error ORA-29973.
I use:
VS 2010. .NET framework 4, Windows 7 x 64
ODP.NET Version ODAC112011beta

Cnx As New OracleConnection("DATA SOURCE=ORCL;DBA PRIVILEGE=SYSDBA;) Dim USER ID = SYS; PASSWORD = xxx; »)
CNX. Open()
Dim cmd As New OracleCommand("select deptno from scott.emp where deptno < 20", cnx)
OracleDependency.Port = 1200
_dep = new OracleDependency (cmd)
_dep. QueryBasedNotification = True
cmd. Notification.IsNotifiedOnce = False
cmd ExecuteNonQuery()).

I give Notification of change to user sys. Strangely revokint that this right does not cause a different error message.

The following example of Oracle throws the same exception:
http://www.Oracle.com/technology/OBE/hol08/dotnet/changenotification/odpnetchg_otn.htm

What I am doing wrong?

Hello

This is unrelated to the beta version.

QBC documentation...

http://download.Oracle.com/docs/CD/B28359_01/AppDev.111/b28424/adfns_cqn.htm#CHDIEJEI
You must be logged on as a non - SYS user to create QBC records.

It will be useful,
Greg

Tags: Database

Similar Questions

Error ORA-022887 during the insert operation how to handle correctly...
Hello everyone I got an error in during the insert operation how to handle correctly?
SQL statements below.

INSERT STAFF. TRANSLATIONS (TID, SCRIPT_NAME, TAG, TR, FR, LOCAL)
VALUES ((SELECT LOCATION. SQX_TID. (NEXTVAL DOUBLE AS TID), 'TEST_TEST', 'TEST', 'TR', 'FR', 'LOCAL');

Thank you
Try this,

INSERT STAFF. TRANSLATIONS (TID, SCRIPT_NAME, TAG, TR, FR, LOCAL)
VALUES (PERSONAL. SQX_TID. NEXTVAL, 'TEST_TEST', 'TEST', 'TR', 'FR', 'LOCAL');

'CREATE JAVA' error: ORA-29506: derived from the USING clause invalid query
Hello

I created a table with the following attributes:

name varchar2 (200);
LOB_DATA blob

I loaded a java source file in the lob_data blob.

I then called the SQL:

create or replace and compile the java source named "RemoteCommand" using blob
Select lob_data from str_blob_table where name = 'RemoteCommand.java ';

and I get the error:

ORA-29506: invalid query from the USING clause
ORA-00936: lack of expression
29506 00000 - "query invalid derived from USING clause.
* Cause: The USING clause does not form a valid query.
* Action: Correct the USING clause.

If I simply copy and paste the query part of the USING clause:

Select lob_data from str_blob_table where name = 'RemoteCommand.java ';

I get a valid result in SQLDeveloper.

Any thoughts on what is happening here?

A few notes:
1. it is a 8i database.
2. it works very well on a 9i database, but according to the SQL reference for 8i, it should work as well.

Thank you
Brent
Try to delete "select" in the USING clause, that is to say change the SELECT BLOB SUPPORT... for BLOB to HELP... The original form of the syntax of JAVA to CREATE did not expect the SELECT token must be explicitly provided. Somewhere between 8i and 9i the parser was changed to try the provided text as well as what, with SELECT prefixed. So a CREATE JAVA statement you tried working in 9i but in 8i fails because SELECT would always be added before you try using the clause as a query, resulting a SELECT duplicate token.

ORA-00976: virtual specified or operator not allowed here

Hello
We had error after upgrade of GR 11, 2, in the insert statement.
INSERT INTO SDE_TBL_FLEXTRIMSITROUT
(BRANCHCD,
SOURCECD,
CURRENTNO,
BATCHNO,
DEPTCD,
CTL
INITIATIONDATE,
AMOUNT,
ACCOUNT,
ACCOUNTBRANCH,
TXNCD,
DEBITCREDIT,
LCYEQUIVALENT,
EXCHRATE,
VALUEDATE,
INSTRUMENTNO,
RELCUST,
ADDLTEXT,
TXNMIS1,
TXNMIS2,
TXNMIS3,
TXNMIS4,
TXNMIS5,
TXNMIS6,
TXNMIS7,
TXNMIS8,
TXNMIS9,
TXNMIS10,
COMPMIS1,
COMPMIS2,
COMPMIS3,
COMPMIS4,
COMPMIS5,
COMPMIS6,
COMPMIS7,
COMPMIS8,
COMPMIS9,
COMPMIS10,
COSTCODE1,
COSTCODE2,
COSTCODE3,
COSTCODE4,
COSTCODE5,
RELATEDACCOUNT,
RELATEDREF,
USERREFERENCE,
ACCTPOSTOVERWRITE,
EXCHRATEOVERWRITE,
VALUEDATEOVERWRITE,
ACCTBALOVERWRITE,
ITRREFER,
RefinanceAmount,
PROCESSID)
VALUES
(vBranchCode,
cCreateNewTrimsITR_rec. APPLSYS,
ROWNUM,
nBatchNo,
cCreateNewTrimsITR_rec. DEPT,
vCcy,
To_date (cCreateNewTrimsITR_rec. HOUR, 'YYYYMMDD'),
nAmount,
vAccount,
vAccountBranch, - added by Sibylle
vTxnCd,
cDebitCredit,
nLcyEquivalent,
nExchRate,
To_date (cCreateNewTrimsITR_rec. VALUEDATE, 'YYYYMMDD'),
vInstrumentNo,
--' ' || SUBSTR (cCreateNewTrimsITR_rec. ITRREFER, 2, 11),
vFlxCntry | cCreateNewTrimsITR_rec. APNO,
vDesc,
cCreateNewTrimsITR_rec. TRANSOUC,
RPAD (' ', 9);
vExpenseMIS,
vProductMIS,
RPAD (' ', 9);
RPAD (' ', 9);
RPAD (' ', 9);
RPAD (' ', 9);
RPAD (' ', 9);
RPAD (' ', 9);
RPAD (' ', 9);
RPAD (' ', 9);
RPAD (' ', 9);
RPAD (' ', 9);
RPAD (' ', 9);
RPAD (' ', 9);
RPAD (' ', 9);
RPAD (' ', 9);
RPAD (' ', 9);
RPAD (' ', 9);
RPAD (' ', 9);
RPAD (' ', 9);
RPAD (' ', 9);
RPAD (' ', 9);
RPAD (' ', 9);
RPAD (' ', 20);
cCreateNewTrimsITR_rec. THEIRREF,
RPAD (' ', 16).
cActPostOverwrite,
cExchRateOverWrite,
cValueDateOverWrite,
cAcctBalOverWrite,
cCreateNewTrimsITR_rec. ITRREFER,
cCreateNewTrimsITR_rec. REFIAMOUNT,
nFlexOutProcessId);
Error: ORA-00976: specified virtual or operator not allowed here
According to the audit, which are a problem in GR 11, 2 with insert query using rownum in values.
Someone knows how to fix this?

I wonder why you want to use rownum as a value of insertion? It's not really worth doing an insert without a select statement.

If you want to use it, it would look like

Insert into t1 (name, row_num_value)

Select name

rownum

the t2;

But then you can use an order by clause, on the other it would spoil the rownum order. So an important question is, where is the rownum used for?

Changing table - SQL error: ORA-04091: table XYZ is changing, function of triggering/can not see

Hi all
I am a newbie to Oracle and I am faced with the above error. Please see the below code snippets. Can someone please tell what I am doing wrong? Thank you in advance.
Thank you
CREATE TABLE ABC
(
ID VARCHAR2 ENABLE NUMBER NOT NULL,
FIELD1 ACTIVATE THE NUMBER NOT NULL,
FIELD2 ACTIVATE THE VARCHAR2 (8 BYTE) NOT NULL,
CONSTRAINT JOB_PK PRIMARY KEY (ID)
)
;
CREATE TABLE XYZ
(
ACTIVATE THE NUMBER 4 R_ID NOT NULL,.
ID VARCHAR2 ENABLE NUMBER NOT NULL,
Column1 NUMBER (2.0) default 0.00,.
Column2 NUMBER (2.0) default 0.00,.
COLUMN3 NUMBER (2.0).
NUMBER (2.0) TOTAL 0.00 default.
CONSTRAINT TRIP_PAYMENT_PK PRIMARY KEY (ID)
)
;
create or replace trigger trigger1
After Insert on XYZ
for each line
Declare
number of newTotal;
Start
newTOTAL: =: new. Column1 +: new. Column2 +: new. COLUMN3;
setting a day of XYZ together Total = newTotal;
end;
Insert into ABC (1, 45, ' Demo');
insertion in XYZ (1, 1, 12.50, 10.20 33,50, ");
Error report:
SQL error: ORA-04091: table XYZ is changing, function of triggering/can not see

Try one before line

create or replace trigger trigger1

before inserting on XYZ

for each line

Start
: new. TOTAL: =: new. Column1 +: new. Column2 +: new. COLUMN3;
end;

call a function inside a function to insert into a table and receiver error - ORA-14551: cannot perform a DML operation within a query.

Hi all
your help is greatly appreciated...
Calling B.fucntion inside an A.fonctions to insert data into a table.

Here when you call the B.fucntion to insert data in the table... receiver AM a mistake
Omitted in B - SQL Error: ORA-14551: cannot perform a DML operation inside a query...

Can someone please help me to clarify this...

The FUNCTION A(varUPD_TYPE IN VARCHAR2) RETURN VARCHAR2 IS
varRETURN_VALUE VARCHAR2 (25): = NULL;
numALLOWED_COUNT PROD. PROCESS_COUNTER. TYPE % ALLOWED_COUNT;
numLAST_COUNT_ADDED PROD. PROCESS_COUNTER. TYPE % LAST_COUNT_ADDED;
dtCHANGE_DATE DATE: = NULL;
varSTMT VARCHAR2 (2000);
bln_Allowed BOOLEAN;
myVar VARCHAR2 (32767).

BEGIN
IF varUPD_TYPE = "A" THEN
BEGIN
SELECT CH_DATE, LAST_COUNT_ADDED, ALLOWED_COUNT
IN dtCH_DATE, numLAST_COUNT_ADDED, numALLOWED_COUNT
PROD. PROCESS_COUNTER
WHERE NOM_PROCESSUS = "DAILY".
AND COUNTER_IND = A '
IF dtCH_DATE < = trunc (sysdate) THEN
numLAST_COUNT_ADDED: = 0;
END IF;
EXCEPTION
WHILE OTHERS THEN
numLAST_COUNT_ADDED: = 0;
numALLOWED_COUNT: = 1;
END;
IF numALLOWED_COUNT > = numLAST_COUNT_ADDED + 1 THEN

bln_Allowed: = True;

varSTMT: = "UPDATE PROD. TMS_PROCESS_COUNTER ';
varSTMT: = varSTMT | ' SET last_count_added = ' | (numLAST_COUNT_ADDED + 1);
varSTMT: = varSTMT | "WHERE nom_processus =" DAILY "';
varSTMT: = varSTMT | "AND COUNTER_IND ="D"';

IF varSTMT IS NOT NULL
THEN
MyVar: = B(96,varSTMT);
PROC_LOG (' CALL B ': myVar);
IF myvar > 0 THEN
NULL;
END IF;
END IF;
On the other

End if;
END IF;

EXCEPTION WHEN OTHERS THEN
PROC_LOG ("A failed '");
PROC_LOG (' SQL error: ' |) SUBSTR (SQLERRM, 1, 1000));
RETURNS A NULL VALUE.
PUT AN END TO;
The FUNCTION B(numTABLE_ID IN NUMBER, varSQL_STATEMENT IN VARCHAR2) RETURNS NUMBER IS
varINSERT_BATCH_STMT VARCHAR2 (32767): = NULL;
varADD_REC_TYPE BATCH_TABLES. TYPE % ADD_REC_TYPE;
BEGIN

INSERT INTO BATCH_STATEMENT (ID, TABLE_ID, STATEMENT, QUEUE_SEQUENCE_ID)
VALUES (Numidian, numTABLE_ID, varSQL_STATEMENT, 1);
EXCEPTION WHEN OTHERS THEN
PROC_LOG ('B failed');
PROC_LOG (' SQL error: ' |) SUBSTR (SQLERRM, 1, 1000));
RETURNS - 1;
END B;

Structure of the Batch_statement table:

ID Number (15) not null
number (2) not null table_id
Statement varchar2 (4000) not null
Queue_sequence_id number (5) not null

Why do you do such coding mess full of bad practices.

Remove the exceptions WHEN OTHERS, you're a turing a mistake in this way, they are bugs and (never) use functions to perform DML.

Functions are not intended for DML. Period.

Oracle on the SQL Server tables dblinked query error ORA-00904
Hello

I created a dblink to a SQL from Oracle database using generic connectivity.
The following query returns the error ORA-00904 invalid identifier in the (tblEmp.Empno) WHERE clause

SELECT 'EmpNo', "EmpName", "DeptName".
OF tblEmp@sqlserver.
tblDept@sqlserver
WHERE tblDept.DeptNo = tblEmp.Empno

I had to include the column names between double quotes because of the case review of the columns, but I can't do the
same thing for the WHERE clause.

(1) so how can I fix this error?
(2) also how can I include the Deptno column with the table alias in the columns list?
(Deptno is ambiguous in the Emp and Dept tables)

Kind regards
Sam
Looks like you have case-sensitive column names, try this
```
SELECT "EmpNo","EmpName", "DeptName"
FROM tblEmp@sqlserver e,
tblDept@sqlserver d
WHERE d."DeptNo" = e."Empno" --<--- are you sure this is the correct join condition
```
What should we not
```
WHERE d."DeptNo" = e."DeptNo"
```
Published by: Alex Nuijten on September 22, 2009 13:28

ERROR "ora-01422" during insertion in the table?

Hello
I have created the dynamic action of PL/SQL to insert data but founded by page_item
```
 declare 
x_found_pages number;
x_auth_id number;
x_user_id number;
 begin
 x_user_id := :P41_USR_ID; -- this is my page_item _____ successful run When change it to number value .. !




      select count(V_APP_PAGES.PAGE_ID) into x_found_pages
      from V_AUTH_DTL V_AUTH_DTL,V_APP_PAGES V_APP_PAGES 
      where V_AUTH_DTL.PAGE_ID!=V_APP_PAGES.PAGE_ID
      and  V_AUTH_DTL.USR_ID = x_user_id;
   
      select T_AUTH.ID into x_auth_id 
      from T_AUTH_DTL T_AUTH_DTL,T_AUTH T_AUTH 
      where T_AUTH_DTL.AUTH_ID=T_AUTH.ID
      and T_AUTH.USR_ID = x_user_id;


-- Checking...? 
  if x_found_pages > 0 then

        for i in (select V_APP_PAGES.PAGE_ID
           from V_AUTH_DTL V_AUTH_DTL,V_APP_PAGES V_APP_PAGES 
           where V_AUTH_DTL.PAGE_ID!=V_APP_PAGES.PAGE_ID
           and  V_AUTH_DTL.USR_ID = x_user_id)
    
  loop
  insert into T_AUTH_DTL (AUTH_ID,PAGE_ID) values (x_auth_id,i.PAGE_ID);
  end loop;

    end if;

 end;
```
Please help me to avoid the ERROR "ora-01422" when running code in the dynamic action...
Thank you...

AMR Abdeen wrote:

I have created the dynamic action of PL/SQL to insert data but founded by page_item
1. declare
2. number of x_found_pages;
3. number of x_auth_id;
4. number of x_user_id;
5. Start
6. x_user_id: =: P41_USR_ID; -It is my page_item _ successfully performed when change to value the number...!
7. SELECT count (V_APP_PAGES. Page_id) in x_found_pages
8. of V_AUTH_DTL V_AUTH_DTL, V_APP_PAGES V_APP_PAGES
9. where V_AUTH_DTL. PAGE_ID! = V_APP_PAGES. PAGE_ID
10. and V_AUTH_DTL. USR_ID = x_user_id;
11. Select T_AUTH.ID from x_auth_id
12. of T_AUTH_DTL T_AUTH_DTL, T_AUTH T_AUTH
13. where T_AUTH_DTL. AUTH_ID = T_AUTH.ID
14. and T_AUTH. USR_ID = x_user_id;
15. -Checking...?
16. If x_found_pages > 0 then
17. I'm in (select V_APP_PAGES. PAGE_ID
18. of V_AUTH_DTL V_AUTH_DTL, V_APP_PAGES V_APP_PAGES
19. where V_AUTH_DTL. PAGE_ID! = V_APP_PAGES. PAGE_ID
20. and V_AUTH_DTL. USR_ID = x_user_id)
21. loop
22. insert into T_AUTH_DTL (AUTH_ID, PAGE_ID) values (x_auth_id, i.PAGE_ID);
23. end loop;
24. end if;
25. end;
Please help me to avoid the ERROR "ora-01422" when running code in the dynamic action...

The error is explicit:

ORA-01422: exact fetch returns more than number of lines

Cause: The exact extraction specified number is less than the rows returned.

Action: Rewrite the query or change the number of rows requested

This would imply the query in line 16 as County dissociated in the previous one will always return only one row.

Run
```
select T_AUTH.ID into x_auth_id
from T_AUTH_DTL T_AUTH_DTL,T_AUTH T_AUTH
where T_AUTH_DTL.AUTH_ID=T_AUTH.ID
and T_AUTH.USR_ID = :x_user_id
```
in the workshop of SQL by using the P41_USR_ID value in the variable link to find out how many rows it returns.

It is likely that the entire block can be replaced by a single INSERT statement. If you provide instructions CREATE TABLE, INSERT statements to create sample data and a clear definition of the requirements that we try to do.

What is the point of the inclusion of tables aliases that are exactly the same as the names of the tables?

"Is:java.sql.SQLException error: ORA-01555: snapshot too old: rollback segment number with the name ' ' too small '.

Hello
We conduct apply CM which is a failure with the Error: "declared:java.sql.SQLException: ORA-01555: snapshot too old: rollback segment number with the name '' too small'."
Its in our unique the production instance. I checked on the return parameter. Here are the details.
SQL > show Cancel parameter
VALUE OF TYPE NAME
------------------------------------ ----------- ------------------------------
_in_memory_undo Boolean TRUE
_undo_debug_usage integer 2
UNDO_MANAGEMENT string AUTO
UNDO_RETENTION integer 40000
undo_tablespace string APPS_UNDOTS1
SQL > select max (maxquerylen) of v$ undostat;
MAX (MAXQUERYLEN)
----------------
637116
Please suggest what needs to be done to go further.

Kind regards
Prabhat.
Post edited by: 942633

Hello

ORA-02067: the rollback transaction or registration required

As mentioned, you will need to look at the design of the code:

Error: ORA 2067
Text: rollback transaction or registration required
-------------------------------------------------------------------------------
Cause: A failure (typically a trigger or a stored procedure with several updates remotely) has occurred, such as the execution of all or nothing from a previous call to Oracle cannot be guaranteed.
Action: return to a previous point of backup or restore the transaction and resubmit.

------

ORA-01555 caused by the following SQL statement (SQL ID: 5y0q4u8r2hdy9, query term s = 637608, SCN: 0x0bcc.4ed82762):

------

ACTUAL SIZE [MB] UNDO UNDO RETENTION [s] NECESSARY UNDO SIZE [MB]

------------------------ ------------------------------------------------------------------------- ------------------------

304849 40000 267232.292

To better help you, please let us know:

-What is the function of this program.

-Did you recently parameter changes until you have this error.

Please ensure that the validation controls are implemented correctly, the DBA team and development will work hand in hand.

Thank you &

Best regards

InPlace schema evolution error: ORA-31166: error code internal etc...

Hello

I have a table in which I will be storing an XMLTYPE column based on an XML schema. I use the following version of the database:

SQL*Plus: Release 11.2.0.1.0 Production on Thu Aug 23 18:20:12 2012

Copyright (c) 1982, 2010, Oracle.  All rights reserved.


Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

Now, when I run my test InPlace Schema Evolution, I get the following error message:

< font color = "red" >

ORA-31166: internal error code to handle ignorable attributes

< / make >

I built a re-producable case of test for the purpose of this post on the forum. For starters, I have a database scheme grants the following privileges:

DIRECTLY GRANTED SYSTEM PRIVS
=============================
CREATE TRIGGER
ALTER SESSION
CREATE TABLE

EXECUTE PRIVS (SYS-OWNED PACKAGES)
=============
EXECUTE ON DBMS_XMLSCHEMA

ROLES GRANTED
=============
CONNECT
DATA_ROLE

DATA_ROLE DDL
=============
create role DATA_ROLE not identified;
grant create database link to DATA_ROLE;
GRANT CREATE MATERIALIZED VIEW TO DATA_ROLE;
grant create procedure to DATA_ROLE;
grant create sequence to DATA_ROLE;
GRANT CREATE SYNONYM TO DATA_ROLE;
grant create table to DATA_ROLE with admin option;
grant create trigger to DATA_ROLE;
grant create view to DATA_ROLE;
grant select any dictionary to DATA_ROLE;

All other scripts are run as the database schema. For the purposes of clarity, let's call the {*} TEST_DB_SCHEMA {*}. I follow the steps below in this scheme:

H3. 1. run this PL/SQL script to record the Version 1 of my XML schema:

PROMPT -------------------------------;
PROMPT INITIAL XML SCHEMA REGISTRATION;
PROMPT -------------------------------;

SET SERVEROUTPUT ON
SET FEEDBACK OFF

DECLARE
   l_xsd_url_con CONSTANT VARCHAR2(60) := 'http://home/xsd/test_binXML_v1.xsd';
   
   l_xml_schema VARCHAR2(32767);
   
   E_XSD_ALREADY_REGISTERED EXCEPTION;
   PRAGMA EXCEPTION_INIT(E_XSD_ALREADY_REGISTERED, -31085);
BEGIN
   l_xml_schema :=
      '<xs:schema'||CHR(10)||
      'xmlns:xs="http://www.w3.org/2001/XMLSchema"'||CHR(10)||
      'xmlns:xdb="http://xmlns.oracle.com/xdb"'||CHR(10)||
      'version="1.0"'||CHR(10)||
      'xdb:storeVarrayAsTable = "true">'||CHR(10)||
      ' <xs:element name="TransactionBatch" type="TransactionBatchType" xdb:defaultTable="XSD_TEST_BATCH_BINXML1"/>'||CHR(10)||
      ' <xs:complexType name="TransactionBatchType">'||CHR(10)||
      '  <xs:sequence>'||CHR(10)||
      '   <xs:element name="Transaction" type="TransactionType" minOccurs="1" maxOccurs="unbounded" xdb:defaultTable="XSD_TEST_TRANSACTION_BINXML1"/>'||CHR(10)||
      '  </xs:sequence>'||CHR(10)||
      ' </xs:complexType>'||CHR(10)||
      ' <xs:complexType name="TransactionType">'||CHR(10)||
      '  <xs:sequence>'||CHR(10)||
      '   <xs:element name="Portal" type="PortalType" minOccurs="1" maxOccurs="1" />'||CHR(10)||
      '   <xs:element name="CustomerId" type="CustomerIdType" minOccurs="1" maxOccurs="1"/>'||CHR(10)||
      '   <xs:element name="TransactionQuantity" type="TransactionQuantityType" minOccurs="1" maxOccurs="1"/>'||CHR(10)||
      '   <xs:element name="AppTransactionId" type="AppTransactionIdType" minOccurs="1" maxOccurs="1"/>'||CHR(10)||
      '   <xs:element name="TransactionDetails" type="TransactionDetailType" minOccurs="1" maxOccurs="1"/>'||CHR(10)||
      '   <xs:element name="Username" type="UsernameType" minOccurs="1" maxOccurs="1" />'||CHR(10)||
      '  </xs:sequence>'||CHR(10)||
      ' </xs:complexType>'||CHR(10)||
      ' <xs:simpleType name="PortalType">'||CHR(10)||
      '  <xs:restriction base="xs:string">'||CHR(10)||
      '   <xs:minLength value="1"/>'||CHR(10)||
      '   <xs:maxLength value="30"/>'||CHR(10)||
      '   <xs:enumeration value="TEST1"/>'||CHR(10)||
      '   <xs:enumeration value="TEST2"/>'||CHR(10)||
      '  </xs:restriction>'||CHR(10)||
      ' </xs:simpleType>'||CHR(10)||
      ' <xs:simpleType name="CustomerIdType">'||CHR(10)||
      '  <xs:restriction base="xs:string"/>'||CHR(10)||
      ' </xs:simpleType>'||CHR(10)||
      ' <xs:simpleType name="TransactionQuantityType">'||CHR(10)||
      '  <xs:restriction base="xs:integer">'||CHR(10)||
      '   <xs:minExclusive value="0"/>'||CHR(10)||
      '  </xs:restriction>'||CHR(10)||
      ' </xs:simpleType>'||CHR(10)||
      ' <xs:simpleType name="AppTransactionIdType">'||CHR(10)||
      '  <xs:restriction base="xs:string">'||CHR(10)||
      '   <xs:minLength value="1"/>'||CHR(10)||
      '   <xs:maxLength value="20"/>'||CHR(10)||
      '  </xs:restriction>'||CHR(10)||
      ' </xs:simpleType>'||CHR(10)||
      ' <xs:simpleType name="TransactionDetailType">'||CHR(10)||
      '  <xs:restriction base="xs:string">'||CHR(10)||
      '   <xs:minLength value="1"/>'||CHR(10)||
      '  </xs:restriction>'||CHR(10)||
      ' </xs:simpleType>'||CHR(10)||
      ' <xs:simpleType name="UsernameType">'||CHR(10)||
      '  <xs:restriction base="xs:string">'||CHR(10)||
      '   <xs:minLength value="1"/>'||CHR(10)||
      '   <xs:maxLength value="30"/>'||CHR(10)||
      '  </xs:restriction>'||CHR(10)||
      ' </xs:simpleType>'||CHR(10)||
      '</xs:schema>';
   
   DBMS_XMLSCHEMA.REGISTERSCHEMA(
      schemaurl       => l_xsd_url_con,
      schemadoc       => l_xml_schema,
      local           => TRUE,                             -- XSD must only be visible to the Owner DB Schema in which this script is run.
      genTypes        => FALSE,                            -- Don't want to generate object types, as we're using Binary XML.
      force           => FALSE,                            -- Raise all errors on creation
      owner           => USER,                             -- XML Schema will belong to the currently executing user.
      options         => DBMS_XMLSCHEMA.REGISTER_BINARYXML -- We wish to register the XSD as Binary XML.
   );
   
EXCEPTION
   WHEN E_XSD_ALREADY_REGISTERED
   THEN
      DBMS_OUTPUT.PUT_LINE('XML Schema '||l_xsd_url_con||' is already registered.');
      
END;
/

SET FEEDBACK ON

H3. 2. create a bunch of Table with an XMLTYPE column based on version 1 of my XML schema:

PROMPT ----------------------;
PROMPT ONE-OFF DDL STATEMENTS;
PROMPT ----------------------;

DROP TABLE test_batch;
DROP SEQUENCE seq_test_batch_id;

CREATE TABLE test_batch
(
   batch_id        NUMBER(20),
   batch_timestamp TIMESTAMP   DEFAULT SYSTIMESTAMP,
   batch_xml       XMLTYPE,
   CONSTRAINT tbh_batch_id_nn        CHECK(batch_id IS NOT NULL),
   CONSTRAINT tbh_batch_timestamp_nn CHECK(batch_timestamp IS NOT NULL),
   CONSTRAINT tbh_batch_xml_nn       CHECK(batch_xml IS NOT NULL)
)
XMLTYPE COLUMN batch_xml STORE AS SECUREFILE BINARY XML
XMLSCHEMA "http://home/xsd/test_binXML_v1.xsd"
ELEMENT "TransactionBatch"
PARTITION BY RANGE(batch_timestamp)
INTERVAL (NUMTOYMINTERVAL(1, 'MONTH'))
(
   PARTITION P_TEST_BATCH_201208 VALUES LESS THAN (TO_DATE('01-SEP-2012', 'DD-MON-YYYY')) TABLESPACE &&TABLSPACE_OF_YOUR_CHOICE
);

CREATE UNIQUE INDEX idx_tbh_batch_id ON test_batch(batch_id)
TABLESPACE TXTREME_IDX_XLG;

ALTER TABLE test_batch
   ADD CONSTRAINT tbh_batch_id_pk PRIMARY KEY (batch_id) USING INDEX idx_tbh_batch_id;

CREATE SEQUENCE seq_test_batch_id
START WITH 1
INCREMENT BY 1
MAXVALUE 99999999999999999999
CYCLE
NOCACHE
NOORDER;

H3. 3. fill this table with the test data.

PROMPT --------------------------;
PROMPT CREATING INITIAL TEST DATA;
PROMPT --------------------------;

TRUNCATE TABLE TEST_BATCH;

SET TIMING ON
DECLARE
   l_batch_count_con CONSTANT NUMBER(4) := 200;
   
   l_transaction_count   PLS_INTEGER;
   l_total_transactions  PLS_INTEGER DEFAULT 0;
   l_transaction_xmlclob CLOB;
   l_transaction_xmldoc  XMLTYPE;
BEGIN
   FOR idx IN 1..l_batch_count_con
   LOOP
      l_transaction_count := TRUNC(DBMS_RANDOM.VALUE(1,100));
      
      -- Initialise XML CLOB String. 
      l_transaction_xmlclob := '<?xml version="1.0"?>'||CHR(10)||'<TransactionBatch>';
      
      -- Insert the contents of the XML CLOB String.
      FOR idx IN 1 .. l_transaction_count
      LOOP
         l_transaction_xmlclob := l_transaction_xmlclob||CHR(10)||
                                  '  <Transaction>'||CHR(10)||
                                  '    <Portal>TEST1</Portal>'||CHR(10)||
                                  '    <CustomerId>1234567891</CustomerId>'||CHR(10)||
                                  '    <TransactionQuantity>4</TransactionQuantity>'||CHR(10)||
                                  '    <AppTransactionId>1232K89C</AppTransactionId>'||CHR(10)||
                                  '    <TransactionDetails>This is another long free text field</TransactionDetails>'||
                                  '    <Username>Jimbo2</Username>'||CHR(10)||
                                  '  </Transaction>';
      END LOOP;
      
      --Terminate XML CLOB String.
      l_transaction_xmlclob := l_transaction_xmlclob||CHR(10)||'</TransactionBatch>';
      
      -- Create XMLTYPE XML Document.
      l_transaction_xmldoc := XMLTYPE.createXML(l_transaction_xmlclob);
      
      -- Populate the TEST_BATCH Table.
      INSERT INTO test_batch
        ( batch_id,
          batch_timestamp,
          batch_xml
        )
      VALUES
        ( SEQ_TEST_BATCH_ID.NEXTVAL,
          SYSTIMESTAMP,
          l_transaction_xmldoc
        );
        
      l_total_transactions := l_total_transactions + l_transaction_count;
   END LOOP;
   
   DBMS_OUTPUT.PUT_LINE('Inserted a total of '||l_total_transactions||' transaction XML pieces across '||l_batch_count_con||' Test Batches.');
   COMMIT;
   DBMS_OUTPUT.PUT_LINE('Commit complete.');
END;
/

SET TIMING OFF

H3. 4. save the Version 2 of my XML schema

PROMPT -----------------------------------------------------------------------------------;
PROMPT NEW XML SCHEMA REGISTRATION - IDENTICAL TO OLD SCHEMA EXCEPT FOR NEW <Test> ELEMENT;
PROMPT -----------------------------------------------------------------------------------;

SET FEEDBACK OFF

DECLARE
   l_xsd_url_con CONSTANT VARCHAR2(60) := 'http://home/xsd/test_binXML_v2.xsd';
   
   l_xml_schema VARCHAR2(32767);
   
   E_XSD_ALREADY_REGISTERED EXCEPTION;
   PRAGMA EXCEPTION_INIT(E_XSD_ALREADY_REGISTERED, -31085);
BEGIN
   l_xml_schema :=
      '<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xdb="http://xmlns.oracle.com/xdb" version="1.0" xdb:storeVarrayAsTable="true">'||CHR(10)||
      '<xs:element name="TransactionBatch" type="TransactionBatchType" xdb:defaultTable="XSD_TEST_BATCH_BINXML2"/>'||CHR(10)||
      '<xs:complexType name="TransactionBatchType">'||CHR(10)||
      ' <xs:sequence>'||CHR(10)||
      '  <xs:element name="Transaction" type="TransactionType" minOccurs="1" maxOccurs="unbounded" xdb:defaultTable="XSD_TEST_TRANSACTION_BINXML2"/>'||CHR(10)||
      ' </xs:sequence>'||CHR(10)||
      '</xs:complexType>'||CHR(10)||
      '<xs:complexType name="TransactionType">'||CHR(10)||
      ' <xs:sequence>'||CHR(10)||
      '  <xs:element name="Portal" type="PortalType" minOccurs="1" maxOccurs="1"/>'||CHR(10)||
      '  <xs:element name="CustomerId" type="CustomerIdType" minOccurs="1" maxOccurs="1"/>'||CHR(10)||
      '  <xs:element name="TransactionQuantity" type="TransactionQuantityType" minOccurs="1" maxOccurs="1"/>'||CHR(10)||
      '  <xs:element name="AppTransactionId" type="AppTransactionIdType" minOccurs="1" maxOccurs="1"/>'||CHR(10)||
      '  <xs:element name="TransactionDetails" type="TransactionDetailType" minOccurs="1" maxOccurs="1"/>'||CHR(10)||
      '  <xs:element name="Username" type="UsernameType" minOccurs="1" maxOccurs="1"/>'||CHR(10)||
      '  <xs:element name="Test" type="TestType" minOccurs="0" maxOccurs="1"/>'||CHR(10)||
      ' </xs:sequence>'||CHR(10)||
      '</xs:complexType>'||CHR(10)||
      '<xs:simpleType name="PortalType">'||CHR(10)||
      ' <xs:restriction base="xs:string">'||CHR(10)||
      '  <xs:minLength value="1"/>'||CHR(10)||
      '  <xs:maxLength value="30"/>'||CHR(10)||
      '  <xs:enumeration value="TEST1"/>'||CHR(10)||
      '  <xs:enumeration value="TEST2"/>'||CHR(10)||
      ' </xs:restriction>'||CHR(10)||
      '</xs:simpleType>'||CHR(10)||
      '<xs:simpleType name="CustomerIdType">'||CHR(10)||
      ' <xs:restriction base="xs:string"/>'||CHR(10)||
      '</xs:simpleType>'||CHR(10)||
      '<xs:simpleType name="TransactionQuantityType">'||CHR(10)||
      ' <xs:restriction base="xs:integer">'||CHR(10)||
      '  <xs:minExclusive value="0"/>'||CHR(10)||
      ' </xs:restriction>'||CHR(10)||
      '</xs:simpleType>'||CHR(10)||
      '<xs:simpleType name="AppTransactionIdType">'||CHR(10)||
      ' <xs:restriction base="xs:string">'||CHR(10)||
      '  <xs:minLength value="1"/>'||CHR(10)||
      '  <xs:maxLength value="20"/>'||CHR(10)||
      ' </xs:restriction>'||CHR(10)||
      '</xs:simpleType>'||CHR(10)||
      '<xs:simpleType name="TransactionDetailType">'||CHR(10)||
      ' <xs:restriction base="xs:string">'||CHR(10)||
      '  <xs:minLength value="1"/>'||CHR(10)||
      ' </xs:restriction>'||CHR(10)||
      '</xs:simpleType>'||CHR(10)||
      '<xs:simpleType name="UsernameType">'||CHR(10)||
      ' <xs:restriction base="xs:string">'||CHR(10)||
      '  <xs:minLength value="1"/>'||CHR(10)||
      '  <xs:maxLength value="30"/>'||CHR(10)||
      ' </xs:restriction>'||CHR(10)||
      '</xs:simpleType>'||CHR(10)||
      '<xs:simpleType name="TestType">'||CHR(10)||
      ' <xs:restriction base="xs:string">'||CHR(10)||
      '  <xs:minLength value="1"/>'||CHR(10)||
      '  <xs:maxLength value="30"/>'||CHR(10)||
      ' </xs:restriction>'||CHR(10)||
      '</xs:simpleType>'||CHR(10)||
      '</xs:schema>';
   
   DBMS_XMLSCHEMA.REGISTERSCHEMA(
      schemaurl       => l_xsd_url_con,
      schemadoc       => l_xml_schema,
      local           => TRUE,                             -- XSD must only be visible to the Owner DB Schema in which this script is run.
      genTypes        => FALSE,                            -- Don't want to generate object types, as we're using Binary XML.
      force           => FALSE,                            -- Raise all errors on creation
      owner           => USER,                             -- XML Schema will belong to the currently executing user.
      options         => DBMS_XMLSCHEMA.REGISTER_BINARYXML -- We wish to register the XSD as Binary XML.
   );
   
EXCEPTION
   WHEN E_XSD_ALREADY_REGISTERED
   THEN
      DBMS_OUTPUT.PUT_LINE('XML Schema '||l_xsd_url_con||' is already registered.');
      
END;
/

SET FEEDBACK ON

H3. 5 test to insert a new XML document in line with the second XML schema. This test fails as expected.

PROMPT ---------------------------------------------------------------;
PROMPT ATTEMPT TO INSERT V2 XSD-COMPLIANT XMLDOC INTO TEST_BATCH TABLE;
PROMPT ---------------------------------------------------------------;

DECLARE
   l_transaction_xmldoc XMLTYPE;
   
   E_XSD_VALIDATION_FAILURE EXCEPTION;
   PRAGMA EXCEPTION_INIT(E_XSD_VALIDATION_FAILURE, -31061);
BEGIN
   l_transaction_xmldoc := XMLTYPE.createXML(
                              '<?xml version="1.0" encoding="UTF-8"?>'||CHR(10)||
                              '<TransactionBatch>'||CHR(10)||
                              '  <Transaction>'||CHR(10)||
                              '    <Portal>CARMAN</Portal>'||CHR(10)||
                              '    <CustomerId>1234567891</CustomerId>'||CHR(10)||
                              '    <TransactionQuantity>4</TransactionQuantity>'||CHR(10)||
                              '    <AppTransactionId>1232K89C</AppTransactionId>'||CHR(10)||
                              '    <TransactionDetails>This is a long free text field</TransactionDetails>'||CHR(10)||
                              '    <Username>Jimbo2</Username>'||CHR(10)||
                              '    <Test>This is an In-Place Schema Evolution Test</Test>'||CHR(10)||
                              '  </Transaction>'||CHR(10)||
                              '</TransactionBatch>'
                           );
   
   -- Attempt to populate the SUBMISSION_BATCH Table.
   INSERT INTO submission_batch
     ( batch_id,
       batch_timestamp,
       batch_xml
     )
   VALUES
     ( SEQ_SUB_BATCH_ID.NEXTVAL,
       SYSTIMESTAMP,
       l_transaction_xmldoc
     );
   
   DBMS_OUTPUT.PUT_LINE(SQL%ROWCOUNT||' row inserted.');
   COMMIT;
   DBMS_OUTPUT.PUT_LINE('Commit complete.');

EXCEPTION
   WHEN E_XSD_VALIDATION_FAILURE
   THEN
      DBMS_OUTPUT.PUT_LINE('Insert failed as expected.'||CHR(10));
      DBMS_OUTPUT.PUT_LINE(SQLERRM);
END;
/

H3. 6. try Inplace development of Version 1 of the XML schema in Version 2.

PROMPT --------------------------------------------------------------------------------------;
PROMPT PERFORM IN-PLACE EVOLUTION AND DE-REGISTER/PURGE OLD SCHEMA IF EVOLUTION IS SUCCESSFUL;
PROMPT --------------------------------------------------------------------------------------;

SET TIMING ON

DECLARE
   l_current_schema   XMLTYPE;
   l_new_schema       XMLTYPE;
   l_xsd_differences  XMLTYPE;
   
   l_resource         BOOLEAN;
BEGIN
   SELECT schema
     INTO l_current_schema
     FROM user_xml_schemas
    WHERE schema_url = 'http://home/xsd/test_binXML_v1.xsd';
   
   SELECT schema
     INTO l_new_schema
     FROM user_xml_schemas
    WHERE schema_url = 'http://home/xsd/test_binXML_v2.xsd';
   
   SELECT XMLDIFF(l_current_schema, l_new_schema)
     INTO l_xsd_differences
     FROM dual;
   
   DBMS_OUTPUT.PUT_LINE('Successfully extrapolated XDIFF XML Document.');
   
   DBMS_XMLSCHEMA.inPlaceEvolve( 'http://home/xsd/test_binXML_v1.xsd',
                                 l_xsd_differences,
                                 DBMS_XMLSCHEMA.INPLACE_TRACE
                               );
   
   DBMS_OUTPUT.PUT_LINE('Successfully evolved original XML Schema.');
   
EXCEPTION
   WHEN OTHERS
   THEN
      ROLLBACK;
      DBMS_OUTPUT.PUT_LINE('Error issued during InPlace XML Schema Evolution:');
      DBMS_OUTPUT.PUT_LINE(SQLERRM);
END;
/

H3. The scripts above provide the following Test output:

Connected to Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 
Connected as TEST_DB_SCHEMA@dbs02local
 
SQL> 
-------------------------------
INITIAL XML SCHEMA REGISTRATION
-------------------------------
 
XML Schema http://home/xsd/test_binXML_v1.xsd is already registered.
 
Executed in 0 seconds

----------------------
ONE-OFF DDL STATEMENTS
----------------------
  
Table created
 
Executed in 0.016 seconds
 
Index created
 
Executed in 0.016 seconds
 
Table altered
 
Executed in 0 seconds
 
Sequence created
 
Executed in 0 seconds

--------------------------
CREATING INITIAL TEST DATA
--------------------------
 
Table truncated
 
Executed in 0.032 seconds

Inserted a total of 10259 transaction XML pieces across 200 Test Batches.
Commit complete.
 
PL/SQL procedure successfully completed
 
Executed in 8.487 seconds

-----------------------------------------------------------------------------------
NEW XML SCHEMA REGISTRATION - IDENTICAL TO OLD SCHEMA EXCEPT FOR NEW <Test> ELEMENT
-----------------------------------------------------------------------------------
 
XML Schema http://home/xsd/test_binXML_v2.xsd is already registered.

---------------------------------------------------------------
ATTEMPT TO INSERT V2 XSD-COMPLIANT XMLDOC INTO TEST_BATCH TABLE
---------------------------------------------------------------
 
Insert failed as expected.

ORA-31061: XDB error: XML event error
ORA-19202: Error occurred in XML processing
LSX-00213: only 0 occurrences of particle "Transaction", minimum is 1
 
PL/SQL procedure successfully completed
 
--------------------------------------------------------------------------------------
PERFORM IN-PLACE EVOLUTION AND DE-REGISTER/PURGE OLD SCHEMA IF EVOLUTION IS SUCCESSFUL
--------------------------------------------------------------------------------------
 
Successfully extrapolated XDIFF XML Document.
Error issued during InPlace XML Schema Evolution:
ORA-31166: internal error code to handle ignorable attributes
 
PL/SQL procedure successfully completed
 
Executed in 0.046 seconds
SQL>

NOTE: When I ran the above tests, I had already created the test of XML schemas. That's why the output messages, say...

H4. Now, as it is the first time I've ever tried evolution of XML schema in Oracle XMLDB, is there someone who could potentially open the door please, re. solve the < font color = "red" >ORA-31166< / police > error?

Hello

First of all, thank you for your efforts on the provision of a decent test case.

However, there are a few inconsistencies:

-Step 5 attempts to insert into SUBMISSION_BATCH, but the table created above is TEST_BATCH
-Same for the sequence name

Now back to the real question...

I think the problem comes because you run XMLDiff against two versions saved of your drawings.
When Oracle stores a schema, it adds a large number of attributes for internal use (you can see them by querying USER_XML_SCHEMAS. DIAGRAM) but we as end users don't have to worry about them.
However, by building the Xdiff document based on these two 'internal' versions, we explicitly say Oracle whose internal attributes must be changed during the evolution of the scheme, leading to potential conflicts.

A few other comments:
-Given that you're using the binary XML schema, you must also set "genTables-online false" and more "genTypes-online false."
-Also delete all annotations from xdb:defaultTable and xdb:storeVarrayAsTable on the diagrams, they are of no use in this situation.
-Do not save the schema of the v2, it is not necessary. Just use a transient instance when calling XMLDiff

So, to summarize:

-XMLDiff run against both original patterns (do not save a new in any case, the process of evolution will take care of replacing the old).
-of course, don't forget to change the INPLACE_TRACE to INPLACE_EVOLVE when ready :)

Hope that helps.

Published by: odie_63 on August 23, 2012 16:31 - fixed some typos

SQL error: ORA-01873: the interval leading precision is too small
Hello

My requirement is to get the current timestamp in the format microsec Epoch.

I am trying to execute the following query

Select (CAST (((current_timestamp-TO_DATE (1er janvier 1970 00:00:00 ', ' 'JJ-MM-AAAA HH24:MI:SS)) * 24 * 60 * 60 * 1000000) AS varchar (32))) as "dt" from dual;))

I get the following error
Error from the 1 in the command line:
Select (CAST (((current_timestamp-TO_DATE (1er janvier 1970 00:00:00 ', ' 'JJ-MM-AAAA HH24:MI:SS)) * 24 * 60 * 60 * 1000000) AS varchar (32))) as double 'dt'))
Error report:
SQL error: ORA-01873: the interval leading precision is too small
01873 00000 - "the interval leading precision is too small."
* Cause: The precision of the interval leading is too small to store the
specified interval.
* Action: Increase the accuracy of foreground of the interval or specify a
meantime, with smaller leading precision.

But if I tried to do
Select (CAST (((sysdate-TO_DATE (1er janvier 1970 00:00:00 ', ' 'JJ-MM-AAAA HH24:MI:SS)) * 24 * 60 * 60 * 1000000) AS varchar (32))) as "dt" from dual;))
works fine, but I get the bad epochtime sysdate has no time zone information.

Please help me how to do the first query to work so that I can get the current_timestamp change to gmt and convert it in time.
Please let me know if there is another way to get the Epochtime.
Depending on whether you want to or not to include the fraction of a second use:
```
with t as (
           select  current_timestamp at time zone 'gmt' - to_timestamp_tz('01/01/1970 00:00:00 GMT','MM-DD-YYYY HH24:MI:SS TZR') interval_diff,
                   cast(current_timestamp at time zone 'gmt' as date) - to_date('01/01/1970 00:00:00', 'MM-DD-YYYY HH24:MI:SS') num_diff
             from  dual
          )
select  cast(
             (
              (
               (
                extract(day from interval_diff) * 24 + extract(hour from interval_diff)
               ) * 60 + extract(minute from interval_diff)
              ) * 60 + extract(second from interval_diff)
             ) * 1000000
             AS varchar(32)
            ) as "ts",
        cast(num_diff * 24 * 60 * 60 * 1000000 AS varchar(32)) as "dt"
  from t
/ 

ts                   dt
-------------------- --------------------
1336237158093000     1336237158000000

SQL>  
```
SY.

SQL error: ORA-01779: cannot modify a column that matches a key examine
Hi all

The requirement is that I have two tables s_party_d and S_CONTACT_d. the need to update the column name with FST_NAME | ',' | Last_name when column rowid in both tables are equal. I used the query previously below: -.

Update
(select
E1. Name,
e.FST_NAME,
Select
Of
s_party_d e1,
E S_CONTACT_d
where
E1. Game of ROW_ID = e.ROW_ID)
name = FST_NAME | ',' | LAST_NAME;

But I get the error message when executing the query

Error in the command line: 31 column: 3
Error report:
SQL error: ORA-01779: cannot modify a column that is mapped to a table not preserved key
01779 00000 - 'impossible to change a column that is mapped to a non-preserved table at key'
* Cause: An attempt was made to insert or update columns in a join finds out who
map to a table not kept the key.
* Action: Change the directly underlying base tables.

Can U please tell me why this error and how to solve?

Thank you
Mathon
Mathon wrote:

So, I have to look into some other method... I can't achieve this using a single update statement...

Well, no matter what you do you need to decide what FST_NAME | ',' | Name to use. As I already pointed out for each line of the line of the s_party_d table there are several rows in table S_CONTACT_d. Again, you must yo decide what S_CONTACT_d table row you want to use. For example:
```
update s_party_d e1
   set e1.name = (
                  select  max(e.FST_NAME) ||', '|| max(e.LAST_NAME)
                    from  S_CONTACT_d e
                    where e1.ROW_ID=e.ROW_ID
                 )
 where e1.ROW_ID in (
                     select  e.ROW_ID
                       from  S_CONTACT_d e
                    )
/
```
SY.

Not able to change the password by using the query. Select APPS.fnd_web_sec
Not able to change the password by using the query.
Select APPS.fnd_web_sec.change_password ('username', 'password') 'RES' double;

Can someone tell why and what privileges and subsidies have flexibility to the user non-apps while it can change the password using fnd_web_sec.change_password.

Concerning
the information above does not solve my problem, I get the message

Because you do not have permission on all objects that are referenced by the API (see below).

Select FND_WEB_SEC. CHANGE_PASSWORD ('MARSHAD', 'mohammad @123') "RES" of the double

*

ERROR on line 1:

ORA-00942: table or view does not exist

ORA-06512: at the 'APPS '. FND_CORE_LOG', line 25

ORA-06512: at the 'APPS '. FND_CORE_LOG', line 432

ORA-06512: at the 'APPS '. FND_PROFILE', line 110

ORA-06512: at the 'APPS '. FND_SSO_MANAGER", line 227

ORA-06512: at the 'APPS '. FND_WEB_SEC', line 1425

ORA-06512: at line 1...

can you please list me what are the grants and other Jules Destrooper I should give to a user so that he can change password.

I don't have the list of objects and you should get yourself by consulting the site code and eTRM API.

by changing the DDT in the user non-apps after the grant, will, it may be able to change the password.please tell this syntax is correct or not.
Select applications. FND_WEB_SEC. CHANGE_PASSWORD ('user', 'pwd') "RES" of the double

What is the point of using 'FND_WEB_SEC. CHANGE_PASSWORD' and not FNDCPASS or FND_USER_PKG API?

Thank you
Hussein

Get error - ora-01003 no instruction not analyzed
Hello

I customized a form and added under request for insertion trigger before Friday. For the last 4 days that it was working fine and now if we try to save this form, we get the error "ora-01003 no instruction not analyzed.

Below you will find the query added in the prior insertion trigger: -.

DECLARE
BEGIN
INCIDENT_TRACKING_LIB. Pre_Insert;
Q_TXN. Event ('PRE-INSERT', ' INCIDENT_TRACKING');
INSERT INTO cmw_bc_mobile_number select: incident_tracking.account,: INCIDENT_TRACKING. Error_code, double SYSDATE
WHERE does not exist (select * from cmw_bc_mobile_number)
where customer_number =:incident_tracking.account);
END;

Please can someone help me solve this problem.

Kind regards
REDA
did you change the tables involved?

escape character must be the string of length 1 (error ORA-01425)
Hi all!

I get this error message (SQL error: ORA-01425: escape character must be the string of length 1) when querying an oracle 9i database with:

SELECT * FROM table WHERE column LIKE '%' ESCAPE ' \';

Bar which makes it a double backslash (included with apostrophes) would solve the problem, however, with this change, the request is more executable in a 10g database.

Is there a way to make the executable SQL above (with a single backslash escape) code in both (and latest) versions, without changing it? Maybe a server definition database that could solve this problem...

Suggestions for the problem described are greatly appreciated!

Thank you
col2 NVARCHAR2 (100)

OK, you should have mentioned before using unicode ;)

However, should not always identical fields be treated identically in any database?...

Yes, they should :(

In any case the escape string should obviously be treated as unicode so the right way, I guess, would be
```
  select * from mytable where col2 like N'%' escape N'\'; 
```
Note the front N ' \' to make the unicode string.

Change Notifications error "ORA-29973: unsupported query or operation."

Similar Questions

Maybe you are looking for