ORA-02089: COMMIT is not allowed in a session of subordinate.

Similar Questions

• ORA-20001: DateTrack update not allowed for a record that started today

  Hello
  
  We are working on the package of integration of data for employees in our project and we fail to create the back-end employee by calling hr_employee_api.create_employee.
  
  When we try to update we have a flag that defines datetrack_update_mode as 'UPDATE' flag 'U' and 'CORRECTION' to report as 'C', we call hr_person_api.update_person to add more details of employee.
  
  I'm trying to update an old record flagged as 'U' and to the below error
  
  Error in the API in update employee ORA-20001: DateTrack update not allowed for a record that started today
  Cause: You tried to perform an effective update date of registration which begins the same day.
  Action: Change your mode of DateTrack of correction or to change your date of entry into force.
  
  But I'm trying to update the record with effective date which does not have sysdate and logically I implement to pass the datetrack_update_mode as "UPDATE" fails with the above error.
  
  Pointers on this is much appreciated.
  
  Thanks in advance.
  
  Kind regards
  Rekha.

  OK, so the effective_start_date of the line you are trying to edit is 21/03/2012

  You specify the parameter p_effective_date in 21/03/2012, i.e. the same day!

  So, you cannot use the track date "UPDATE" mode, as the smallest length of the change of the date of the AMT is 1 day. To do this, like Gillies at in an earlier answer, is to use a date-track of "CORRECTION" mode, or use another date for your p_effective_date parameter if it is appropriate.

  When the error message refers to "todays", means in fact "entry into force you have chosen.

  Hope that clarifies things for you.

  Clive

  Published by: clive_t on April 4, 2012 08:40

• ORA-02287: sequence number not allowed here

  < police = "Courier New" >
  Hello
  Why do I have this problem?
  Insert an order tab2 select tab2_seq.nextval, eng_cat from (select distinct job_det eng_cat) by 2.
  
  SQL > r
  1 * insert into tab2_seq.nextval select eng_cat select (separate eng_cat tab2
  Insert in tab2 select tab2_seq.nextval, eng_cat from (select distinct eng_cat from)
  *
  ERROR on line 1:
  ORA-02287: sequence number not allowed here
  
  Thank you and best regards,
  Human
  < / make >

  It's 'order of 2' which makes it fail. That makes no sense at all?
  Just remove the order by clause, then it works ;-)

