ORA-00904 after Transport

hi,
when i transport a request to the production system i get ora-00904 error. i check with developers and everything seems ok from side.
same request when transported to QA does not complaint
help will be appreciated
regards
aijaz

hi,
- the error ORA-904 means:
ORA-904 %s: invalid identifier / invalid column name
This means that, from SAP a command is sent to the oracle database indicating a wrong column.
What wou have to do is to identify
- The command with the wrong column.
- where this command is comming from
- why it has a wrong column.
There is not much we can do from a forum with the lack of informqtion provided.
In the developer trace you should see the error and the command ( usually a query )
Then you know the table. Compare the columns in the table, perhaps the table is different from the developer system.

Similar Messages

ORA-00904 After modifying table

I have a versioned table named cnstrnt. Due to the number of existing constraints, I was unable to unversion it, but had to add a column (note: bad idea #1). I ran the command "exec dbms_wm.beginddl('cnstrnt'); alter table cnstrnt_lts add (cnstrnt_num number(1) not null); " When I tried to commit, I received an error. Another error was received when rolling back. I then forced the commit using the ignore_last_error=>true (bad idea #2); I then decided that I had no choice but to unversion it (wish that I had come to this conclusion earlier); I received an error that it had a problem with the my new column. In my infinate wisdom, I tried to roll back the DB to a point in time before I started messing with the table. I did not go back far enough, and because it was open with "resetlogs", no longer have the datafiles. I was able to do a beginddl on the table, and removed the column. It commited without a problem. Now that I am trying to do a new ddl on the table (new constraint to an existing versioned table), I am receiving the ORA-00904 error stating that the cnstrnt_num column is an invalid qualifier. I see everywhere that I went wrong. Any help on getting me out of this mess?

We support all of the conditions that you list. When you need to perform DDL on a table that contains a foreign key, you need to be sure to call beginDDL and commitDDL on the tables in the appropriate order, which is outlined in the user guide. Also note that workspaces are not created for a specific table. Once a workspace is created it can be used by any user that has the necessary privileges, and any table can be modified within it.
I think the issue here is that ignore_last_error was set to true, and the statement that was ultimately skipped, was required for normal functionality. This parameter should only be used when it is safe to do so, and you know how to recover from skipping the statement.
If you do end up filing a TAR, all of this can be addressed further using your specific case/example.
Regards,
Ben

Getting ora:00904 invalid indentifier error while running i query

Hi,
I have a remote database and local database both are oracle 10gR2.Now i have written the below mentioned query in my local database and is working fine,but in case remote database it is throughing error ora:00904 invalid indentifier.
I had export the dump from remote db and import it on my local db and i tried the same and it is working fine on local after that also.
As i believe that this error usually come for column name not exist or column name or it's length or for any special character in column name of the table.But as i said it is working fine on local db but not in remote db though i am using the same dump for local and remote.
Though when i am querying the table i can able to fetch data for the any record but when i am using the below mentioned query for the same i am getting the error.As i am doing this to fecth the data for child parent related relationship.
Can any one suggest is there anything related to configaration or something else.
Please do let me know if you do want some more information on the query what i am doing inside of it.
Rgds,
Anit
Edited by: Anit A. on Sep 1, 2008 2:32 AM
Edited by: Anit A. on Sep 1, 2008 2:33 AM

WITH t
AS
SELECT decode(t.spnlevel
,3,t.u_quotesdtlid
,2,decode((select count(*)
from u_quotesdtl t2
where t2.u_quotesdtlid = t.u_quotesdtlid
and t2.parentspn = (t2.jobgroupid||':'||t2.jobtype)
),0,(select t1.u_quotesdtlid
from u_quotesdtl t1
where t1.spnitemcode = t.parentspn
and t1.spnlevel = '3'
and t1.jobtype = t.jobtype
and t1.jobgroupid = t.jobgroupid
and t1.QUOTEID = t.QUOTEID
),t.u_quotesdtlid
,1,decode((select count(*)
from u_quotesdtl t2
where t2.QUOTEID = t.QUOTEID
and t2.parentspn = (t2.jobgroupid||':'||t2.jobtype)
),0,t.u_quotesdtlid,decode((select count(*)
from u_quotesdtl t3
where t3.QUOTEID = t.QUOTEID
and t3.parentspn = (t3.jobgroupid||':'||t3.jobtype)
and t3.u_quotesdtlid in (select t1.u_quotesdtlid
from u_quotesdtl t1
where t1.spnitemcode = t.parentspn
and t1.spnlevel = '2'
and t1.jobtype = t.jobtype
and t1.jobgroupid = t.jobgroupid
and t1.QUOTEID = t.QUOTEID
),0,(select t4.u_quotesdtlid
from u_quotesdtl t4
,(select t1.parentspn
,t1.jobtype
,t1.jobgroupid
from u_quotesdtl t1
where t1.spnitemcode = t.parentspn
and t1.spnlevel = '2'
and t1.jobtype = t.jobtype
and t1.jobgroupid = t.jobgroupid
and t1.QUOTEID = t.QUOTEID
) t5
where t4.spnitemcode = t5.parentspn
and t4.spnlevel = '3'
and t4.jobtype = t5.jobtype
and t4.jobgroupid = t5.jobgroupid
and t4.QUOTEID = t.QUOTEID
(select t1.u_quotesdtlid
from u_quotesdtl t1
where t1.spnitemcode = t.parentspn
and t1.spnlevel = '2'
and t1.jobtype = t.jobtype
and t1.jobgroupid = t.jobgroupid
and t1.QUOTEID = t.QUOTEID
,null,t.u_quotesdtlid) as parentquoteid
,t.u_quotesdtlid as quotesdtlid
,t.spnlevel as spnlevel
FROM u_quotesdtl t
WHERE t.QUOTEID ='som key id'
ORDER BY parentquoteid,t.spnlevel desc
select * from t;

PL/SQL: ORA-00904: invalid identifier (DG4ODBC 11.2.0.2 & MySQL)

I have a PL/SQL script processing information between Oracle database and MySQL database. My script ran perfectly with DG4ODBC 11.1.0.7. Then we upgraded Oracle to 10.2.0 and DG4ODBC 11.2.0.2. Now if I run my script from Solaris command line like ./myscript.shl, I get the following errors:
PL/SQL: ORA-00904: "cmswhit_moodle1"."mdl_grade_grades"."finalgrade": invalid identifier
PL/SQL: ORA-00904: "cmswhit_moodle1"."mdl_question_states"."attempt": invalid identifier
The strange thing is if I run the same query by cut and paste into sqlplus from command line, the query works perfectly without any problems.
What is the cause of this problem?
Any help would be greatly appreciated.
Jeffrey

Hi Klaus,
The problem was solved after I updated MySQL ODBC to a new version from 5.1.8 to 5.1.13.
Summary of the problem and its solution:
The Problem: It appears that dg4odbc 11.2.0.2 requires a newer version of MyODBC. Previously I used MyODBC 5.1.8 which ran into problems with dg4odbc 11.20.0.2.
The Solution: After I updated MyODBC to 5.1.13, my PL/SQL scripts all work.
I need to point out that with MyODBC 5.1.8, I can run queries and updates from SQL*Plus console, but now PL/SQL scripts.
I'll close this thread.
Once again, thank you and happy holidays.
Jeffrey

Exception: java.sql.SQLException: ORA-00904: "SEQ_NAME": invalid identifier

Hi everyone,
we are facing the below issue when trying to schedule a BI report.
Error Details:
+oracle.apps.xdo.servlet.scheduler.ProcessingException: Exception [TOPLINK-4002] (Oracle TopLink - 11g Release 1 (11.1.1.0.0) (Build 080319)): oracle.toplink.exceptions.DatabaseException+
Internal Exception: java.sql.SQLException: ORA-00904: "SEQ_NAME": invalid identifier
Error Code: 904
Call: UPDATE SEQUENCE SET SEQ_COUNT = SEQ_COUNT 50 WHERE SEQ_NAME = 'JOB_ID_SEQ'+
Query: DataModifyQuery()
+     at oracle.apps.xdo.servlet.scheduler.toplink.ToplinkDataHandler.insertJob(ToplinkDataHandler.java:830)+
+     at oracle.apps.xdo.servlet.ui.scheduler.SchedulerServlet.scheduleJob(SchedulerServlet.java:1896)+
+     at oracle.apps.xdo.servlet.ui.scheduler.SchedulerServlet.doPost(SchedulerServlet.java:293)+
+     at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)+
+     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)+
+     at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)+
+     at oracle.apps.xdo.servlet.security.SecurityFilter.doFilter(SecurityFilter.java:94)+
+     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621)+
+     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)+
+     at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)+
+     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)+
+     at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:216)+
+     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:117)+
+     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:110)+
+     at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)+
+     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)+
+     at java.lang.Thread.run(Thread.java:595)+
+Caused by: Exception [TOPLINK-4002] (Oracle TopLink - 11g Release 1 (11.1.1.0.0) (Build 080319)): oracle.toplink.exceptions.DatabaseException+
Internal Exception: java.sql.SQLException: ORA-00904: "SEQ_NAME": invalid identifier
Error Code: 904
Call: UPDATE SEQUENCE SET SEQ_COUNT = SEQ_COUNT 50 WHERE SEQ_NAME = 'JOB_ID_SEQ'+
Query: DataModifyQuery()
+     at oracle.toplink.exceptions.DatabaseException.sqlException(DatabaseException.java:296)+
+     at oracle.toplink.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(DatabaseAccessor.java:724)+
+     at oracle.toplink.internal.databaseaccess.DatabaseAccessor.executeNoSelect(DatabaseAccessor.java:790)+
+     at oracle.toplink.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:524)+
+     at oracle.toplink.internal.databaseaccess.DatabaseAccessor.executeCall(DatabaseAccessor.java:467)+
+     at oracle.toplink.internal.sessions.AbstractSession.executeCall(AbstractSession.java:795)+
+     at oracle.toplink.internal.queryframework.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:193)+
+     at oracle.toplink.internal.queryframework.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:179)+
+     at oracle.toplink.internal.queryframework.DatasourceCallQueryMechanism.executeNoSelectCall(DatasourceCallQueryMechanism.java:222)+
+     at oracle.toplink.internal.queryframework.DatasourceCallQueryMechanism.executeNoSelect(DatasourceCallQueryMechanism.java:202)+
+     at oracle.toplink.queryframework.DataModifyQuery.executeDatabaseQuery(DataModifyQuery.java:55)+
+     at oracle.toplink.queryframework.DatabaseQuery.execute(DatabaseQuery.java:671)+
+     at oracle.toplink.internal.sessions.AbstractSession.internalExecuteQuery(AbstractSession.java:2260)+
+     at oracle.toplink.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1074)+
+     at oracle.toplink.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1058)+
+     at oracle.toplink.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1032)+
+     at oracle.toplink.sequencing.QuerySequence.update(QuerySequence.java:319)+
+     at oracle.toplink.sequencing.QuerySequence.updateAndSelectSequence(QuerySequence.java:258)+
+     at oracle.toplink.sequencing.StandardSequence.getGeneratedVector(StandardSequence.java:62)+
+     at oracle.toplink.sequencing.DefaultSequence.getGeneratedVector(DefaultSequence.java:144)+
+     at oracle.toplink.sequencing.Sequence.getGeneratedVector(Sequence.java:256)+
+     at oracle.toplink.internal.sequencing.SequencingManager$Preallocation_Transaction_NoAccessor_State.getNextValue(SequencingManager.java:444)+
+     at oracle.toplink.internal.sequencing.SequencingManager.getNextValue(SequencingManager.java:873)+
+     at oracle.toplink.internal.sequencing.ClientSessionSequencing.getNextValue(ClientSessionSequencing.java:75)+
+     at oracle.toplink.internal.descriptors.ObjectBuilder.assignSequenceNumber(ObjectBuilder.java:234)+
+     at oracle.toplink.internal.sessions.UnitOfWorkImpl.assignSequenceNumbers(UnitOfWorkImpl.java:419)+
+     at oracle.toplink.internal.sessions.UnitOfWorkImpl.calculateChanges(UnitOfWorkImpl.java:497)+
+     at oracle.toplink.internal.sessions.UnitOfWorkImpl.commitToDatabaseWithChangeSet(UnitOfWorkImpl.java:1407)+
+     at oracle.toplink.internal.sessions.UnitOfWorkImpl.commitRootUnitOfWork(UnitOfWorkImpl.java:1167)+
+     at oracle.toplink.internal.sessions.UnitOfWorkImpl.commit(UnitOfWorkImpl.java:939)+
+     at oracle.apps.xdo.servlet.scheduler.toplink.ToplinkDataHandler.insertJob(ToplinkDataHandler.java:815)+
+     ... 16 more+
Caused by: java.sql.SQLException: ORA-00904: "SEQ_NAME": invalid identifier
+     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:138)+
+     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:316)+
+     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:282)+
+     at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:639)+
+     at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:113)+
+     at oracle.jdbc.driver.T4CStatement.execute_for_rows(T4CStatement.java:561)+
+     at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1161)+
+     at oracle.jdbc.driver.OracleStatement.executeUpdate(OracleStatement.java:1585)+
+     at oracle.toplink.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(DatabaseAccessor.java:713)+
+     ... 45 more+
Found a thread related to this but there it was explained that the error was occuring when trying to notify regarding output through email. In our case, issue is occuring just during scheduling itslef.
Also I haved checked the following schedular tables in my database.
SQL> select table_name from all_tables where table_name like 'S_NQ%'
+2 /+
TABLE_NAME
S_NQ_ERR_MSG
S_NQ_INSTANCE
S_NQ_JOB_PARAM
S_NQ_JOB
SQL> select SEQ_NAME.CURRVAL FROM DUAL;
select SEQ_NAME.CURRVAL FROM DUAL
*+
ERROR at line 1:
ORA-02289: sequence does not exist
Please help me out in solving this as I have tried almost all possible solutions.
Thanks,
Sri Harsha.
Edited by: user10545574 on Dec 20, 2009 10:24 PM

