ORA-00904 when exporting job queues

Hi!
I have a 8.1.6.3.7 database (although you only see 8.1.6.3.0) when you log in) which I'm trying to export.
Everything is fine until the time comes to export job queues. I then get the following error messages:
EXP-00008: ORACLE error 904 encountered
ORA-00904: invalid column name
EXP-00000: Export terminated unsuccessfully
Now, I've just spent my morning looking through the discussion forums to see if anyone else had this error, but no luck.
What I've done:
- Rerun catexp: no change
- ensured that I'm running the same version of the RDBMS and export (v8.1.6.3(.7) and 8.1.6.3.0): ok?
Any ideas anyone?
Thanks,
Kevin

Hi Prathmesh,
in fact I saw this very thread before and I made sure that both solutions were applied. Moreover as I said patch 6991626 had already been applied earlier, precisley to fix this problem, and I've had been able to successfully export other albeit somewhat smaller schemas (500M instead of 3GB) in the last few months. This is why I was so puzzled to see that exact bug raise its ugly head again. As far as I can tell I didn't do any modification to the DB since that last patch in nov. 2009. In fact the DB has been running pretty much untouched since then.
I even tried yestereday to reinstalled the patch again; opatch does the operation gracefully, first rolling back the patch then reapplying it again, with only a warning about the patch being already present. However the pb does not get fixed any better.
Thanks a lot for your help,
Chris

Similar Messages

[Designer 10.1.2.0.2] ORA-00904 on EXPORT

Im getting errors on export with Repository Administration Utility :
Connected to: Oracle Database 10g Release 10.1.0.2.0 - Production
Export done in WE8ISO8859P1 character set and AL16UTF16 NCHAR character set
Note: grants on tables/views/sequences/roles will not be exported
. exporting pre-schema procedural objects and actions
. exporting foreign function library names for user DESIGNER
. exporting PUBLIC type synonyms
. exporting private type synonyms
. exporting object type definitions for user DESIGNER
About to export DESIGNER's objects ...
. exporting database links
. exporting sequence numbers
. exporting cluster definitions
. about to export DESIGNER's tables via Conventional Path ...
. . exporting table CDDL_TMP_TBL 0 rows exported
EXP-00056: ORACLE error 904 encountered
ORA-00904: "SYS"."DBMS_EXPORT_EXTENSION"."FUNC_INDEX_DEFAULT" : identificateur non valide
. . exporting table CDI_CLASS_SET_CODE_TYPES 5 rows exported
. . exporting table CDI_CODE_SECTION_TYPES 5 rows exported
. . exporting table CDI_DELTAB 0 rows exported
. . exporting table CDI_DFLT_USER_PREFS 1102 rows exported
EXP-00056: ORACLE error 904 encountered
ORA-00904: "SYS"."DBMS_EXPORT_EXTENSION"."FUNC_INDEX_DEFAULT" : identificateur non valide
. . exporting table CDI_DFLT_USER_PREF_USAGES 1159 rows exported
EXP-00056: ORACLE error 904 encountered
ORA-00904: "SYS"."DBMS_EXPORT_EXTENSION"."FUNC_INDEX_DEFAULT" : identificateur non valide
. . exporting table CDI_FORMS 29 rows exported
EXP-00056: ORACLE error 904 encountered
ORA-00904: "SYS"."DBMS_EXPORT_EXTENSION"."FUNC_INDEX_DEFAULT" : identificateur non valide
. . exporting table CDI_FUNNET 0 rows exported
. . exporting table CDI_GENERATION_TARGETS 2 rows exported
. . exporting table CDI_GEN_TARGET_PROPERTIES 2 rows exported
. . exporting table CDI_LANGUAGE_DEFINITIONS 20 rows exported
EXP-00056: ORACLE error 904 encountered
ORA-00904: "SYS"."DBMS_EXPORT_EXTENSION"."FUNC_INDEX_DEFAULT" : identificateur non valide
. . exporting table CDI_MODNET 0 rows exported
. . exporting table CDI_NAV 126 rows exported
EXP-00056: ORACLE error 904 encountered
ORA-00904: "SYS"."DBMS_EXPORT_EXTENSION"."FUNC_INDEX_DEFAULT" : identificateur non valide
. . exporting table UPG_SDD_UES 0 rows exported
EXP-00056: ORACLE error 904 encountered
ORA-00904: "SYS"."DBMS_EXPORT_EXTENSION"."FUNC_INDEX_DEFAULT" : identificateur non valide
. . exporting table UPG_SDW_ACCESS_RIGHTS 8 rows exported
. exporting synonyms
. exporting views
. exporting stored procedures
. exporting operators
. exporting referential integrity constraints
. exporting triggers
. exporting indextypes
. exporting bitmap, functional and extensible indexes
. exporting posttables actions
. exporting materialized views
. exporting snapshot logs
. exporting job queues
. exporting refresh groups and children
. exporting dimensions
. exporting post-schema procedural objects and actions
. exporting statistics
Export terminated successfully with warnings.
Ive used search without success !
Does someboby know what it is about ?
Thks
.