• ORA-20009: you are not allowed to connect to this database

  Hello
  
  We have the 11.2.0.1.0 Oracle database.
  
  The DB automatically stops as well as the service stops.
  
  Verification of the alert log, here are the errors... These are continually producing the newspaper and new .trc and .trm files are created every minute.
  
  Errors in the d:\oracle\admin\fw4dev\bdump\diag\rdbms\fw4dev\fw4dev\trace\fw4dev_j000_7424.trc file:
  ORA-00604: an error has occurred at the SQL level 1 recursive
  ORA-20009: you are not allowed to connect to this database
  ORA-06512: at line 4 level
  Fri Jul 01 13:14:32 2011
  Errors in the d:\oracle\admin\fw4dev\bdump\diag\rdbms\fw4dev\fw4dev\trace\fw4dev_ora_8672.trc file:
  ORA-00604: an error has occurred at the SQL level 1 recursive
  ORA-20009: you are not allowed to connect to this database
  ORA-06512: at line 4 level
  Fri Jul 01 13:15:19 2011
  Errors in the d:\oracle\admin\fw4dev\bdump\diag\rdbms\fw4dev\fw4dev\trace\fw4dev_j000_4916.trc file:
  ORA-00604: an error has occurred at the SQL level 1 recursive
  ORA-20009: you are not allowed to connect to this database
  ORA-06512: at line 4 level
  Fri Jul 01 13:15:41 2011
  Errors in the d:\oracle\admin\fw4dev\bdump\diag\rdbms\fw4dev\fw4dev\trace\fw4dev_ora_3952.trc file:
  ORA-00604: an error has occurred at the SQL level 1 recursive
  ORA-20009: you are not allowed to connect to this database
  ORA-06512: at line 4 level
  Fri Jul 01 13:16:19 2011
  Errors in the d:\oracle\admin\fw4dev\bdump\diag\rdbms\fw4dev\fw4dev\trace\fw4dev_j000_832.trc file:
  ORA-00604: an error has occurred at the SQL level 1 recursive
  ORA-20009: you are not allowed to connect to this database
  ORA-06512: at line 4 level
  Fri Jul 01 13:17:16 2011
  Errors in the d:\oracle\admin\fw4dev\bdump\diag\rdbms\fw4dev\fw4dev\trace\fw4dev_ora_3988.trc file:
  ORA-00604: an error has occurred at the SQL level 1 recursive
  ORA-20009: you are not allowed to connect to this database
  ORA-06512: at line 4 level
  Fri Jul 01 13:17:19 2011
  Errors in the d:\oracle\admin\fw4dev\bdump\diag\rdbms\fw4dev\fw4dev\trace\fw4dev_j000_4352.trc file:
  ORA-00604: an error has occurred at the SQL level 1 recursive
  ORA-20009: you are not allowed to connect to this database
  ORA-06512: at line 4 level
  Fri Jul 01 13:18:19 2011
  Errors in the d:\oracle\admin\fw4dev\bdump\diag\rdbms\fw4dev\fw4dev\trace\fw4dev_j000_2892.trc file:
  ORA-00604: an error has occurred at the SQL level 1 recursive
  ORA-20009: you are not allowed to connect to this database
  ORA-06512: at line 4 level
  Fri Jul 01 13:19:19 2011
  Errors in the d:\oracle\admin\fw4dev\bdump\diag\rdbms\fw4dev\fw4dev\trace\fw4dev_j000_2416.trc file:
  ORA-00604: an error has occurred at the SQL level 1 recursive
  ORA-20009: you are not allowed to connect to this database
  ORA-06512: at line 4 level
  ......
  ..
  .
  
  Please go back, in case anyone has the solution for the same thing.
  
  Kind regards
  Jinisha

  Hello
  It is a 'feature' really annoying a logon trigger event is 'CONNECTION' not 'LOGON' that is to say there is a space after the opening of SESSION

  Change your query to

  Select * from dba_triggers, where triggering_event like 'LOGON '.

  And you will find it.

  See you soon,.
  Harry

• ORA-01733-virtual column not allowed here - insert using inline view

  Does anyone know why I get ORA-01733-virtual column not allowed here
  
  SQL > select * from v version $;
  
  BANNER
  --------------------------------------------------------------------------------
  Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
  PL/SQL release 11.1.0.6.0 - Production
  CORE 11.1.0.6.0 Production
  AMT for 32-bit Windows: Version 11.1.0.6.0 - Production
  NLSRTL Version 11.1.0.6.0 - Production
  
  
  
  -no error without the WITH CHECK option
  
  SQL > INSERT INTO
  2 (SELECT
  3 location_id,
  4 city
  5 l.country_id
  6 OF country c, localities, regions r l
  7 where l.country_id = c.country_id
  8 and c.region_id = r.region_id
  9 and r.region_name = 'Asia')
  10 VALUES (5500, 'Common Wansdworth', 'UK');
  
  1 line of creation.
  
  SQL > rollback;
  
  Complete restoration.
  
  
  -error with WITH CHECK OPTION
  
  
  SQL > INSERT INTO
  2 (SELECT
  3 location_id,
  4 city
  5 l.country_id
  6 OF country c, localities, regions r l
  7 where l.country_id = c.country_id
  8 and c.region_id = r.region_id
  9 and r.region_name = 'Asia' WITH CHECK OPTION)
  10 VALUES (5500, 'Common Wansdworth', 'UK');
  INSERT INTO
  *
  ERROR on line 1:
  ORA-01733: virtual column not allowed here
  
  
  
  
  I was expecting
  
  ORA-01402: discovers the violation of where WITH CHECK OPTION clause
  
  for the second. Am I missing here?

  Coskan wrote:
  Randolf

  Thanks a lot for the update of this old question
  After reading the link, I think I should ignore this error and accept him as ORA-01402

  The information that you have asked me to check me do not have an understanding of the different error types.

  Coskan,

  I didn't know this is an old thread that somehow got updated by someone else.

  Regarding your question: you're right that the output of the script is not really that useful.

  I have just run on 10.2.0.4 and in general, it seems that the output of USER_UPDATABLE_COLUMNS is incorrect regarding the views of join using the WITH CHECK OPTION.

  For example although the location_id from the TEST_V_2 column appears as non-editable (probably because of the rule that "the columns used in the join expression" cannot be modified in a join view when you use the WITH CHECK OPTION) I can run successfully your insert if statement I choose a location_id less than 2000.

  It seems that summed up the difference if you join more than two tables, you'll always get the error "ORA-01733" when you try to insert in the join with the enabled OPTION CHECK view. For example to add a third table TEST_V_2 which does not change the original view, but simply joined meaning for example COUNTRIES to LOCATIONS, will show the same behavior to throw an ORA-01733, however it works fine when the omission of the WITH CHECK OPTION.

  So overall, I tend to say it is really a limitation of the implementation and it is not actually an ORA-01402 but looks like Oracle is simply trying to tell you: Amendment No. INSERT in this possible view. Updates however seem to work, at least I can find some examples of work.

  There seems to be other restrictions of implementation with the WITH CHECK OPTION in place even when the only membership as two tables, for example when trying to join the COUNTRIES and PLACES but by selecting only in PLACES and by using a filter on the COUNTRY_ID predicate fails with ORA-01733 when this predicate is applied to the COUNTRY. COUNTRY_ID but it works if this predicate is applied to PLACES. COUNTRY_ID.

  I could imagine that Oracle has quietly added some of these restrictions with each patch set due to the angle of the case/adverse reactions encountered. I saw this for other features, too.

  Kind regards
  Randolf

  Oracle related blog stuff:
  http://Oracle-Randolf.blogspot.com/

  SQLTools ++ for Oracle (Open source Oracle GUI for Windows):
  http://www.sqltools-plusplus.org:7676 /.
  http://sourceforge.NET/projects/SQLT-pp/