Hello,
In the delivery email configuration server page (under BI Publisher Admin Tab), the username / password to enter is the one defined on the email server itself. It is the user that will be user to send the emails when scedhuling a report.
It may not be Administrator/ Administrator (not a user defined with OBI admin tool) but the username/password defined on the email server itself.
Moreover, to properly configure the BI Publisher Scheduler, it is a prerequistes to create bipsched user on Oracle DB and install the schema tables in Oracle DB (by clicking on Install Schema button after defining database connection under Admin / Scheduler Configuration tab)
From the error your are getting 'SEQ_NAME unknown..., it appears that the tables are not created'.
Hope this helps and good luck
Matthieu

ORA-00904: invalid column name in select query by using abstract datatype

Hi,
I had created abstract datatype as PERSON_TY and ADDRESS_TY ,
after inserting the record . i'm tryng to select the column but i got the error , even i refferd all those thing. they are given that same please look this finde me a result.
SQL> DESC PERSON_TY
Name Null? Type
NAME VARCHAR2(25)
ADDRESS ADDRESS_TY
SQL> DESC ADDRESS_TY
Name Null? Type
STREET VARCHAR2(30)
CITY VARCHAR2(25)
STATE CHAR(2)
COUNTRY VARCHAR2(15)
SQL> SELECT * FROM EMPLOYE
2 ;
EMP_CODE
PERSON(NAME, ADDRESS(STREET, CITY, STATE, COUNTRY))
10
PERSON_TY('VENKAT', ADDRESS_TY('112: BLUE MOUNT', 'CHENNAI', 'TN', 'INDIA'))
20
PERSON_TY('SRINI', ADDRESS_TY('144: GREEN GARDEN', 'THAMBARAM', 'TN', 'INDIA'))
SQL> SELECT PERSON.NAME FROM EMPLOYE
2 ;
SELECT PERSON.NAME FROM EMPLOYE
ERROR at line 1:
ORA-00904: invalid column name
regards
venki

