bug: Houston-27122 and ORA-00904

I get this error when I run any page of the adf. Error object in the view. error is as follows

What is error.how can I fix this. Guide to devloper ADF is this problem of "_Default using Inline views for read-only queries" _

anyone has an idea about this.

Thanks in advance

Published by: vinay kumar on April 22, 2009 09:29

Vinay,

You even try to "setNestedSelectForFullSql" in the little box marked 'Search' on the forum page?

You will find stories like this one:

I assume you are using an expert mode VO.
In this case, you can override the create() method in the subclass of the VOImpl of your VO and call the method:

  // overridden framework method in YourViewNameImpl.java
  public void create() {
    super.create();
    setNestedSelectForFullSql(false);
  }

This should avoid the "wrapping" of the request with the online display.

Tags: Java

Similar Questions

DROP table and CREATE with column name and ORA: 00904
Hello
I created a table with an attribute date CRTD_ON and two other attributes. Successfully created. I can see the data tab and the window empty data with column names in the header...
Now, I had to change the name of field attribute date on OPNG_DATE so I don't bother to change, instead, I deleted and created with the name of the column has changed. Then I restart the ddl. Once again managed to create. But this time I am not able to see the data tab or the column headings. And I see the error of the log of the data Publisher ORA-00904: "CRTD_ON": invalid identifier
Is this a bug?
There is a current bug where you will get the data if you have a public synonym with the same table name pointing to another table with another structure. Can you confirm that in your environment?

K.

The rights of the applicant, change of context (PL/SQL-> SQL-> PL/SQL) and ORA-00904