• get the error ORA-30483 (window functions not allowed herevv)

  Hi all

  Oracle version: 11.2.0.2.0

  
  

  with Table_dm AS

  (select 1 month_no, "wk1" week, DM_AMT 120, 300 GRoss_Amt, Week_no 4, Gross_qty 12, 1000 dm_adj_total double

  UNion all

  Select 1 month_no, "wk2" week, DM_AMT 120, 300 GRoss_Amt, Week_no 4, Gross_qty 12, 1000 dm_adj_total double

  Union of all the

  Select 1 month_no, "wk3" week, DM_AMT 120, 300 GRoss_Amt, Week_no 4, Gross_qty 12, 1000 dm_adj_total double

  Union of all the

  Select 1 month_no, "wk4" week, DM_AMT 120, 300 GRoss_Amt, Week_no 4, Gross_qty 12, 1000 dm_adj_total double

  Union of all the

  Select 2 month_no, 'wk5"week, DM_AMT 200, 400 GRoss_Amt, Week_no 5, Gross_qty 20, 1000 dm_adj_total double

  UNion all

  Select month_no 2, "wk6" week, DM_AMT 200, 400 GRoss_Amt, Week_no 5, Gross_qty 20, 1000 dm_adj_total double

  Union of all the

  Select month_no 2, "wk7" week, DM_AMT 200, 400 GRoss_Amt, Week_no 5, Gross_qty 20, 1000 dm_adj_total double

  UNion all

  Select month_no 2, "wk8" week, DM_AMT 200, 400 GRoss_Amt, Week_no 5, Gross_qty 20, 1000 dm_adj_total double

  UNion all

  Select month_no 2, "wk9" week, DM_AMT 200, 400 GRoss_Amt, Week_no 5, Gross_qty 20, 1000 dm_adj_total double

  )

  Select month_NO, GROSS_AMT

  (select

  mONTH_NO

  sum (first_value (GROSS_AMT) more (PARTITION MONTH_NO)) Gross_amt

  of table_dm

  Month_no group

  )

  get the following error

  "ORA-30483: window functions are not allowed here."

  The value of Gross_Amt must be the total of the Group month_no gross_amt (the Gross_Amt would be the first value in each month_no

  the value of Gross_Amt must therefore 700 in this case.

  Please suggest.

  AB

  Thank you very much, SY, is really a useful solution<>

• ORA-01733: virtual column not allowed here

  UPDATE (
  SELECT callingnumber, calledcallzone, b.callzone callzone, b.ndc
            FROM (SELECT DISTINCT SUBSTR (connectedcallingnumber, 3, 3) callingnumber,
                           calledcallzone,rownum 
                      FROM rating_temp
                     WHERE calltype = 0) a,
                 (SELECT *
                    FROM callzone cc
                   WHERE LENGTH (ndc) = 3) b
           WHERE callingnumber = ndc
           )
     SET calledcallzone = callzone-----VIRTUAL COLUMN NOT ALLOWED HERE

  Published by: user8731258 on November 29, 2010 12:45 AM

  Its simple you used SEPARATE in your first view inline. And so you cannot use columns for UPDATE.

• Error ORA-02287: sequence number not allowed here

  Hello
  
  I got an error ORA-02287: unauthorized here when you run sql statement insert below sequence number.
  
  INSERT INTO SI_KEY_DBF
  (M_IDENTITY, M_REF, M_GROUP, M_, M_TYPE, M_MULTIPLE, M_START, M_END, M_PREVIOUS, M_NEXT, M_INS_DATE, M_MOD_DATE,
  M_INS_TIME, M_MOD_TIME, M_AMEND, M_LABEL, M_ENTITY, M_TRN_FAMILY, M_TRN_GROUP, M_TRN_TYPE, M_CURRENCY,
  M_O_CUR, M_NOVO, M_CRDE, M_CODE, M_USER, M_VAL_STATUS, M_STL_METHOD, M_TRD_SECT, M_COMMENT, M_MARKET,
  M_CLEARER, M_SI_TCI)
  (SELECT M_IDENTITY, (SELECT SI_KEY_DBFS.nextval FROM dual), M_GROUP, m_, M_TYPE, M_MULTIPLE, NULL, NULL, M_PREVIOUS, M_NEXT, SYSDATE, SYSDATE,
  To_Char(sysdate,'HH:mm:SS'), To_Char(SYSDATE,'HH:MM:SS'), 0, M_LABEL, M_ENTITY, M_TRN_FAMILY,.
  M_TRN_GROUP, M_TRN_TYPE, M_CURRENCY, M_O_CUR, M_NOVO, M_CRDE, M_CODE, M_USER, M_VAL_STATUS,
  M_STL_METHOD, M_TRD_SECT, M_COMMENT, M_MARKET, M_CLEARER, M_SI_TCI FROM SI_KEY_DBF WHERE M_REF IN
  (M_REF SELECT TABLE #DATA #SITRN_DBF WHERE M_HLD_AC IN (SELECT IDXOAC FROM DDINDX)))
  
  Can someone help me on how to solve this problem? Really appreciate your help. Thank you.

  >
  (SELECT M_IDENTITY, (SELECT SI_KEY_DBFS.nextval FROM dual),
  >
  You already choose to get rid of the nested select statement and simply use the value

  (SELECT M_IDENTITY, SI_KEY_DBFS.nextval, 
  

• ORA-16143: connections of RFS not allowed during or after a Terminal recovery

  Hi all
  
  I wanted to transfer primary DB archiving log of STANDBY DB by the window / given destnination
  
  After you have created the database physically Eve, I put database waiting for recovery by using the command:-change the recovery of database managed standby database disconnect from the session.
  
  After that when I ran this command: -.
  ALTER database recover managed standby database finish;
  
  After that when I tried to recover database to help given comand awaiting:-recover managed standby database.
  
  Get the error such as ORA-16143: RFS connections that are not allowed during or after a Terminal recovery
  
  I can see this error on primary DB filev alerts log
  
  I can open my database in waiting.
  
  The two Oracle: 10.2.0.4
  The two platform: RHEL 4.7
  
  Please suggest me for this, help is appreciated
  
  Published by: user1687821 on July 12, 2010 08:37

  user1687821,

  After the use of the clause to FINISH, you MUST open the standby database as PRIMARY.

  Finishing clause must be used while you're perparing to failover to your database pending.

  Which is clearly given by the error message; you did a cover of Terminal:

   ORA-16143: RFS connections not allowed during or after terminal recovery 
  

  unless you have a pending restore point until you execute the clause of finishing, you will need rebuild your watch or use it as the primary database.

  See you soon.

• Database trigger - PL/SQL: ORA-00984: column not allowed here

  I am trying to create a trigger that will update a table of audit used when a row is changed. Using a sequence number to assign an identifier unique to each line as it is created. Need to capture the user ID, date modified and action (update), the image of the front line.
  

  CREATE SEQUENCE emp_audit_seq START WITH 10;                

  Create table emp (
     empno       NUMBER(4)      Primary Key,
     ename       VARCHAR2(10),
     job            VARCHAR2(9),
     mgr           NUMBER(4),
     hiredate     DATE,
     sal             NUMBER(7,2),
     comm        NUMBER(7,2),
     deptno       NUMBER(2));

  CREATE TABLE emp_audit   (
       audit_uid          NUMBER(15)      Primary Key,
       change_date          DATE,
       change_user          VARCHAR2(30),
       action                  CHAR(1),
       empno                  NUMBER(4),
       ename                  VARCHAR2(10),          
       job               VARCHAR2(9),
       mgr               NUMBER(4),
       hiredate          DATE,
       sal               NUMBER(7,2),
       comm                  NUMBER(7,2),
       deptno                  NUMBER(2));

  CREATE OR REPLACE TRIGGER trig_emp_audit
    BEFORE UPDATE ON emp
    FOR EACH ROW
  BEGIN
    INSERT INTO emp_audit
      VALUES(emp_audit_seq.nextval, change_date, change_user, action, :old.empno, :old.ename, :old.job, :old.mgr, :old.hiredate, :old.sal, :old.comm, deptno);
  END;
  /
  
  Warning: Trigger created with compilation errors.
  
  SQL> show errors
  Errors for TRIGGER TRIG_EMP_AUDIT:
  
  LINE/COL ERROR
  -------- -----------------------------------------------
  2/3      PL/SQL: SQL Statement ignored
  3/149    PL/SQL: ORA-00984: column not allowed here

  Can someone help to help me find what I'm doing wrong with the trigger?
  
  Published by: LostNoob on August 25, 2012 14:24

  First of all, when you write an INSERT statement, it is always good for the columns that you insert in the list. Which makes the code easier to follow - you do not have separately pull toward the top of the table definition to know what order of columns is inserted. And it makes the code easier to manage because the declaration become invalid if you add a new column to the table in the future.

  Second, CHANGE_DATE, CHANGE_USER and ACTION are not (probably) functions and are not local variables so it is not supposed to use them in an INSERT statement. You need to write code or to take advantage of the existing functions to fill in these columns. I suppose, for example, that you want to use SYSDATE to fill the CHANGE_DATE and the USER to fill the column CHANGE_USER. My guess is that ACTION must always be a 'U' for UPDATE.

  Thirdly, it seems that you left the: old man on the DEPTNO column.

  Put them all together, you would have something like

  CREATE OR REPLACE TRIGGER trig_emp_audit
    BEFORE UPDATE ON emp
    FOR EACH ROW
  BEGIN
    INSERT INTO emp_audit(
        audit_uid,
        change_date,
        change_user,
        action,
        enpno,
        ename,
        job,
        mgr,
        hiredate,
        sal,
        comm,
        deptno )
      VALUES(
        emp_audit_seq.nextval,
        sysdate,
        user,
        'U',
       :old.empno,
       :old.ename,
       :old.job,
       :old.mgr,
       :old.hiredate,
       :old.sal,
       :old.comm,
       :old.deptno);
  END;
  / 
  

  Justin

• PL/SQL: ORA-00984: column not allowed here

  Sorry, it's probably easy and I forgot something simple, but it's driving me crazy :-)
  

  VARIABLE g_fk_deduction      VARCHAR2(30)
  VARIABLE g_fk_empno          NUMBER
  VARIABLE g_before_or_after_flag     CHAR(1)
  VARIABLE g_deduction_amount     NUMBER
  
  BEGIN
    :g_fk_deduction           := '401K';
    :g_fk_empno               := 7369;
    :g_before_or_after_flag     := 'B';
    :g_deduction_amount          := 150.00;
  END;
  /
  BEGIN
    INSERT INTO emp_deductions      (fk_deduction, fk_empno, before_or_after_flag, deduction_amount)
     VALUES               (g_fk_deduction, g_fk_empno, g_before_or_after_flag, g_deduction_amount);
    COMMIT;
  END;
  /

  Error: PL/SQL: ORA-00984: column not allowed here on g_deduction_amount
  in the value clause.
  Any help would be appreciated.
  
  Table is below:

  CREATE TABLE emp_deductions     (
        fk_deduction            VARCHAR2(30),
        fk_empno                  NUMBER(4),
        before_or_after_flag         CHAR(1),
        deduction_amount            NUMBER(6,2));

  Published by: LostNoob on August 23, 2012 19:06

  rp0428 wrote:
  >
  : g_fk_deduction: = "401k".
  : g_fk_empno: = 7369;
  : g_before_or_after_flag: = 'B ';.
  : g_deduction_amount: = 150.00;
  >
  Why did you put a colon here? Get rid of them.

  They are necessary, since they are declared SQL * more variable.

  The problem for the OP, is that in the clause values in the insert the colon are missing.

  Published by: Mark Williams on August 23, 2012 22:31

  Here is your example requested:

  SQL> create table test (c number);
  
  Table created.
  
  SQL> variable v_c number
  SQL> begin
    2    :v_c := 46;
    3  end;
    4  /
  
  PL/SQL procedure successfully completed.
  
  SQL> begin
    2    insert into test values (:v_c);
    3  end;
    4  /
  
  PL/SQL procedure successfully completed.
  
  SQL> commit;
  
  Commit complete.
  
  SQL> select * from test;
  
           C
  ----------
          46
  
  1 row selected.
  
  SQL>
  

• Procedure returns ORA-00984: column not allowed here

  Get an error returned by my procedure and can't understand it. Someone has an idea?
  Thanks in advance,
  Carpet
  
  14/2 PL/SQL: statement ignored
  15/80 PL/SQL: ORA-00984: column not allowed here
  
  
  
  CREATE OR REPLACE PROCEDURE basket_add_sp
  (p_idproduct in NUMBER,
  p_price in NUMBERS
  p_quantity in NUMBERS
  p_idbasket in NUMBERS
  p_option1 in NUMBERS
  p_option in NUMBERS)
  IS
  lv_seq_num bb_basketitem.idbasketitem%TYPE;
  BEGIN
  SELECT bb_idbasketitem_seq. NEXTVAL
  IN lv_seq_num
  FROM DUAL;
  INSERT INTO bb_basketitem (idbasketitem, idproduct, price, quantity, idbasket, option 1, option 2)
  VALUES (lv_seq_num, p_idproduct, p_price, p_quantity, p_idbasket, p_option1, p_option2);
  COMMIT;
  END;
  /

  What is p_option2 in the INSERT statement? In the settings, you have only p_option1 and p_option.

  I agree with Walter, you can save an e/s by losing the select double.

• ORA-01719: outer join operator (+) not allowed in operand of GOLD or IN

  I'm migrating a stored procedure (package) in Oracle 11 g.  The SQL has an outer join, combined with a "GOLD":

  Select a.row1, a.row2, b.row3, b.row4, c.row5, c.row6

  schema1.table1 a, schema1.table2 b, schema2.table3 c

  where

  ((c.orgunit = a.org (+) and b.newaccount (+) and TO_CHAR(c.createdatetime,'MM/DD/YYYY = c.account and c.feed = 'FOO' ') = TO_CHAR (SYSDATE, ' DD/MM/YYYY'))

  or

  ((c.feed = 'BAR' and c.orgunit = a.org (+) and c.account b.newaccount (+) and TO_CHAR(c.createdatetime,'MM/DD/YYYY =') = TO_CHAR (SYSDATE, ' DD/MM/YYYY'));

  The error is:

  ORA-01719: outer join operator not allowed in operand of GOLD or IN

  * Cause: Outer join appears in a clause or.

  * Action: If A and B are predicates, to achieve the effect of (has or B).

  I do not understand how to apply the suggested action to my query above.  Can anyone provide a solution or a workaround?

  Thank you.

  your base table is c, a and b must be attached to the left

  Select a.row1, a.row2, b.row3, b.row4, c.row5, c.row6

  of schema2.table3 c

  Join schema1.table1 left a c.orgunit on = a.org

  c.account left join schema1.table2 b = b.newaccount

  where c.createdatetime > = trunc (sysdate)

  and c.createdatetime<>

  and (c.feed = 'FOO' or c.feed = 'BAR');

• You are not allowed to open the form ORA-01403: no data found

  Hello

  I created a new forms of Oracle 10 g. It compiles successfully, but when it is open, it gives an error message: you are not allowed to open the form ORA-01403: no data found.

  I am already connected to the database. Please can someone help what is the reason of this problem, and no matter what possible resolution?

  Looks like you have some kind of security is enabled.  However, because you do not share details about your environment or what you're doing here is not that we can do is guess.

  • Exactly what version of forms do you use?
  • Exactly which version of the database that you are using?
  • You use something like Oracle E-Business (e.g. template.fmb)?
  • You created the form with Oracle Designer?
  • If you create a simple form using only the layout assistants and the DataBlock compared to schema Oracle demo (SCOTT), this form run?

  No additional details describing what you do or have done could be useful.

• ORA-00976: virtual specified or operator not allowed here

  Hello

  We had error after upgrade of GR 11, 2, in the insert statement.

  INSERT INTO SDE_TBL_FLEXTRIMSITROUT

  (BRANCHCD,

  SOURCECD,

  CURRENTNO,

  BATCHNO,

  DEPTCD,

  CTL

  INITIATIONDATE,

  AMOUNT,

  ACCOUNT,

  ACCOUNTBRANCH,

  TXNCD,

  DEBITCREDIT,

  LCYEQUIVALENT,

  EXCHRATE,

  VALUEDATE,

  INSTRUMENTNO,

  RELCUST,

  ADDLTEXT,

  TXNMIS1,

  TXNMIS2,

  TXNMIS3,

  TXNMIS4,

  TXNMIS5,

  TXNMIS6,

  TXNMIS7,

  TXNMIS8,

  TXNMIS9,

  TXNMIS10,

  COMPMIS1,

  COMPMIS2,

  COMPMIS3,

  COMPMIS4,

  COMPMIS5,

  COMPMIS6,

  COMPMIS7,

  COMPMIS8,

  COMPMIS9,

  COMPMIS10,

  COSTCODE1,

  COSTCODE2,

  COSTCODE3,

  COSTCODE4,

  COSTCODE5,

  RELATEDACCOUNT,

  RELATEDREF,

  USERREFERENCE,

  ACCTPOSTOVERWRITE,

  EXCHRATEOVERWRITE,

  VALUEDATEOVERWRITE,

  ACCTBALOVERWRITE,

  ITRREFER,

  RefinanceAmount,

  PROCESSID)

  VALUES

  (vBranchCode,

  cCreateNewTrimsITR_rec. APPLSYS,

  ROWNUM,

  nBatchNo,

  cCreateNewTrimsITR_rec. DEPT,

  vCcy,

  To_date (cCreateNewTrimsITR_rec. HOUR, 'YYYYMMDD'),

  nAmount,

  vAccount,

  vAccountBranch, - added by Sibylle

  vTxnCd,

  cDebitCredit,

  nLcyEquivalent,

  nExchRate,

  To_date (cCreateNewTrimsITR_rec. VALUEDATE, 'YYYYMMDD'),

  vInstrumentNo,

  --'      ' || SUBSTR (cCreateNewTrimsITR_rec. ITRREFER, 2, 11),

  vFlxCntry | cCreateNewTrimsITR_rec. APNO,

  vDesc,

  cCreateNewTrimsITR_rec. TRANSOUC,

  RPAD (' ', 9);

  vExpenseMIS,

  vProductMIS,

  RPAD (' ', 9);

  RPAD (' ', 9);

  RPAD (' ', 9);

  RPAD (' ', 9);

  RPAD (' ', 9);

  RPAD (' ', 9);

  RPAD (' ', 9);

  RPAD (' ', 9);

  RPAD (' ', 9);

  RPAD (' ', 9);

  RPAD (' ', 9);

  RPAD (' ', 9);

  RPAD (' ', 9);

  RPAD (' ', 9);

  RPAD (' ', 9);

  RPAD (' ', 9);

  RPAD (' ', 9);

  RPAD (' ', 9);

  RPAD (' ', 9);

  RPAD (' ', 9);

  RPAD (' ', 9);

  RPAD (' ', 20);

  cCreateNewTrimsITR_rec. THEIRREF,

  RPAD (' ', 16).

  cActPostOverwrite,

  cExchRateOverWrite,

  cValueDateOverWrite,

  cAcctBalOverWrite,

  cCreateNewTrimsITR_rec. ITRREFER,

  cCreateNewTrimsITR_rec. REFIAMOUNT,

  nFlexOutProcessId);

  Error: ORA-00976: specified virtual or operator not allowed here

  According to the audit, which are a problem in GR 11, 2 with insert query using rownum in values.

  Someone knows how to fix this?

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

  If you want to use it, it would look like

  Insert into t1 (name, row_num_value)

  Select name

  rownum

  the t2;

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