SELECT PERSON.NAME FROM EMPLOYEIf you look in the documentation, you will see that we need to alias the table in order to make this work:
select e.person.name from employees e
/Cheers, APC
Blog : http://radiofreetooting.blogspot.com

Getting ORA-00904 whle running a procedure!

hi ,
the following procedure is meant for getting the details which has name of the user tables alone along with number of columns,but am getting -ERROR IN BLOCK:::ORA-00904: "tablename": invalid identifier.
DECLARE
v_cols NUMBER:=0;
cursor c is SELECT table_name FROM user_tables ORDER BY table_name;
BEGIN
FOR rec IN c
LOOP
v_cols:=0;
EXECUTE IMMEDIATE 'select count(COLUMN_NAME) from all_col_comments where TABLE_NAME in ('||rec.table_name||') group by TABLE_NAME' INTO v_num_rows;
DBMS_OUTPUT.PUT_LINE (RPAD (rec.table_name, 32) || LPAD (v_num_rows, 9));
END LOOP;
DBMS_OUTPUT.PUT_LINE ('-------------------End_of_Script-------------------');
EXCEPTION
WHEN OTHERS THEN
DBMS_OUTPUT.PUT_LINE('ERROR IN BLOCK:::'||SQLERRM);
END;
if there anything needs to change in procedure ,let me know.

DECLARE
       v_cols NUMBER:=0;
       cursor c is SELECT table_name FROM user_tables ORDER BY table_name;