Hello
I'm doing a validation test of principle with regard to the rights of the applicant. I created 2 diagrams of Test (DEFINER1 and INVOKER1) for the same thing. When I call a procedure in the Invoker1 Definer1 and the procedure has, in turn, a SQL statement inside that a PL/SQL function calls, so he get ORA-00904 "" is not a valid identifier. All procedures/packages in the scheme of Definer1 are created as the rights of the applicant. Simplified script below for the same, kindly let me know if I make a mistake, it's the expected behavior, or miss me something.
set line 10000
Set feedback off
------------------------------------------------------------------------------------------------------------------------------
QUICK problem: error ORA-00904: "object name": invalid identifier
CALLS while the use of the appellant's rights, procedure call PL/SQL that has a SQL that calls a PL/SQL function.
------------------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------------------------
GUEST
GUEST
------------------------------------------------------------------------------------------------------------------------------
Creating patterns DEFINER1 and INVOKER1 QUICK...
GUEST
------------------------------------------------------------------------------------------------------------------------------
CREATE DEFINER1 USER IDENTIFIED BY DEFINER1
TEMPORARY TEMP TABLESPACE
/
GRANT CREATE SESSION TO DEFINER1
/
GRANT CREATE PROCEDURE FOR DEFINER1
/
CREATE INVOKER1 USER IDENTIFIED BY INVOKER1
TEMPORARY TEMP TABLESPACE
/
GRANT CREATE SESSION TO INVOKER1
/
GRANT CREATE PROCEDURE FOR INVOKER1
/
------------------------------------------------------------------------------------------------------------------------------
GUEST will now connect to the DEFINER1 schema...
GUEST
CONNECT DEFINER1/DEFINER1
------------------------------------------------------------------------------------------------------------------------------
Creating QUICK package (with rights of Summoners) with 2 functions simple (one with PRAGMA RESTRICT_REFERENCES another without him.)...
GUEST
------------------------------------------------------------------------------------------------------------------------------
CREATE or REPLACE PACKAGE global_pkg
AUTHID CURRENT_USER
AS
FUNCTION add2 (NUMBER of p1
NUMBER of p2
)
RETURN NUMBER;
FUNCTION add2_rr (NUMBER of p1
NUMBER of p2
)
RETURN NUMBER;
PRAGMA RESTRICT_REFERENCES (add2_rr, WNDS, WNPS, NSOR, RNP);
END global_pkg;
/
---------------------------------------------------------------
CREATE OR REPLACE PACKAGE BODY GLOBAL_PKG
AS
---------------------------------------------------------------
FUNCTION add2 (NUMBER of p1
NUMBER of p2
)
RETURN NUMBER
IS
BEGIN
RETURN (p1 + p2);
END add2;
---------------------------------------------------------------
FUNCTION add2_rr (NUMBER of p1
NUMBER of p2
)
RETURN NUMBER
IS
BEGIN
RETURN (p1 + p2);
END add2_rr;
---------------------------------------------------------------
END global_pkg;
/
------------------------------------------------------------------------------------------------------------------------------
ENCOURAGE creating stand-alone simple function (with rights of Summoners)...
GUEST
------------------------------------------------------------------------------------------------------------------------------
FUNCTION to CREATE or REPLACE add2 (NUMBER of p1
NUMBER of p2
)
RETURN NUMBER
AUTHID CURRENT_USER
IS
BEGIN
RETURN (p1 + p2);
END ADD2;
/
------------------------------------------------------------------------------------------------------------------------------
PROMPT creation of procedure (with rights of Summoners) who calls the Package and functions...
GUEST
------------------------------------------------------------------------------------------------------------------------------
CREATE OR REPLACE PROCEDURE pr_tester
AUTHID CURRENT_USER
IS
l_num NUMBER (2);
BEGIN
dbms_output.put_line (1 + 1 = ' | global_pkg.add2_rr (1,1));
BEGIN
SELECT global_pkg.add2_rr (1.1)
IN l_num
FROM DUAL;
dbms_output.put_line ('worked..');
EXCEPTION
WHILE OTHERS
THEN
dbms_output.put_line ('global_pkg.add2_rr wo' |) SQLERRM);
END;
dbms_output.put_line (1 + 1 = ' | global_pkg.) ADD2 (1,1));
BEGIN
SELECT global_pkg.add2 (1.1)
IN l_num
FROM DUAL;
dbms_output.put_line ('worked..');
EXCEPTION
WHILE OTHERS
THEN
dbms_output.put_line ('global_pkg.add2 wo' |) SQLERRM);
END;
dbms_output.put_line (1 + 1 = ' |) ADD2 (1,1));
BEGIN
SELECT add2 (1.1)
IN l_num
FROM DUAL;
dbms_output.put_line ('worked..');
EXCEPTION
WHILE OTHERS
THEN
dbms_output.put_line ('add2 wo' |) SQLERRM);
END;
END;
/
------------------------------------------------------------------------------------------------------------------------------
Grant QUICK overlooking the procedure to INVOKER1 scheme...
GUEST
------------------------------------------------------------------------------------------------------------------------------
GRANT EXECUTE ON pr_tester TO invoker1
/
------------------------------------------------------------------------------------------------------------------------------
Test QUICK 1: Define schema works...
GUEST
------------------------------------------------------------------------------------------------------------------------------
SET SERVEROUTPUT ON
BEGIN
pr_tester;
END;
/
------------------------------------------------------------------------------------------------------------------------------
GUEST
GUEST
GUEST
GUEST will now connect to the INVOKER1 schema...
GUEST
CONNECT INVOKER1/INVOKER1
------------------------------------------------------------------------------------------------------------------------------
Test FAST 2: Fails with ORA - 00904 define schema
------------------------------------------------------------------------------------------------------------------------------
SET SERVEROUTPUT ON
BEGIN
definer1.pr_tester;
END;
/
------------------------------------------------------------------------------------------------------------------------------
GUEST
GUEST
GUEST
INVITE to drop the two schemas, enter the password for the sys
------------------------------------------------------------------------------------------------------------------------------
CONNECT SYS AS SYSDBA
DROP USER CASCADE DEFINER1
/
DROP USER INVOKER1
/
------------------------------------------------------------------------------------------------------------------------------
GUEST
GUEST has dropped to users...
------------------------------------------------------------------------------------------------------------------------------
Thank you
Marie.

Basically, you know the answer...

Why you call procedure Tester pr_tester with the name of schema prefix (definer1.pr_tester) during his call of the schema of the invoker?

Now... Imagine the following query runs under the scheme of the appellant:

SELECT global_pkg.add2_rr (1.1)

IN l_num

FROM DUAL;

the schema of the invoker 'knows' global_pkg?

HTH

ORA-00904 during execution of the functions and procedures (IDE version 4.1.0.19)

Recently, I updated my Oracle SQL Developer to the latest version (see below) and now when I try to run the function or procedure of the IDE, I had an alert with the error: "ORA-00904:"OBJECT_ID": invalid identifier." Code provider 904 ". Previous version of IDE works pretty well. What is the problem?
Oracle SQL Developer 4.1.0.19
Version 4.1.0.19
Build a HAND - 19.07