The error could be due to mismatch between the database version and the import/export utility. You have a 10.1.0.2.0 DB but the version of the imp/exp utilities supplied along with Designer 10.1.2.0.2 is 10.1.0.4. You could use 9i imp/exp utilities and export. Another possible method would be to export all workareas in the repository from the RON.
-Praveen

ORA-00604 ORA-00904 When query partitioned table with partitioned indexes

Got ORA-00604 ORA-00904 When query partitioned table with partitioned indexes in the data warehouse environment.
Query runs fine when query the partitioned table without partitioned indexes.
Here is the query.
SELECT al2.vdc_name, al7.model_series_name, COUNT (DISTINCT (al1.vin)),
al27.accessory_code
FROM vlc.veh_vdc_accessorization_fact al1,
vlc.vdc_dim al2,
vlc.model_attribute_dim al7,
vlc.ppo_list_dim al18,
vlc.ppo_list_indiv_type_dim al23,
vlc.accy_type_dim al27
WHERE ( al2.vdc_id = al1.vdc_location_id
AND al7.model_attribute_id = al1.model_attribute_id
AND al18.mydppolist_id = al1.ppo_list_id
AND al23.mydppolist_id = al18.mydppolist_id
AND al23.mydaccytyp_id = al27.mydaccytyp_id
AND ( al7.model_series_name IN ('SCION TC', 'SCION XA', 'SCION XB')
AND al2.vdc_name IN
('PORT OF BALTIMORE',
'PORT OF JACKSONVILLE - LEXUS',
'PORT OF LONG BEACH',
'PORT OF NEWARK',
'PORT OF PORTLAND'
AND al27.accessory_code IN ('42', '43', '44', '45')
GROUP BY al2.vdc_name, al7.model_series_name, al27.accessory_code

I would recommend that you post this at the following OTN forum:
Database - General
General Database Discussions
and perhaps at:
Oracle Warehouse Builder
Warehouse Builder
The Oracle OLAP forum typically does not cover general data warehousing topics.

ORA-00904 when using export

I am trying to run the export utility (NT machine) to export specified tables to a dmp file. The export starts but does not complete successfully due to the ORA-00904 error for having an invalid column name. I looked at the tables I've tried to export and the column names are valid (less than or equal to 30 characters and alphanumeric).
This is the params file I am using:
TABLES=(EMP)
LOG=bob.log
INDEXES=Y
ROWS=Y
COMPRESS=Y
FEEDBACK=10
FILESIZE=100K
FILE=bob.dmp
any information is much appreciated
Thanks

Marco,
I was trying to run the export on an 8.1.7 client machine on an 8.1.6 database. I ran the export on the database server machine locally and it worked fine. It looks like I need to get the versions on the clients to match the database. Thanks for your help.

ORA-39126 when exporting with expdp

Hi there,
I'm getting a crash on 11g 11.1.0.7 when exporting a schema using expdp:
expdp
Connected to: Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Estimate in progress using BLOCKS method...
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
Total estimation using BLOCKS method: 3.096 GB
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA [TABLE_DATA:"NSNPL"."SYS_EXPORT_SCHEMA_02"]
ORA-22813: operand value exceeds system limits
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 7839
----- PL/SQL Call Stack -----
object      line object
handle    number name
0x14d81a160     18237 package body SYS.KUPW$WORKER
0x14d81a160      7866 package body SYS.KUPW$WORKER
0x14d81a160      2744 package body SYS.KUPW$WORKER
0x14d81a160      8504 package body SYS.KUPW$WORKER
0x14d81a160      1545 package body SYS.KUPW$WORKER
0x14d81db88         2 anonymous block
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA []
ORA-22813: operand value exceeds system limits
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 86
ORA-06512: at "SYS.KUPW$WORKER", line 7834
----- PL/SQL Call Stack -----
object      line object
handle    number name
0x14d81a160     18237 package body SYS.KUPW$WORKER
0x14d81a160      7866 package body SYS.KUPW$WORKER
0x14d81a160      2744 package body SYS.KUPW$WORKER
0x14d81a160      8504 package body SYS.KUPW$WORKER
0x14d81a160      1545 package body SYS.KUPW$WORKER
0x14d81db88         2 anonymous block
Job "NSNPL"."SYS_EXPORT_SCHEMA_03" stopped due to fatal error at 00:57:23
This look awfully similar to bug 6991626 (cf ID 737618.1), however the database has already been successfully patched (and in fact even repatched) for this bug:
$ORACLE_HOME/OPatch/opatch lsinventory
Invoking OPatch 11.1.0.6.2
Oracle Interim Patch Installer version 11.1.0.6.2
Copyright (c) 2007, Oracle Corporation. All rights reserved.
Oracle Home       : /opt/oracle/db11g
Central Inventory : /opt/oracle/inventory
   from           : /etc/oraInst.loc
OPatch version    : 11.1.0.6.2
OUI version       : 11.1.0.7.0
OUI location      : /opt/oracle/db11g/oui
Log file location : /opt/oracle/db11g/cfgtoollogs/opatch/opatch2010-06-02_08-23-53AM.log
Lsinventory Output file location : /opt/oracle/db11g/cfgtoollogs/opatch/lsinv/lsinventory2010-06-02_08-23-53AM.txt
Installed Top-level Products (2):
Oracle Database 11g                                                  11.1.0.6.0
Oracle Database 11g Patch Set 1                                      11.1.0.7.0
There are 2 products installed in this Oracle Home.
Interim patches (6) :
Patch 6991626      : applied on Tue Jun 01 22:35:32 WET 2010
   Created on 14 Oct 2008, 23:25:07 hrs PST8PDT
   Bugs fixed:
     6991626
[...]Does anyone have an idea on what might be the culprit here?
Thanks for your help,
Chris

Hi Prathmesh,
in fact I saw this very thread before and I made sure that both solutions were applied. Moreover as I said patch 6991626 had already been applied earlier, precisley to fix this problem, and I've had been able to successfully export other albeit somewhat smaller schemas (500M instead of 3GB) in the last few months. This is why I was so puzzled to see that exact bug raise its ugly head again. As far as I can tell I didn't do any modification to the DB since that last patch in nov. 2009. In fact the DB has been running pretty much untouched since then.
I even tried yestereday to reinstalled the patch again; opatch does the operation gracefully, first rolling back the patch then reapplying it again, with only a warning about the patch being already present. However the pb does not get fixed any better.
Thanks a lot for your help,
Chris

1.5.4 ora-00904 when opening a package from the connections navigator

Hi
I downloaded 1.5.4 for windows and immediately checked to see if this long standing bug has been fixed
1.5.0.53 New file types not opened as plsql (and now neither a
However it hasn't so next thing I do is go the connections navigator to open a package which is the workaround for the above bug (any update on when that is going to be fixed would be appreciated).
If I double click to open a package I get an error message
ORA-00904: "ATTRIBUTE": invalid identifier
A single click on a package does not give any error. Double clicking on the same package in 1.5.1 does not give any error message
Any ideas?
thanks
paul
Edited by: paul.schweiger on Mar 4, 2009 10:36 AM
Stupidly used the rich text editor which doesn't seem to work too well

JB,
There actually is a post from the team in this thread ;-)
The patch on 3/30 was not scheduled to fix any other errors other than the import issue we encountered. We included an LDAP fix and a 9i performance query issue. The exact bugs fixed are listed in the check for updates detail before you download the fix.
All bugs can be logged with Metalink, that is the primary place for logging and tracking bugs. The forum is for discussions on how to use the product - for pointers and advice.
Paul,
By your long standing bug, I assume you mean that .pks, pkb and .plb files are opened in the PL/SQL Editor. This has been fixed in 1.5.4.
What has not been done and has been scheduled for 2.0 is the ability to associate any extension with a file and then open that file with the pl/sql editor.
For all encountering the ora-00904 error, this is specifically related to opening PL/SQL in a 9i database and we have a bug logged for that.
Sue

Error ORA-00904 when trying to update

I am trying to update one table with values from another table. This is how I am trying to do this
UPDATE TOMBSTONE T
SET T._PACKAGE=(SELECT A.PACKAGE from RISK A)
WHERE T.ID=A.ID
When I try to execute this query I get error "ORA-00904 "A"."ID" : invalid identifier"
What do I do wrong?
Thanks
Message was edited by:
user459138

Wrong syntax.
Try
UPDATE TOMBSTONE T
SET T._PACKAGE=(SELECT A.PACKAGE from RISK A WHERE T.ID=A.ID)
WHERE EXISTS (SELECT 1 FROM RISK A WHERE T.ID=A.ID)
Rgds.

ORA-00904 when use column alias in Record Group Query

Is it possible to use column aliases in Record Group Queries?
I have a query that runs fine in SQL*Developer, but gives me runtime errors when I use it as a Record Group Query.
When I use it as a Record Group Query, the Form compiles, but at runtime I receive the following errors:
FRM-40502: ORACLE error: unable to read list of values
when I use Help - Display Error, I see:
ORA-00904:"CHILDNAME":invalid identifier
The query is something like this
select decode(complex stuff here) as "childname" ....
I've tried it with and without the double quotes surrounding the alias name, and have also tried it without using the "as" keyword.
I would appreciate any suggestions or insights. I'm using Forms 9.0.4.
Thanks.

It looks like this is caused by bug 725059:
"FILTER BEFORE DISPLAY" DOESN'T WORK IF LOV HAS COLUMN ALIASES (TRIAGE1098)
My LOV does have the Filter Before Display turned on. Here's the text of the bug:
IF an LOV is created with column aliases in the select statement, (eg: select ename emp_name from emp) and the LOV property "Filter Before Display" is "Yes", THEN when you attempt to filter the LOV at runtime, (eg: type '%' then press the 'Find' button) the internal WHERE clause that forms sends to the database is: WHERE column_alias LIKE '%%' This is incorrect syntax. A client-side sqlnet trace shows this. The correct syntax should be: WHERE column LIKE '%%' . The incorrect syntax results in no rows returned. However no error is displayed by forms to the user.

Ora-00904 when creating a view

Hello everyone,
I'm trying to create a view based on 6 tables, and I'm getting an ORA-00904: Invalid column name error. I also tried to do a basic select * from table_name and inserted one of the restrictions in my where clause and am getting the same error. I've checked and re-checked the column names in my script.
Can anything else be causing this error?
Rose

CREATE OR REPLACE VIEW GEN_VISTA_VW (PERSON_ID,
LAST_NAME, MIDDLE_NAME, FIRST_NAME, ADDRESS, LINE2, LINE3, COMMUNITY, POSTAL_CODE, HOME_PHONE, BUS_PHONE, PROVINCE, HOME_SCHOOL_ID, EMPNO, POSITION, REG_NUMB)
AS (SELECT
          PERSON.PERSON_ID,
          PERSON.LAST_NAME,
          PERSON.MIDDLE_NAME,
          PERSON.FIRST_NAME,
          PERADDR.LINE1,
          PERADDR.LINE2,
          PERADDR.LINE3,
          PERADDR.CITY,
          PERADDR.ZIP,
          PERPHONE.PHONE_NO,
          TBLLOC.PHONE_NO,
          PERADDR.STATE,
          TBLLOC.LOCATION_CODE,
          EMPCOMP.EMPNO,
          TBLPOS.POSITION_TITLE,
          EMPQUAL.REG_NUMB
     FROM
          PERSON,
          PERADDR,
          PERPHONE,
          TBLLOC,
          TBLPOS,
          EMPCOMP,
          EMPQUAL
     WHERE
          person.person_id = tblpos.person_id
AND person.person_id = perphone.person_id
     AND person.person_id = peraddr.person_id
     AND person.person_id = empqual.person_id
     AND person.person_id = empcomp.person_id
     AND tblpos.location_code = tblloc.location_code)
Thank you

ORA-00904 when execute query

Similar to the SRDemo Search and Results on the same page example, if I put in an invalid query in a numeric field such as "> ddd", I get the error ORA-00904: "DDD": invalid identifier. If I hit my Clear Criteria button (Delete action), I get the same message three times. I get the three messages no matter how many times I hit the button.
If I manually clear the field and hit the button, I get two of the above messages and the result iterator shows many rows which are all blank.
A couple of questions:
What is the best way to validate the query before it is executed?
I want to avoid too much coding and I can modify the error message if needed. Is there another way to reset the the query form?
Using JDev 10.1.3.2.0 ADF BC
Thanks,
Tom

Thanks Tif. I will definitely bookmark this link.
However, my users are not that sophisticated. I really need a form based query.
The error is easily reproducible. Just go to the SRDemo application and to the Advanced Search tab. Put in any non-numeric character in the Request field and click Find. Click the Clear button to clear the query and you'll get the ORA error several times. You'll keep getting those errors no matter how many times you click it.
Now, blank out the value you entered in the Request field and hit Clear again. You'll get the ORA errors again but you'll also see the Results table fill with rows but they will all be blank.
I really like the QBE feature (it gives the user flexibility with little coding from me) but I need a way (easily, hopefully) to trap the error and to be able to clear the query.
I'm fairly new to JDev so I may be missing something obvious here.
Thanks,
Tom

RME-02105 AND ORA-00955 WHEN EXPORTING APPLICATION SYSTEM

WHEN TRYING TO EXPORT APPLICATION SYSTEM FROM RON.
and after resbonding to the messsage "Export tables are already populated,you want to clear them?" by "yes" ,I RECIEVED THE ABOVE ERRORS .
I USE ORACLE databse 8.1.7 with Oracle Designer 6i Version 6.5.52.1.0.
is ther any help?

OK,
I have read the link and I have talked with our DBA. He says taht we are working with a 9.2 (9.2.0.7 exactly) version. In this version he believes taht the only way to use the flashback query feature was through the use of the utility package DBMS_FLASHBACK. Therefore, the sentence ALTER database flashback that would work on a 10g version off does'nt have sense on 9.2.
Anyone knows how to avoid the flashback error in a 9.2 environment?

Ora-01555 when export DB on RAC 11GR2

Hi all,
I run a full export on my 11GR2 DB and i have 6 errors on sysman tables :
ORA-31693: Table data object "SYSMAN"."MGMT_POLICY_ASSOC_EVAL_SUMM" failed to load/unload and is being skipped due to error:
ORA-02354: error in exporting/importing data
ORA-01555: snapshot too old: rollback segment number 21 with name "_SYSSMU21_2772229671$" too small
Do you have an idea ?
Thanks.

$ oerr ora 1555
01555, 00000, "snapshot too old: rollback segment number %s with name \"%s\" too small"
// *Cause: rollback records needed by a reader for consistent read are
// overwritten by other writers
// *Action: If in Automatic Undo Management mode, increase undo_retention
// setting. Otherwise, use larger rollback segmentsIf you increase undo_retention parameter you may also need to increase undo tablespace datafiles.

Oracle 8i full export fails (ORA-00904)

Hello Guru's.
I encounter this problem when i try a full export.
Database version is 8.1.7.4 and the export utility is also 8.1.7.4
When i try exporting it generates a ORA-00904 error. I traced on this error and see the following:
*** SESSION ID:(8.57) 2007-03-21 10:33:53.738
*** 2007-03-21 10:33:53.738
ksedmp: internal or fatal error
ORA-00904: invalid column name
Current SQL statement for this session:
SELECT GRANTOR, GRANTORID, GRANTEE, PRIV, WGO, ISDIR, TYPE FROM SYS.EXU8GRN WHERE OBJID = :1 ORDER BY WGO DESC, SEQUENCE
I checked the compatible parameter:
(compatible string 8.1.7)
Any reply greatly appreciated.

Yeah, well, maybe running catexp.sql will solve that .....
And it did.
But more stuff is coming up, proberly when i try to import this thingie into Oracle 10g.
Thanks, and reply!

Import/Export Jobs Fail - ORA-01017 Invalid UserName/PW - Solved!

Every time I try to run either an Import or Export Job from OEM it always fails with ORA-01017 Invalid UserName/PW.
I have read numerous posts in this forum on related topics.
Suggestion have been;
1. Make sure OS login is a member of the ORA_DBA group.
2. Make sure the OS user has the ability to logon as batch job.
3. Make sure the ORACLE_SID and ORACLE_HOME are set.
4. Make sure to set up Preferred Credentials on the Preferences page.
4. On and on and on.
I am using Oracle Version 10.2.0.1.0 On Windows 2003 Server Enterprise SP1.
When I installed the DB using Oracle Universal Installer it asks what Password you would like to assign to SYS, SYSTEM etc. I used the following password "AvT_$651#JK" which it accepted without problem. The installation completed and I am able to log into OEM using SYS/AvT_$651#JK (SYSDBA) or SYSTEM/AvT_$651#JK (Normal).
I then proceed to "import from export files" a schema from a previously "export to export files" that was created on another host using the same Oracle Version 10.2.0.1.0 On Windows 2003 Server Enterprise SP1. This job always fails with "ORA-01017 Invalid UserName/PW" even though the username and pw are correct!
Turns out the password itself is the problem, apparently some part of the process (RMAN??) does not like the special characters in the PW. Changing the PW to "testpw1" worked.
Using Oracle Universal Installer should have prevented me from using a password that violated this policy.
BG...

Does you provide username under local security policy along with domainname like
abc\uo.cok ? If not, please enter username along with domainname and let me know the result. If possible aste eventviewer log for this connection

"ORA-00904: "POLTYP": invalid identifier" in export

First I got errors when I did the export with an export tool of Release 11.1.0.7.0 and there were lot of ORA-00904 and ORA-01003 like the following:
XP-00008: ORACLE error 904 encountered
ORA-00904: "MAXSIZE": invalid identifier
. . exporting table XRATE_INFO
EXP-00008: ORACLE error 1003 encountered
ORA-01003: no statement parsed
Then I tried to do export with another version of export tool (Release 10.2.0.4.0) The errors changed to the following:
.about to export FM's tables via Direct Path...
EXP-00008: ORACLE error 904 encountered
ORA-00904: "POLTYP": invalid identifier
EXP-00000: Export terminated unsuccessfully
The export tool I used is of Release 10.2.0.4.0
Has anyone had similar problems before?
Edited by: 910547 on Jan 26, 2012 7:31 PM

910547 wrote:
First I got errors when I did the export with an export tool of Release 11.1.0.7.0 and there were lot of ORA-00904 and ORA-01003 like the following:
XP-00008: ORACLE error 904 encountered
ORA-00904: "MAXSIZE": invalid identifier
. . exporting table XRATE_INFO
EXP-00008: ORACLE error 1003 encountered
ORA-01003: no statement parsed
Then I tried to do export with another version of export tool (Release 10.2.0.4.0) The errors changed to the following:
.about to export FM's tables via Direct Path...
EXP-00008: ORACLE error 904 encountered
ORA-00904: "POLTYP": invalid identifier
EXP-00000: Export terminated unsuccessfully
The export tool I used is of Release 10.2.0.4.0
Has anyone had similar problems before?
Edited by: 910547 on Jan 26, 2012 7:31 PMThis possibly a bug raise SR with Oracle Support

ORA-00904 when exporting job queues

Similar Messages

Maybe you are looking for