BEGIN
       FOR rec IN c
      LOOP
          v_cols:=0;
      EXECUTE IMMEDIATE 'select count(COLUMN_NAME) from all_col_comments where TABLE_NAME in ('''||rec.table_name||''') group by TABLE_NAME' INTO v_num_rows;      ------> Added '' before and After Table Name to allow Oracle to consider as String
          DBMS_OUTPUT.PUT_LINE (RPAD (rec.table_name, 32) || LPAD (v_num_rows, 9));
      END LOOP;
      DBMS_OUTPUT.PUT_LINE ('-------------------End_of_Script-------------------');
EXCEPTION
WHEN OTHERS THEN
DBMS_OUTPUT.PUT_LINE('ERROR IN BLOCK:::'||SQLERRM);
END;You can use below version using Parameter Binding (Untested!!!)
DECLARE
       v_cols NUMBER:=0;
       cursor c is SELECT table_name FROM user_tables ORDER BY table_name;
BEGIN
       FOR rec IN c
      LOOP
          v_cols:=0;
      EXECUTE IMMEDIATE 'select count(COLUMN_NAME) from all_col_comments where TABLE_NAME in (:1) group by TABLE_NAME' INTO v_num_rows using rec.table_name;
          DBMS_OUTPUT.PUT_LINE (RPAD (rec.table_name, 32) || LPAD (v_num_rows, 9));
      END LOOP;
      DBMS_OUTPUT.PUT_LINE ('-------------------End_of_Script-------------------');
EXCEPTION
WHEN OTHERS THEN
DBMS_OUTPUT.PUT_LINE('ERROR IN BLOCK:::'||SQLERRM);
END;

RMAN-06004:ORACLE error from recovery catalog ... ORA-00904: : invalid ...

Good Morning All,
One of our RMAN backups is failing with the following error message. Any suggestions would be greatly appreciated.
==================================================================================================
Starting backup at 12/30/2008 22:03:47
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 12/30/2008 22:03:47
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> ##BACKUP ARCHIVELOG ALL FORMAT '%d_bkp_al_%t_Set%s_Piece%p' delete input;
2>
3> # DELETE ARCHIVELOG UNTIL TIME 'SYSDATE-7';
4>
5> # check if 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 the past two weeks can be restored
12> # RESTORE ARCHIVELOG FROM TIME 'SYSDATE-7' VALIDATE;
13>
14> # - Verify all backups on backup media are intact
15> # CROSSCHECK BACKUP OF DATABASE;
16>
17> # - Display a list of files that need to be backed up based on the retention
18> # policy. For this case study, files that don't have at least 1 backups
19> # will be reported.
20> REPORT NEED BACKUP;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 7 days
Report of files whose recovery needs more than 7 days of archived logs
File Days Name
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of report command at 12/30/2008 22:03:48
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> # - delete un-necessary backups. This command deletes backups based on the
2> # retention policy.
3> ######### commented out DELETE OBSOLETE - TSM not configured to delete on 68
4> #########DELETE OBSOLETE;
5>
6> # - get complete list of existing backups
7> LIST BACKUP;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of list command at 12/30/2008 22:03:49
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> #-end of file-
2> **end-of-file**
RMAN>
Edited by: ORA_UMAIR on Dec 31, 2008 7:51 AM

This Oracle Database is 9.2.0.6.0. Here is the complete log file. The RMAN script that I am using ran successfully many times before.
====================================================================================================
Recovery Manager: Release 9.2.0.6.0 - 64bit Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
RMAN>
connected to recovery catalog database
RMAN>
connected to target database: CUSTPR (DBID=525071053)
RMAN>
RMAN> #########################################################################
2> # LEVEL 0 BACKUP #
3> #########################################################################
4>
5> # Configure backups to be written to disk.
6> CONFIGURE DEFAULT DEVICE TYPE TO DISK;
old RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
new RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Set the retention policy to a recovery window of 7 days. This ensures that
2> # RMAN retains all backups needed to recover the database to any point in time
3> # in the last 7 days. You can use the DELETE OBSOLETE command to delete
4> # backups that are no longer required by the retention policy. To exclude a
5> # backup from consideration by the policy, you can use KEEP option with the
6> # BACKUP command.
7> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
old RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to use two disk channels for backup, restore, recovery, and
2> # maintenance operations.
3> CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
old RMAN configuration parameters:
CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
new RMAN configuration parameters:
CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to write disk backups to the /backup directory.
2> # The format specifier %t is replaced with a 4-byte timestamp, %s with the
3> # backup set number, and %p with the backup piece number.
4> CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
old RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
new RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to back up the control file after each backup.
2> CONFIGURE CONTROLFILE AUTOBACKUP ON;
old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to write controlfile autobackups to the /backup directory.
2> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Enable the backup optimization feature introduced in 9i to make sure that
2> # RMAN won't backup an archivelog or datafile if there already exists a backup
3> # of that file. The FORCE option can be used to override optimization on a
4> # specific BACKUP command.
5> CONFIGURE BACKUP OPTIMIZATION ON;
old RMAN configuration parameters:
CONFIGURE BACKUP OPTIMIZATION ON;
new RMAN configuration parameters:
CONFIGURE BACKUP OPTIMIZATION ON;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Use the SHOW ALL command to see the current configuration settings.
2> SHOW ALL ;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%d_bkp_cf%F';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 1;
CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' FORMAT '%d_bkp_df%t_Set%s_Piece%p';
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/orahome2/custprdb/9.2.0/dbs/snapcf_custpr.f'; # default
RMAN>
RMAN> # The following commands are run each day to start the backup cycle.
2> # The steps are:
3> # - Take an incremental level 0 backup of the database. A level 0 backup is
4> # a complete backup of the entire file which can be used as the basis
5> # for a subsequent incremental backup.
6> # - Backup all archivelogs that have not already been backed up.
7> # - Delete on-disk archivelogs older than seven days.
8>
9> BACKUP INCREMENTAL LEVEL 0 FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p'
10> DATABASE maxsetsize 33G
11> PLUS ARCHIVELOG FORMAT '/backups/admin/custpr/%d_bkp_al%t_Set%s_Piece%p'
12> delete all input;
Starting backup at 12/30/2008 22:01:40
current log archived
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=11 devtype=DISK
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=8008 recid=7910 stamp=674638862
input archive log thread=1 sequence=8009 recid=7911 stamp=674671207
input archive log thread=1 sequence=8010 recid=7912 stamp=674697380
input archive log thread=1 sequence=8011 recid=7913 stamp=674780433
input archive log thread=1 sequence=8012 recid=7914 stamp=674784211
input archive log thread=1 sequence=8013 recid=7915 stamp=674863288
input archive log thread=1 sequence=8014 recid=7916 stamp=674863300
channel ORA_DISK_1: starting piece 1 at 12/30/2008 22:01:41
channel ORA_DISK_1: finished piece 1 at 12/30/2008 22:03:47
piece handle=/backups/admin/custpr/CUSTPR_bkp_al674863300_Set3083_Piece1 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:02:07
channel ORA_DISK_1: deleting archive log(s)
archive log filename=/custpr/arch/arch_custpr_8008.log recid=7910 stamp=674638862
archive log filename=/custpr/arch/arch_custpr_8009.log recid=7911 stamp=674671207
archive log filename=/custpr/arch/arch_custpr_8010.log recid=7912 stamp=674697380
archive log filename=/custpr/arch/arch_custpr_8011.log recid=7913 stamp=674780433
archive log filename=/custpr/arch/arch_custpr_8012.log recid=7914 stamp=674784211
archive log filename=/custpr/arch/arch_custpr_8013.log recid=7915 stamp=674863288
archive log filename=/custpr/arch/arch_custpr_8014.log recid=7916 stamp=674863300
Finished backup at 12/30/2008 22:03:47
Starting backup at 12/30/2008 22:03:47
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 12/30/2008 22:03:47
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> ##BACKUP ARCHIVELOG ALL FORMAT '%d_bkp_al_%t_Set%s_Piece%p' delete input;
2>
3> # DELETE ARCHIVELOG UNTIL TIME 'SYSDATE-7';
4>
5> # check if 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 the past two weeks can be restored
12> # RESTORE ARCHIVELOG FROM TIME 'SYSDATE-7' VALIDATE;
13>
14> # - Verify all backups on backup media are intact
15> # CROSSCHECK BACKUP OF DATABASE;
16>
17> # - Display a list of files that need to be backed up based on the retention
18> # policy. For this case study, files that don't have at least 1 backups
19> # will be reported.
20> REPORT NEED BACKUP;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 7 days
Report of files whose recovery needs more than 7 days of archived logs
File Days Name
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of report command at 12/30/2008 22:03:48
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> # - delete un-necessary backups. This command deletes backups based on the
2> # retention policy.
3> ######### commented out DELETE OBSOLETE - TSM not configured to delete on 68
4> #########DELETE OBSOLETE;
5>
6> # - get complete list of existing backups
7> LIST BACKUP;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of list command at 12/30/2008 22:03:49
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> #-end of file-
2> **end-of-file**
RMAN>
Recovery Manager complete.

ORA-00904 in Merge statement

I encountered with ORA-00904 in Merge statement. I fixed the error but I don't know why. Would you please help me explain it? Thanks in advance. The following is the detail description of my question.
I have two tables TBL_A<col1 integer,col2 integer> TBL_B<col1 integer,col2 integer> and an anonymous block to test executed in Oracle 10gR2.
DECLARE
V_NUM INTEGER;
BEGIN
V_NUM := 1;
/*merge I it's okay.the function of merge seems meaningless, please pay attention to its grammar*/
MERGE INTO TBL_A A
USING (SELECT V_NUM N, COL1, COL2 FROM TBL_B) B
ON (A.COL1 = B.N)
WHEN MATCHED THEN
UPDATE SET A.COL2 = B.COL2;
/*merge II*/
/*ora-00904*/
MERGE INTO TBL_A A
USING (SELECT V_NUM, COL1, COL2 FROM TBL_B) B
ON (A.COL1 = V_NUM)
WHEN MATCHED THEN
UPDATE
SET A.COL2 = B.COL2;
/*merge III is okay*/
MERGE INTO TBL_A A
USING (SELECT COL1, COL2 FROM TBL_B) B
ON (A.COL1 = V_NUM)
WHEN MATCHED THEN
UPDATE
SET A.COL2 = B.COL2;
COMMIT;
END;
I traced the 904 error and it seems the point is in the binding of variable V_NUM. But I don't know the exact reason. I think maybe it relates with the parse of PL/SQL. Would someone please help me or give me some hints?

hi,
When you saye,
   MERGE INTO TBL_A A
    USING (SELECT V_NUM,
                  COL1,
                  COL2
             FROM TBL_B) B
       ON (A.COL1 = V_NUM)
   WHEN MATCHED
   THEN
      UPDATE SET A.COL2 = B.COL2;
In the above for ON (A.COL1 = V_NUM)
oracle treats v_num as a variable in the procedure rather than v_num returned from using clause.
So you need to alias that.
MERGE INTO TBL_A A
    USING (SELECT V_NUM as somecol,
                  COL1,
                  COL2
             FROM TBL_B) B
       ON (A.COL1 = b.somecol)
   WHEN MATCHED
   THEN
      UPDATE SET A.COL2 = B.COL2;Edited by: Ganesh Srivatsav on May 12, 2011 11:42 AM
Added alias after peter pointed out for variable in the using.

EA3 Why does unit test end with ORA-00904

Database version
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL Developer version
Oracle IDE 4.0.0.12.27
Java(TM) Platform 1.7.0_25
Error message:
An error was encountered performing the requested operation:
ORA-00904: : ugyldig identifikator
00904. 00000 - "%s: invalid identifier"
*Cause:
*Action:
Vendor code 904
Whenever I go into the "Unit Test" modules, create a "Suite," and then click on that Suite, I get the error message.
I get that same error when pulling up a unit test. I am able to run the unit test, it completes successfully, but I also get that same error mentioned above.
The test is calling a simple pl/sql function (returning Hello World). The finction is in the same schema as the user running the test.
Is this is a known bug?
Message was edited by: dori The following message appears in the console: Exception while performing action Run Test java.lang.NullPointerException at oracle.dbtools.unit_test.locking.LockManager.lock(LockManager.java:64) at oracle.dbtools.unit_test.editor.UtEditor.obtainEditLock(UtEditor.java:429) at oracle.dbtools.unit_test.editor.UtTestEditor.updateContent(UtTestEditor.java:135) at oracle.dbtools.unit_test.navigator.UtNavigatorContextMenu.showEditor(UtNavigatorContextMenu.java:2711) at oracle.dbtools.unit_test.navigator.UtNavigatorContextMenu.openElement(UtNavigatorContextMenu.java:2638) at oracle.dbtools.unit_test.navigator.UtNavigatorContextMenu.run(UtNavigatorContextMenu.java:616) at oracle.dbtools.unit_test.navigator.UtNavigatorContextMenu.runTest(UtNavigatorContextMenu.java:577) at oracle.dbtools.unit_test.navigator.UtNavigatorContextMenu.handleEvent(UtNavigatorContextMenu.java:2374) at oracle.ideimpl.controller.MetaClassController.handleEvent(MetaClassController.java:53) at oracle.ide.controller.IdeAction$ControllerDelegatingController.handleEvent(IdeAction.java:1482) at oracle.ide.controller.IdeAction.performAction(IdeAction.java:663) at oracle.ide.controller.IdeAction.actionPerformedImpl(IdeAction.java:1153) at oracle.ide.controller.IdeAction.actionPerformed(IdeAction.java:618) at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:2018) at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2341) at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:402) at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:259) at javax.swing.AbstractButton.doClick(AbstractButton.java:376) at javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:833) at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:877) at java.awt.Component.processMouseEvent(Component.java:6505) at javax.swing.JComponent.processMouseEvent(JComponent.java:3321) at java.awt.Component.processEvent(Component.java:6270) at java.awt.Container.processEvent(Container.java:2229) at java.awt.Component.dispatchEventImpl(Component.java:4861) at java.awt.Container.dispatchEventImpl(Container.java:2287) at java.awt.Component.dispatchEvent(Component.java:4687) at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4832) at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4492) at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4422) at java.awt.Container.dispatchEventImpl(Container.java:2273) at java.awt.Window.dispatchEventImpl(Window.java:2719) at java.awt.Component.dispatchEvent(Component.java:4687) at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:735) at java.awt.EventQueue.access$200(EventQueue.java:103) at java.awt.EventQueue$3.run(EventQueue.java:694) at java.awt.EventQueue$3.run(EventQueue.java:692) at java.security.AccessController.doPrivileged(Native Method) at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76) at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:87) at java.awt.EventQueue$4.run(EventQueue.java:708) at java.awt.EventQueue$4.run(EventQueue.java:706) at java.security.AccessController.doPrivileged(Native Method) at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76) at java.awt.EventQueue.dispatchEvent(EventQueue.java:705) at oracle.javatools.internal.ui.EventQueueWrapper._dispatchEvent(EventQueueWrapper.java:169) at oracle.javatools.internal.ui.EventQueueWrapper.dispatchEvent(EventQueueWrapper.java:151) at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:242) at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:161) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:150) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:146) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:138) at java.awt.EventDispatchThread.run(EventDispatchThread.java:91)

I'm experiencing the same problem. I've called AppleCare repeatedly for a solutiuon, but I haven't gotten an answer yet and like you above I removed just about anything I could think of. I'd like to start considering third party apps we might have installed that maybe to blame.
Why? Because I installed a fresh copy of Lion onto a Class 10 SD card and then later I turned on full disk encryption there. I no longer experienced the problem after I booted from that card.
I also experienced a problem with full disk encryption with my 2010 MacBook Air sitting doing nothing at the encryption login screen. It spontaneously restarted three times before I turned it off. Later I moved to a 2011 model and did not see the spontaneously restarts again.
Now I'm stuck with this annoying double login.

Problem with theme service after transport to QAS

Hi,
when i click the link on BSP page inside portal, iam getting following error. the link is working outside portal.
its working on dev r/3 and portal. i got the problem after transport of the package to QAS, i checked all the services and alla are active.
http://XXXXXXX:7035/irj/portalapps/com.sap.portal.design.portaldesigndata/themes/portal/main_theme/controls call was terminated because the corresponding service is not available.
Theme is active and its applied for every user, i have 30 BSP pages in portal and only this page is showing this error, this page will be launched as popup from portal.
Thanks in Advance,
Damodhar.

SQL> exec dbms_xdb.sethttpport(8080);
BEGIN dbms_xdb.sethttpport(8080); END;
ERROR at line 1:
ORA-06550: line 1, column 7:
PLS-00201: identifier 'DBMS_XDB' must be declared
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
another one...........

When i add CMR between 2 CMP, it show ORA-00904

i create 2 "CMP from table" without foreign key. i can create both instance by home.create() . after i add CMR between both. i can create master but can't create detail. when i create the detail, it show ORA-00904.
anyone can help me?
master table is
CREATE TABLE KAY_TMP_1 (
ID VARCHAR2 (2) NOT NULL,
KAY_NUM NUMBER (9,2),
KAY_NAME VARCHAR2 (10),
KAY_DATE DATE,
PRIMARY KEY ( ID ) ) ;
detail table is
CREATE TABLE KAY_TMP_2 (
ID2 VARCHAR2 (2) NOT NULL,
SUB_ID2 VARCHAR2 (2) NOT NULL,
KAY_NAME2 VARCHAR2 (10),
PRIMARY KEY ( ID2, SUB_ID2 ) ) ;
ejb-jar.xml
<?xml version = '1.0' encoding = 'GBK'?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar>
<enterprise-beans>
<entity>
<description>Entity Bean ( CMP )</description>
<display-name>Kay_tmp_2</display-name>
<ejb-name>Kay_tmp_2</ejb-name>
<home>fehd.web.util.Kay_tmp_2Home</home>
<remote>fehd.web.util.Kay_tmp_2</remote>
<local-home>fehd.web.util.Kay_tmp_2LocalHome</local-home>
<local>fehd.web.util.Kay_tmp_2Local</local>
<ejb-class>fehd.web.util.impl.Kay_tmp_2Bean</ejb-class>
<persistence-type>Container</persistence-type>
<prim-key-class>fehd.web.util.Kay_tmp_2PK</prim-key-class>
<reentrant>False</reentrant>
<cmp-version>2.x</cmp-version>
<abstract-schema-name>Kay_tmp_2</abstract-schema-name>
<cmp-field>
<field-name>id2</field-name>
</cmp-field>
<cmp-field>
<field-name>sub_id2</field-name>
</cmp-field>
<cmp-field>
<field-name>kay_name2</field-name>
</cmp-field>
</entity>
<entity>
<description>Entity Bean ( CMP )</description>
<display-name>Kay_tmp_1</display-name>
<ejb-name>Kay_tmp_1</ejb-name>
<home>fehd.web.util.Kay_tmp_1Home</home>
<remote>fehd.web.util.Kay_tmp_1</remote>
<local-home>fehd.web.util.Kay_tmp_1LocalHome</local-home>
<local>fehd.web.util.Kay_tmp_1Local</local>
<ejb-class>kaytmp.Kay_tmp_1Bean</ejb-class>
<persistence-type>Container</persistence-type>
<prim-key-class>java.lang.String</prim-key-class>
<reentrant>False</reentrant>
<cmp-version>2.x</cmp-version>
<abstract-schema-name>Kay_tmp_1</abstract-schema-name>
<cmp-field>
<field-name>id</field-name>
</cmp-field>
<cmp-field>
<field-name>kay_num</field-name>
</cmp-field>
<cmp-field>
<field-name>kay_name</field-name>
</cmp-field>
<cmp-field>
<field-name>kay_date</field-name>
</cmp-field>
<primkey-field>id</primkey-field>
</entity>
<relationships>
<ejb-relation>
<ejb-relation-name>kayTmp1_kayTmp2</ejb-relation-name>
<ejb-relationship-role>
<ejb-relationship-role-name>kayTmp1-have-many-KayTmp2</ejb-relationship-role-name>
<multiplicity>One</multiplicity>
<cascade-delete/>
<relationship-role-source>
<ejb-name>Kay_tmp_1</ejb-name>
</relationship-role-source>
<cmr-field>
<cmr-field-name>kayTmp2</cmr-field-name>
<cmr-field-type>java.util.Collection</cmr-field-type>
</cmr-field>
</ejb-relationship-role>
<ejb-relationship-role>
<multiplicity>Many</multiplicity>
<relationship-role-source>
<ejb-name>Kay_tmp_2</ejb-name>
</relationship-role-source>
</ejb-relationship-role>
</ejb-relation>
</relationships>
</ejb-jar>
orion-ejb-jar.xml
<?xml version = '1.0' encoding = 'GBK'?>
<!DOCTYPE orion-ejb-jar PUBLIC "-//Evermind//DTD Enterprise JavaBeans 1.1 runtime//EN" "http://xmlns.oracle.com/ias/dtds/orion-ejb-jar.dtd">
<orion-ejb-jar>
<enterprise-beans>
<entity-deployment name="Kay_tmp_1" copy-by-value="false" data-source="jdbc/iasdbDS" exclusive-write-access="false" table="KAY_TMP_1">
<primkey-mapping>
<cmp-field-mapping name="id" persistence-name="ID" persistence-type="VARCHAR2(2)"/>
</primkey-mapping>
<cmp-field-mapping name="id" persistence-name="ID" persistence-type="VARCHAR2(2)"/>
<cmp-field-mapping name="kay_num" persistence-name="KAY_NUM" persistence-type="NUMBER(9,2)"/>
<cmp-field-mapping name="kay_name" persistence-name="KAY_NAME" persistence-type="VARCHAR2(10)"/>
<cmp-field-mapping name="kay_date" persistence-name="KAY_DATE" persistence-type="DATE"/>
</entity-deployment>
<entity-deployment name="Kay_tmp_2" copy-by-value="false" data-source="jdbc/iasdbDS" exclusive-write-access="false" table="KAY_TMP_2">
<primkey-mapping>
<cmp-field-mapping>
<fields>
<cmp-field-mapping name="id2" persistence-name="ID2" persistence-type="VARCHAR2(2)"/>
<cmp-field-mapping name="sub_id2" persistence-name="SUB_ID2" persistence-type="VARCHAR2(2)"/>
</fields>
</cmp-field-mapping>
</primkey-mapping>
<cmp-field-mapping name="id2" persistence-name="ID2" persistence-type="VARCHAR2(2)"/>
<cmp-field-mapping name="sub_id2" persistence-name="SUB_ID2" persistence-type="VARCHAR2(2)"/>
<cmp-field-mapping name="kay_name2" persistence-name="KAY_NAME2" persistence-type="VARCHAR2(10)"/>
</entity-deployment>
</enterprise-beans>
<assembly-descriptor>
<default-method-access>
<security-role-mapping impliesAll="true" name="<default-ejb-caller-role>"/>
</default-method-access>
</assembly-descriptor>
</orion-ejb-jar>

Have a look at the orion-ejb-jar.xml which is generated by oc4j in the application-deployments dir.
Oc4j takes your orion-ejb-jar.xml and generates its own basing on your version.
In the generated file you should be able to see the select statements which will be executed.

Internal : java.sql.SQLSyntaExceptionxErrorException: ORA-00904: "TENANT_ID

I had to refresh my view to the latest label. After I did the ade refresh -latest, I got this label:
FMWTOOLS_11.1.1.6.0_GENERIC_120112.0037.2_PATCHES4FA_11.1.1.6.2_PLATFORMS
this label also updated the JDeveloper to 11.1.1.6. I was using before 11.1.5.
The problem is that now I cannot run composites that were running with no issues before the upgrade.
This error is shown in the console after starting the SOA server, without even trying to run anything at all.
soa_server1] [ERROR] [] [oracle.soa.mediator.common.listener] [tid: Workmanager: , Version: 0, Scheduled=false, Started=false, Wait time: 0 ms\n] [ecid: 889cfef60875ddb5:-530c4ecd:135e2d7308b:-8000-0000000000000003,0] [APP: soa-infra] DBLocker caught exception while retrieving locked messages. Will retry retrieval after 2 seconds[[
Local Exception Stack:
Exception [TOPLINK-4002] (Oracle TopLink - 11g Release 1 (11.1.1.6.0) (Build 111018)): oracle.toplink.exceptions.DatabaseException
Internal Exception: java.sql.SQLSyntaxErrorException: ORA-00904: "TENANT_ID": invalid identifier
Error Code: 904
Call: SELECT CASE_ID, CONTAINER_ID, DUMMY1, MSG_ID, COMPONENT_DN, OPERATION, CREATION_DATE, PRIORITY, COMPONENT_STATUS, QNAME_LOCAL_PART, CASE_INFO, QNAME_NAMESPACE, LOCK_TIME, SOURCE_URI, TENANT_ID, INSTANCE_CREATED, IS_EVENT, STATUS FROM MEDIATOR_DEFERRED_MESSAGE WHERE (((STATUS = ?) AND (LOCK_TIME = ?)) AND (CONTAINER_ID = ?))
bind => [1, 2012-03-05 04:59:22.978, 56B16AC166BF11E1AF4DC30F777D0670]
Query: ReadAllQuery(oracle.tip.mediator.common.persistence.MediatorDeferredMessage)
at oracle.toplink.exceptions.DatabaseException.sqlException
My environment:
is a VM with Linux
I am using the standalone weblogic
running SOA composites.
Is this a Database Issue?
Any help would be appreciated.
Thanks
Edited by: user721265 on Mar 9, 2012 5:00 AM

Hi,
Try to create the column as:
ALTER TABLE MEDIATOR_DEFERRED_MESSAGE
ADD (TENANT_ID NUMBER(18, 0) DEFAULT -1 );
The RCU does not create that column. There are two more tables that "should have" that column (or even more? ): COMPOSITE_INSTANCE and CUBE_INSTANCE.
Check this site:
http://www.oracle.com/technetwork/database/availability/oraclefmw-soa-11gr1-securefiles-1842740.pdf
Regards,
AAPDL

ORA-00904 coming because of table JOIN

I have this query which works fine, how everwhen I attempt to join the pubsched table based on schedules.areaid = pubsched.areaid it comes up with ORA-00904
telling me that the area id is invalid.
Try commenting out line 8 of the query which joins the pubsched table and it will work fine.
Line 8 uncommented blows it up.
pubsched is used to determine if a schedule is published or not. Joining pubsched is being done to eliminate non published schedules from the query results.
Just for clarification, need help making the join work.
Any help is much appreciated.
Thanks,
George
SELECT
empid,
areaid,
startpp + day_number - 1 AS startdate,NULL AS starttime,NULL AS endtime,
8 AS hours,
0 AS minutes FROM schedules s
JOIN payperiods pp ON pp.periodid = s.periodid
JOIN pubsched ps on ps.periodid = s.periodid and ps.areaid=s.areaid
UNPIVOT ( v
    FOR day_number IN (day1 AS 1,
                       day2 AS 2,
                       day3 AS 3,
                       day4 AS 4,
                       day5 AS 5,
                       day6 AS 6,
                       day7 AS 7,
                       day8 AS 8,
                       day9 AS 9,
                       day10 AS 10,
                       day11 AS 11,
                       day12 AS 12,
                       day13 AS 13,
                       day14 AS 14
WHERE UPPER(SUBSTR (v, 1, 4)) = 'SHFT';
select * from pubsched where areaid=2003 and periodid='092013';
CREATE TABLE SCHEDULES
SCHEDULEID NUMBER(12) NOT NULL,
EMPID NUMBER(12) NOT NULL,
PERIODID VARCHAR2(6 BYTE) NOT NULL,
AREAID NUMBER(12) NOT NULL,
DAY1 VARCHAR2(50 BYTE),
DAY2 VARCHAR2(50 BYTE),
DAY3 VARCHAR2(50 BYTE),
DAY4 VARCHAR2(50 BYTE),
DAY5 VARCHAR2(50 BYTE),
DAY6 VARCHAR2(50 BYTE),
DAY7 VARCHAR2(50 BYTE),
DAY8 VARCHAR2(50 BYTE),
DAY9 VARCHAR2(50 BYTE),
DAY10 VARCHAR2(50 BYTE),
DAY11 VARCHAR2(50 BYTE),
DAY12 VARCHAR2(50 BYTE),
DAY13 VARCHAR2(50 BYTE),
DAY14 VARCHAR2(50 BYTE),
NOPTIND1 INTEGER DEFAULT 0,
NOPTIND2 INTEGER DEFAULT 0,
NOPTIND3 INTEGER DEFAULT 0,
NOPTIND4 INTEGER DEFAULT 0,
NOPTIND5 INTEGER DEFAULT 0,
NOPTIND6 INTEGER DEFAULT 0,
NOPTIND7 INTEGER DEFAULT 0,
NOPTIND8 INTEGER DEFAULT 0,
NOPTIND9 INTEGER DEFAULT 0,
NOPTIND10 INTEGER DEFAULT 0,
NOPTIND11 INTEGER DEFAULT 0,
NOPTIND12 INTEGER DEFAULT 0,
NOPTIND13 INTEGER DEFAULT 0,
NOPTIND14 INTEGER DEFAULT 0
CREATE TABLE PAYPERIODS
PERIODID VARCHAR2(6 BYTE) NOT NULL,
STARTPP DATE,
ENDPP DATE
CREATE TABLE PUBSCHED
PUBSCHEDID   NUMBER(12)                       NOT NULL,
PERIODID     VARCHAR2(6 BYTE)                 NOT NULL,
PUPDATE      DATE,
PUBTHRU      DATE,
AREAID       NUMBER(12)                       NOT NULL,
PUBLISHEDBY NUMBER(12)
Insert into SCHEDULES
(SCHEDULEID, EMPID, PERIODID, AREAID, DAY1,
DAY2, DAY3, DAY4, DAY5, DAY6,
DAY7, DAY8, DAY9, DAY10, DAY11,
DAY12, DAY13, DAY14, NOPTIND1, NOPTIND2,
NOPTIND3, NOPTIND4, NOPTIND5, NOPTIND6, NOPTIND7,
NOPTIND8, NOPTIND9, NOPTIND10, NOPTIND11, NOPTIND12,
NOPTIND13, NOPTIND14)
Values
(3693744, 753738, '092013', 2003, 'X',
'SHFT<1530>', 'SHFT<1530>', '1530', '1530', '1530',
'X', 'X', '1530', '1530', 'SHFT',
'1530', '1530', 'X', 0, 0,
0, 0, 0, 0, 0,
0, 0, 0, 0, 0,
0, 0);
Insert into SCHEDULES
(SCHEDULEID, EMPID, PERIODID, AREAID, DAY1,
DAY2, DAY3, DAY4, DAY5, DAY6,
DAY7, DAY8, DAY9, DAY10, DAY11,
DAY12, DAY13, DAY14, NOPTIND1, NOPTIND2,
NOPTIND3, NOPTIND4, NOPTIND5, NOPTIND6, NOPTIND7,
NOPTIND8, NOPTIND9, NOPTIND10, NOPTIND11, NOPTIND12,
NOPTIND13, NOPTIND14)
Values
(3693745, 753740, '092013', 2003, 'X',
'SHFT<1530>', 'SHFT<1530>', '1530', 'SHFT', '1530',
'X', 'X', '1530', '1530', '1530',
'1530', '1530', 'X', 0, 0,
0, 0, 0, 0, 0,
0, 0, 0, 0, 0,
0, 0);
Insert into SCHEDULES
(SCHEDULEID, EMPID, PERIODID, AREAID, DAY1,
DAY2, DAY3, DAY4, DAY5, DAY6,
DAY7, DAY8, DAY9, DAY10, DAY11,
DAY12, DAY13, DAY14, NOPTIND1, NOPTIND2,
NOPTIND3, NOPTIND4, NOPTIND5, NOPTIND6, NOPTIND7,
NOPTIND8, NOPTIND9, NOPTIND10, NOPTIND11, NOPTIND12,
NOPTIND13, NOPTIND14)
Values
(3693746, 753748, '082013', 2003, 'X',
'SHFT<1530>', '1530', '1530', '1530', '1530',
'X', 'X', 'SHFT<1530>', '1530', 'SHFT',
'1530', '1530', 'X', 0, 0,
0, 0, 0, 0, 0,
0, 0, 0, 0, 0,
0, 0);
COMMIT;
Insert into PAYPERIODS
(PERIODID, STARTPP)
Values
('092013', TO_DATE('04/7/2013 00:00:00', 'MM/DD/YYYY HH24:MI:SS'));
COMMIT;
Insert into WMTSCHEDULER.PUBSCHED
   (PUBSCHEDID, PERIODID, PUPDATE, PUBTHRU, AREAID,
    PUBLISHEDBY)
Values
   (51372, '092013', TO_DATE('03/07/2013 11:59:17', 'MM/DD/YYYY HH24:MI:SS'), TO_DATE('04/20/2013 00:00:00', 'MM/DD/YYYY HH24:MI:SS'), 2003,
    752910);
COMMIT;
Expected Output
EMPID,AREAID,STARTDATE,STARTTIME,ENDTIME,HOURS,MINUTES
753738,2003,4/18/2013,,,8,0
753738,2003,4/9/2013,,,8,0
753738,2003,4/8/2013,,,8,0
753740,2003,4/11/2013,,,8,0
753740,2003,4/9/2013,,,8,0
753740,2003,4/8/2013,,,8,0Edited by: George H on Apr 18, 2013 8:41 AM
Edited by: George H on Apr 18, 2013 9:09 AM
Edited by: George H on Apr 18, 2013 9:10 AM
Edited by: George H on Apr 18, 2013 9:20 AM
Edited by: George H on Apr 18, 2013 9:42 AM
Edited by: George H on Apr 18, 2013 11:25 AM

Hi, George,
George H wrote:
I have this query which works fine, how everwhen I attempt to join the pubsched table based on schedules.areaid = pubsched.areaid it comes up with ORA-00904
telling me that the area id is invalid.
Try commenting out line 8 of the query which joins the pubsched table and it will work fine.If I comment out the line
JOIN pubsched ps on ps.periodid = s.periodid and ps.areaid=s.areaid then I don;'t get the error; I get "no rows selected". That's not what you want, is it?
Are you sure the sample data is correct? What are the results you want from the sample data?
SELECT
empid,
areaid,
startpp + day_number - 1 AS startdate,NULL AS starttime,NULL AS endtime,
8 AS hours,
0 AS minutes FROM schedules s
JOIN payperiods pp ON pp.periodid = s.periodid
JOIN pubsched ps on ps.periodid = s.periodid and ps.areaid=s.areaid
UNPIVOT ( v
FOR day_number IN (day1 AS 1,
day2 AS 2,
day3 AS 3,
...You may have noticed that this site normally doesn't display multiple spaces in a row.
Whenever you post formatted text (such as query results) on this site, type these 6 characters:
\(small letters only, inside curly brackets) before and after each section of formatted text, to preserve spacing.
Thanks for posting the CREATE TABLE and INSERT statements, and your query; that's very helpful.
Don't forget to post the desired results given that sample data.

ORA-00904: "ATTRIBUTE20": invalid identifier (Human Resource)

Hi
Please anybody can tell me why the error (ORA-00904: "ATTRIBUTE20": invalid identifier) come. When I am trying to query in form "Human Resource Vision Enterprise > People > Salary Management"
Regards
Makshud

Hi Makshud,
In addition to above information, you can refer the following doc for the generic reason of this error,
[OERR: ORA-904 %s: invalid identifier / invalid column name|https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=18500.1]
This could be the reason for some invalid field entry as ORA-904 coming please verify.
This is just for the information of ORA - 904, reason can only me verified after you provide the information asked by Hussein.
Thanks,
Anchorage :)

ORA-00904 after Transport

Similar Messages

Maybe you are looking for