It seems that OBJECT_ID added to ALL_PROCEDURES for the 10g DB version, but after the version you have (10.2.0.1.0). I don't have a link to the documentation specific to hand Oracle, but see the last comment by Steven Feuerstein in the next blog...

PL/SQL challenge: ALL_PROCEDURES changes over version (5980)

Typically when generation SQL for a particular version of the DB with SQL Developer, only major (10) and (more rarely) secondary numbers (2) gets checked, if your problem is one of those borderline cases that are easy to miss and less likely to get fixed. Whenever a customer has a specific need to use an older version, Oracle expects usually only the last set of patch (for example, 10.2.0.5) would be used.

SDO ORA-00904 identifier valid after patch 20544696 and 20225988 (CPU Apr 15)

The seller of our web mapping system uses a syntax that contains the identifier SDO_GEOM. SDO_GEOMETRY and similar. An example simplified using the point constructor ODD as in...
Select sdo_geom.sdo_geometry (2001, 81989, sdo_geom.sdo_point_type (531599, 184530, null), null, null) double;
This syntax has stopped working in the TEST database, after I applied the patches April 2015 CPU. It generates an ORA-00904: "SDO_GEOM. "" SDO_GEOMETRY ': identifier not valid, which in fact I was expecting. The package SDO_GEOM in schema MDSYS, often referenced without the option scheme by the public synonym, do not contain a type or function SDO_GEOMETRY. I've never used this syntax and wrote instead...
Select mdsys.sdo_geometry (2001, 81989, mdsys.sdo_point_type (531599, 184530, null), null, null) double;
.. of course, who continues to work. However, to my surprise, I found that the syntax of the provider, which generates the ORA-00904 in all databases of fix post, works perfectly well in all our pre patch databases.
Is the same for all other types in the MDSYS (SDO_ELEM_INFO_ARRAY, SDO_ORDINATE_ARRAY...) schema.
I'm dealing with the strange situation where I not only understand why something has stopped working; first of all I do not understand why the syntax of the seller has already worked.
We are using Oracle 11.2.0.4 EE with Oracle Spatial on Windows Server 2008 R2 64-bit. Patches that have been requested are
1) patch 20544696: WINDOWS DB BUNDLE PATCH 11.2. 0.4.15
2) patch 20225988: WINDOWS ORACLE JAVAVM COMPONENT BUNDLE PATCH 11.2. 0.4.3
Kind regards
Torsten

Hi Torsten,

Well, here you have a kind of strange thing Oracle Spatial. If you told me that
```
SELECT SDO_GEOM.SDO_GEOMETRY(2001, 81989, SDO_GEOM.SDO_POINT_TYPE(531599, 184530, NULL), NULL, NULL) FROM dual;
```
is a valid statement, I'd say of course not. But on my production server which is the power supply 11.2.0.4.5, it works!

However, on a 12 c test server it does not work.

All I can say is that you are right in everything you say. Oracle has removed everything that made this weird syntax once the work and it seems that the PSU April stops for good. Your provider needs to fix things and perhaps address why they used such a weird thing in the first place.

Like you I don't see what makes this function on 11g. There is no synonym that I see. And if wrap you it in an anonymous block fails
```
DECLARE
   foo SDO_GEOMETRY;
BEGIN
   SELECT SDO_GEOM.SDO_GEOMETRY(2001,81989,SDO_GEOM.SDO_POINT_TYPE(531599,184530,NULL),NULL,NULL)
   INTO foo
   FROM dual;
END;
/
```
Strange thing indeed. I guess there could be a wider discussion here on what patches are in turn brought in 11g and if the side effects are always worth.

See you soon,.

Paul

Please, I have the following question on the foreign key and the ora-00904
Thanks in advance!

I created the table:

Create the Department table
(
DNAME varchar (15) NOT NULL,
deptID number (5) NOT NULL,
Primary key (dname, deptid)
)

then...

Create table Manager
(
MgrID number (10) not null,
Not null, name varchar (10)
Start_date date not null,
Primary key (mgrid),

CONSTRAINT fk_department
FOREIGN KEY (dname, deptip)
Department of REFERENCES (dname, deptid)
)

Trying to create the table with the constraint, it yeilds one:

ORA-00904: "DNAME": invalid identifier
+.. .with an asterisk under "dname" in line: FOREIGN KEY (dname, deptip) +.

I tried joining my name of the column with quotation marks ("" "); capitalized for consistency; and we tried creating and editing then - all to nothing will do. I also tried to use the user interface with Oracle Express Edition and the moment where I click on create, the same error appears. Could someone help please straighten out me up - was this threat for four days.

Thanks again!
Hello

Welcome to the forum!

Columns that will reference the other table must be declared just like all the other columns; including the names in a FOREIGN KEY constraint is not auotmatically define them.
It works:
```
CREATE TABLE Manager
(       mgrid          NUMBER (10)     NOT NULL,
     Name          VARCHAR (10)     NOT NULL,
     Start_date      DATE          NOT NULL,
     dname          VARCHAR2 (15),               -- New
     deptid          NUMBER (5),               -- New
PRIMARY KEY (mgrid),
     --
CONSTRAINT fk_department
FOREIGN KEY           (dname, deptid)
REFERENCES department (dname, deptid)
);
```
(assuming that the departments table, you posted, there).

Is there a reason why you use VARCHAR instead of VARCHAR2?

In the departments table, do you really need both dname and deptid in the primary key? For example, if you have a line with name = "ACCOUNTING" and deptid = 10; is it possible that you could have another line with deptid = 10 and some different dname, say 'REASEARCH '? It is more common to only have a deptid as primary key and have columns in the foreign key constraints that reference.

Search and apply reception error: ORA-00904: "ON_ACCT_PO_NUM": not valid
Hello

We get an error when you try to apply revenues, ORA-00904: "ON_ACCT_PO_NUM": invalid identifier. Found some Metalink:

Find and apply functionality Arxrwmai filled with ORA-00904: error "ON_ACCT_PO_NUM" [388202.1 ID]
ARXRWMAI: ORA-00904: "On_acct_po_num": invalid identifier, applying the reception [564612.1 ID]
ARP_PROCESS_APPLICATION is not valid - PLS-00302: component 'ON_ACCT_CUST_ID' must be declared [577194.1 ID]

Basically all suggest that the columns (IE ON_ACCT_PO_NUM) are missing in AR_RECEIVABLE_APPLICATIONS. Check these tables and columns are actually there, however, I ran SQL > @$AR_TOP/patch/115/sql/arvrrapp.sql (the version is 115.26.15104.3). And re-tested, always a problem. Audit to verify what patches have been applied recently that could cause this.

RDBMS: 11.2.0.1.0
Oracle Applications: 11.5.10.2

Thank you
-Steve
Hi steve;

Check use select * ad_bugs and check patch that applied using the applied date column

* PS: patch 5359197 is exist on your server that is mentioned on the research and apply feature Arxrwmai ends with ORA-00904: error "ON_ACCT_PO_NUM" [388202.1 ID] *.

Respect of
HELIOS

ORA-00904: "ORA_ROWSCN": invalid identifier

Get this error when trying to open tables in SQL Developer and data display.
ORA-00904: "ORA_ROWSCN": invalid identifier
Found a very old thread talking about this error, and now it's happening with me with SQL Developer Version on a Mac/Yosemite 4.1.1.19.
https://community.Oracle.com/thread/1019844
It happened for awhile and I didn't say anything because I can run a select statement * and get all the data I need. But it is bit boring so wonder if it's a bug that's resurfaced? Anyone else seeing this? Apparently not, because there seems to be no recent discussions on this subject, but maybe I'm not find them.
Earl

References to the built-in ORA_ROWSCN function should not return the message "invalid identifier" when connected to Oracle 10 g R1 or higher. When you connect to a pre - 10 g R1, uncheck the box use ORA_ROWSCN for DataEditor insert and update statements in Tools > Preferences > Database > Object Viewerr.

Edit:

Oracle 10 g or higher, tables with a policy defined on them will know it: ORA-00904: 'ORA_ROWSCN': invalid makes unusable 2.1.0.63 output

Edit2:

More information, if you wish: using ora_rowscn on a table FGAC: bug?

RMAN - 06004:ORACLE error in the recovery catalog. ORA-00904: invalid...
Hello all,.

One of our backups RMAN fails with the following error message. Any suggestions would be greatly appreciated.

==================================================================================================

From backup 2008-12-30 22:03:47
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03002: failure of the backup command to 2008-12-30 22:03:47
RMAN-06004: the recovery catalog database ORACLE error: ORA-00904: invalid identifier

RMAN >
RMAN > #BACKUP # ARCHIVELOG delete all '% d_bkp_al_ % t_Set % s_Piece %p' entry FORMAT;
2 >
3 > # DELETE ARCHIVELOG until ' SYSDATE-7 ";
4 >
5 > # check if the database can be restored
6 > RESTORE DATABASE # VALIDATE;
7 >
8 > # check if controlfile can be restored
9 > #RESTORE # CONTROLFILE to ' / backups/admin/custpr/custpr_bkp_cntlfile.ctl' VALIDATE;
10 >
11 > # check if archivelogs for these past two weeks can be restored
12 > # RESTORE ARCHIVELOG FROM TIME ' SYSDATE-7' VALIDATE ';
13 >
14 > #-check all backups on backup media are intact
15 > # CROSSCHECK BACKUP OF DATABASE;
16 >
17 > #-display based on a list of files that need to be stored on the retention
18 > policy #. For this case study, the files that do not have at least 1 backups
19 > # will be reported.
20 > REPORT NEED backup.
RMAN retention policy apply to the order
RMAN retention policy is set to 7 days recovery window
Report of the files whose recovery needs more 7 days of archived newspapers
Days of files name
---- ----- -----------------------------------------------------
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03002: failure of command report at 2008-12-30 22:03:48
RMAN-06004: the recovery catalog database ORACLE error: ORA-00904: invalid identifier

RMAN >
RMAN > #-remove unnecessary backups. This command deletes the backups based on the
2 > retention policy of #.
3 > # commented DELETE OBSOLETE - TSM not configured to remove on 68
4 > #DELETE # OBSOLETE;
5 >
6 > #-complete list of the existing backups
7 > LIST BACKUP;
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03002: failure of the list command at 2008-12-30 22:03:49
RMAN-06004: the recovery catalog database ORACLE error: ORA-00904: invalid identifier

RMAN >
RMAN > # end of file.
2 > * end-of-file *.

RMAN >

Published by: ORA_UMAIR on December 31, 2008 07:51
No help is possible.
You publish a file of newspaper only, and can not see the command that failed.
Also you include, contrary to the recommendation in the post on Forums label, the complete version number of 4-digit.
This is important because they either has an error in your script that does not find RMAN or you hit a bug.

-----
Sybrand Bakker
Senior Oracle DBA

ORA-00904: "DATA". "" AM ": invalid identifier

Hello
I am facing upwards a situation I can't find why is the error ora-00904 appears.
I wrote the request as follows:

(A)

with data as
  (
  select uc.* 
    from user_computer uc
     where computer_name like '%'||:perioxi||'%'
  )
  select uc.* 
    from user_computer uc
    where exists (select 1
                   from data
                   where data.am = uc.am)
     and exists (select 1
                      from v_misthotoi_orga
                      where uc.am = v_misthotoi_orga.matr)

Where the utilisateur_ordinateur is a table, and the v_misthotoi_orga is a db view (a view that is based on another view that is based on a table that is accessed through a dblink).
A query runs without error.

(B)

with data as
  (
  select uc.* 
    from user_computer uc
     where computer_name like '%'||:perioxi||'%'
  )
  select uc.* 
    from user_computer uc
    where exists (select 1
                   from data
                   where data.am = uc.am)                       <.... THE DATACOLUMN DATA.AM IS USED, WITHOUT ERROR                
     and exists (select 1
                      from v_misthotoi_orga
                      where data.am = v_misthotoi_orga.matr)    <.....THIS IS WHERE THE ERROR IS LOCATED (DATA.AM)

The above query (application B) stops with error: ORA-00904: "DATA". "" AM ": invalid identifier.

You can identify the cause of the error, since the datacolumn 'am' in 'data' datasource is used twice in query B.
In the first instance without any error in the second with the error.

Note: Oracle db v.2
Thank you
SIM

Hey Sim,

Change

select 1
from v_misthotoi_orga
where data.am = v_misthotoi_orga.matr

select 1
from v_misthotoi_orga,
       data  

where data.am = v_misthotoi_orga.matr

In this query, Oracle knows no data unless you specify in the From clause that he should use.

HTH,

Stefan

SQL Error: Invalid identifier ORA-00904

Hello
The Version of SQL Developer: 11g
Two tables: nav_vendors (source), vendor (destination)
Both having 16 'Same' columns (data will differ for some records of... for some data records are same to check the process DML works according to the need).
I'm trying to insert update and delete using merge operation
I m getting error below whenever I tried to merge them. All column names are the same in the table.
SQL error: ORA-00904: "S". "" COMPANY_CODE ": invalid identifier
SQL:
MERGE INTO s source
USING (nvl (d.VENDOR, s.VENDOR) selection of the SELLER,
NVL (d.Name, s.Name) NAME.
NVL (d.NAME3, s.NAME3) Name3,
NVL (d.ADDRESS1, s.ADDRESS1) address1.
NVL (d.DISTRICT, s.DISTRICT) DISTRICT.
NVL (d.CITY, s.CITY), CITY,
NVL (d.Country, s.Country) COUNTRIES.
NVL (d.Postcode, s.Postcode) ZIP Code,
NVL (d.TELEPHONE, s.TELEPHONE), PHONE,.
NVL (d.Fax, s.Fax) FAX.
NVL (d.contact, s.contact) CONTACT.
NVL (d.URL, s.URL) URL.
NVL (d.email, s.email) EMAIL.
NVL (d.DELIVERY_TOLERANCE, s.DELIVERY_TOLERANCE) DELIVERY_TOLERANCE.
NVL (d.EXCLUDE_REWORK_TEXT, s.EXCLUDE_REWORK_TEXT) EXCLUDE_REWORK_TEXT.
NVL (d.COMPANY_CODE, s.COMPANY_CODE) COMPANY_CODE.
(case
When ((d.VENDOR = s.VENDOR)
and (d.NAME = s.NAME)
and (d.NAME3 = s.NAME3)
and (d.ADDRESS1 = s.ADDRESS1)
and (d.DISTRICT = s.DISTRICT)
and (d.CITY = s.CITY)
and (d.COUNTRY = s.COUNTRY)
and (d.POSTCODE = s.POSTCODE)
and (d.TELEPHONE = s.TELEPHONE)
and (d.FAX = s.FAX)
and (d.CONTACT = s.CONTACT)
and (d.URL = s.URL)
and (d.EMAIL = s.EMAIL)
and (d.DELIVERY_TOLERANCE = s.DELIVERY_TOLERANCE)
and (d.EXCLUDE_REWORK_TEXT = s.EXCLUDE_REWORK_TEXT)
and (d.COMPANY_CODE = s.COMPANY_CODE))
then "correspondence".
When d.COMPANY_CODE is null
then 'DELETE '.
When s.COMPANY_CODE is null
then "INSERT."
on the other
"no match."
chck end)
of s nav_vendorz
full outer join of the seller d
On(d.COMPANY_CODE=s.COMPANY_CODE)
) d
(S.COMPANY_CODE = d.COMPANY_CODE AND (in d.chck ("not matched", 'match', 'DELETE')))
WHEN MATCHED THEN
->UPDATE SET s.company_code = d.company_code <-error line
WHERE in d.chck ("not matched", "DELETE")
DELETE WHERE d.chck = 'DELETE '.
WHEN NOT MATCHED THEN
INSERT (VENDOR, NAME, ADDRESS1, NAME3, NEIGHBORHOOD, CITY, COUNTRY, CODE POSTAL, PHONE, FAX, CONTACT, URL, EMAIL, DELIVERY_TOLERANCE, EXCLUDE_REWORK_TEXT, COMPANY_CODE)
VALUES
(d.VENDOR, d.NAME, d.NAME3, d.ADDRESS1, d.DISTRICT, d.CITY, d.COUNTRY, d.POSTCODE, d.TELEPHONE, d.FAX, d.CONTACT, d.URL, d.EMAIL, d.DELIVERY_TOLERANCE,d.EXCLUDE_REWORK_TEXT,d.COMPANY_CODE);/

(1) use different alias names

(2) do not try to update a column that is used to 'ON' clause.

ORA-00904: invalid identifier

Hi all

I'm getting ORA-00904: "SNO_T": invalid identifier will be done in this example. Please let me know where I have error.

create table t4(name varchar2(22),sno number);


insert into t4 values('suman2',2);
insert into t4 values('suman',1);

create or replace type t4_t as object(
 name_t  varchar2(22),
 sno_t   number
 );


create or replace type t4_m is table of t4_t;


/
declare
 l_toys t4_m;
 l1     pls_integer;
begin
 select t4_t(name_t,sno_t)  
  bulk collect into l_toys
  from t4;
-- DBMS_OUTPUT.PUT_line(l_toys.count);

 select count(*) into l1 from t4;


DBMS_OUTPUT.PUT_line(l1);


end;

Error report -
ORA-06550: line 5, column 21:
PL/SQL: ORA-00904: "SNO_T": invalid identifier
ORA-06550: line 5, column 2:
PL/SQL: SQL Statement ignored
06550. 00000 -  "line %s, column %s:\n%s"
*Cause:    Usually a PL/SQL compilation error.
*Action:

Select t4_t (name_t, sno_t)

bulk collect into l_toys

T4;

the columns in your table are called name and sno, so you must use these names in your select statement

t4_t is the manufacturer that expects two values (a string and a number) and having built an object, you will be able to access the object by using object_name.sno_t, but do not all by building this...

HTH

ORA-00904: "YYYY": invalid identifier using impdp

Hello
I am trying to import a part of a table to another table on the remote database using impdp:
Impdp directory of centrumadmin/centrumadmin = network_link DUMP_LOG_DIRECTORY LOGFILE = backup_2014_01.log = REF2ISKNE = 'AUD$ _BACKUP' content TABLES = QUERY DATA_ONLY =------"WHERE \" NTIMESTAMP # "> to_date\ (January 2, 2014","DD-MM-YYYY '------") "------"; "
But still get this error:
Start "CENTRUMADMIN". "' SYS_IMPORT_TABLE_01 ': centrumadmin / * directory = network_link DUMP_LOG_DIRECTORY LOGFILE = backup_2014_01.log = REF2ISKNE TABLES = AUD$ happy _BACKUP = DATA_ONLY QUERY =" WHERE NTIMESTAMP # > to_date (02-2014, MM-YYYY) ""
Current estimation using BLOCKS method...
Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
Total estimation using BLOCKS method: 4,473 GB
ORA-31693: Data Table object 'CENTRUMADMIN '. "" AUD$ _BACKUP "could not load/unload and being ignored because of the error:
ORA-00904: "YYYY": invalid identifier
Work "CENTRUMADMIN". "" SYS_IMPORT_TABLE_01 "completed with error (s 1) to Wed Feb 11 09:32:15 2015 elapsed 0 00:00:03
Any ideas? If I change the date format YYYY-MM-DD or the other, always error is in the last part: ORA-00904: "DD": invalid identifier.
Thank you.
Honza

Hi Mika,

have you played around with some double 'or triple?

as

to_date\ ("02/01/2014","DD-MM-YYYY"------)-«;»

concerning

Kay

ORA-00904: "PCT_DB_TIME": invalid identifier

Hello
on 11.2.0.4 on Win 2008
I got when running:
SQL > SELECT EVENT, n.WAIT_CLASS,.
TIME_WAITED_MICRO, ROUND(TIME_WAITED_MICRO*100/S.DBTIME,1) 2 PCT_DB_TIME
3. IN V$ SYSTEM_EVENT E, V$ EVENT_NAME N,.
4 (SELECT the DBTIME OF the V VALUE $ SYS_TIME_MODEL WHERE STAT_NAME = 'DB time') S
5. WHERE E.EVENT_ID = N.EVENT_ID
6 AND N.WAIT_CLASS NOT IN ('inactive', ' E/s system') and PCT_DB_TIME <>0
7 ORDER BY PCT_DB_TIME ASC;
AND N.WAIT_CLASS NOT IN ('inactive', ' E/s system') and PCT_DB_TIME <>0
*
ERROR on line 6:
ORA-00904: "PCT_DB_TIME": invalid identifier
Thanks for the help.

This is an invalid identifier because you cannot use a column assigned in the application to the location alias WHERE clause or ORDER BY in the same query. You have two options to rewrite this query:

SELECT EVENT, n.WAIT_CLASS,
TIME_WAITED_MICRO, ROUND(TIME_WAITED_MICRO*100/S.DBTIME,1) PCT_DB_TIME
V $ SYSTEM_EVENT E, V$ EVENT_NAME N,.
(SELECT the DBTIME VALUE OF V$ SYS_TIME_MODEL WHERE STAT_NAME = "DB time") S
WHERE E.EVENT_ID = N.EVENT_ID
AND N.WAIT_CLASS NOT IN ('Idle', ' E/s system') and ROUND(TIME_WAITED_MICRO*100/S.DBTIME,1) <> 0
ORDER BY ROUND(TIME_WAITED_MICRO*100/S.DBTIME,1) ASC;

and

SELECT * from
(SELECT EVENT, n.WAIT_CLASS,
TIME_WAITED_MICRO, ROUND(TIME_WAITED_MICRO*100/S.DBTIME,1) PCT_DB_TIME
V $ SYSTEM_EVENT E, V$ EVENT_NAME N,.
(SELECT the DBTIME VALUE OF V$ SYS_TIME_MODEL WHERE STAT_NAME = "DB time") S
WHERE E.EVENT_ID = N.EVENT_ID
AND N.WAIT_CLASS NOT IN ('Idle', ' E/s system'))
where PCT_DB_TIME <> 0
ORDER BY PCT_DB_TIME ASC;

Both work.

David Fitzjarrell

ORA 00904: invalid identifier "JAN".

Hello
I have the rest of the table.
===========================================
create table ATT_ATTENDANCESHEET as
(
Select 1 empid, to_date('21/01/2014','dd/mm/yyyy') prdate, 240 reg, 0 unpaid all double union
Select 2, to_date (January 21, 2014 ', ' dd/mm/yyyy'), 200 reg, 0 unpaid all double union
Select 3, to_date (January 21, 2014 ', ' dd/mm/yyyy'), 240 reg, 0 unpaid all double union
Select option 4, to_date (January 21, 2014 ', ' dd/mm/yyyy'), 480 reg, 0 unpaid all double union
Select 5, to_date (January 21, 2014 ', ' dd/mm/yyyy'), 240 reg, unpaid double 0
);
=================================================
I want to remove rows from table ATT_ATTENDANCESHEET.
If the parameter passed empids, lines for employees would be eliminated.
If empids is null, all records between the given period will be deleted.
I created after the procedure to that effect.
------------------------------------------------------

CREATE or replace FUNCTION deleteAttendanceDetails (startdate DATE, enddate DATE, empids varchar2) RETURN NUMBER as

n number;

condition varchar2 (200);

vsql varchar2 (2000);

BEGIN

IF empids is not null

THEN

condition: condition = |' and empid in ('| empids |') ' ;

END IF;

vsql: =' delete from ATT_ATTENDANCESHEET where prdate between ' | StartDate | 'and' | EndDate | condition;

EXECUTE IMMEDIATE (vsql);

return n;

END;

/

The empids parameter contains the employee IDS separated by commas.
for example
"1,2,3,4"
-----------------------------------------------------------
But when I call this function using
Select deleteAttendanceDetails (to_date('25/01/2014','dd/mm/yyyy'), to_date (' 01/31/2014 ',' dd/mm/yyyy'), ") double;
I get the following error
ORA 00904: invalid identifier "JAN".
ORA-06512: at.. .line 21
I use oracle 10g.
Help, please

Do not use dynamic sql. It's more trouble that it's worth.

Your error comes from the fact that you convert a date to a string, implicitly and then come back.

In addition, your example doesn't have a field of prddate... so I added that, in my test table so that it works.

Try something like that, entirely avoid dynamic sql:
```
CREATE or replace FUNCTION deleteAttendanceDetails (
                              startdate DATE,
                              enddate DATE,
                              empids varchar2
                           )
   RETURN NUMBER
as
   n number;
BEGIN
   delete from ATT_ATTENDANCESHEET
      where ( empid IS NULL
            OR empid in ( select regexp_substr ( empids, '[^,]+', 1, level) empid
                         from dual connect by level <= (LENGTH(empids) - LENGTH(REPLACE(empids, ',')) + 1)
                      )
            )
        and prdate between nvl(startdate, to_date('01-jan-1900','dd-mon-yyyy'))
                       and nvl(enddate  , to_date('01-jan-5000','dd-mon-yyyy'));

  return n;  -- what is "n" ?
END;
/
```
Not really sure what you want to do with "n"... you have nothing in your code... so I did the same

bug: Houston-27122 and ORA-00904

Similar Questions

Maybe you are looking for