ORA-20505: DML error: p_rowid = 22, p_alt_rowid = WRKORDR_ID, p_rowid2 =, p_a

Similar Questions

• ORA-20505: DML error: p_rowid = 684, p_alt_rowid = RETAILER_ID, p_rowid2 =, p

  HELP PLZ

  It's really a small question...

  Run your page in DEBUG mode, and you'll probably notice where the error is thrown.

• ORA-20505: Error DML

  I have a form that is based on a view joining three tables and make changes/insertions/deletions via INSTEAD OF relaxation. Updates go well, but for inserts, I get the following error:
  
  ORA-20505: DML error: p_rowid = 94703, p_alt_rowid = NUM_SEQ_LIN, p_rowid2 =, p_alt_rowid2 is. ORA-01403: no data found
  
  Apparently, INSTEAD OF trigger does not fire (I have inserted into a special table of debug information never show). NUM_SEQ_LIN is initialized.
  
  Does anyone know how to decipher this error message and find what went wrong?
  
  Igor

  Hello Igor.

  If you insert the debug information in the INSTEAD OF trigger (and do not use an autonomous transaction) and the defective trigger, the iof insert debugging information will also be rollbacked.
  Maybe you could post the code of your trigger to insert here.
  Have you checked if the triggers on target tables can cause the problem - those will fire also.
  Your page running in DEBUG mode can help you catch the problem.

  Greetings,
  Roel

  http://roelhartman.blogspot.com/

• ORA-20505: error in DML - data in db Version has changed

  Hello
  Request Express 3.1.0.00.32
  I created a report and master detail in the sample Application on oracle.application.com. I get an error on my Master form when you click < Previous and Next >. I saw other problems of this kind in the forum, but it seems that everyone is a little different. Can someone help me with this error when you browse the next answer (s). Thanks in advance.
  
  ORA-20505: DML error: p_rowid = 6, p_alt_rowid CUSTOMER_ID =, p_rowid2 =, p_alt_rowid2 is. ORA-20503: current Version of the data in the database has changed since the user initiated the update process. current checksum = checksum of the "E9A08EDC02A82871E6865DB254B09ED2" = "39454529513F24BE60C167752BF71750."
  
  I created another page master detail and I don't have any errors when scrolling using the <>. This is a process that can be causing my error by using the page master original detail.
  

  DECLARE 
  CUSTOMER_ID VARCHAR(20);
  BEGIN
   SELECT CUSTOMER_ID INTO :P21_CUSTOMER_ID
   FROM DEMO_CUSTOMERS
   WHERE CUST_FIRST_NAME = :P21_CUST_FIRST_NAME;
  -- processing here
  EXCEPTION
    -- Catches all 'no data found' errors
     WHEN NO_DATA_FOUND THEN
       DBMS_OUTPUT.PUT_LINE
         ('No Data found for SEARCH on ' || CUSTOMER_ID);
  END;

  Published by: Charles was April 30, 2009 11:40

  Hi Charles,

  I had a look at your page 21.

  The problem was that the 'Values of Fetch 2' process was not conditioned and was running in the point of the process "on the load - before the Header." That meant he was running whenever the page is loaded. This process checks the value CUSTOMER_ID in P21_CUST_FIRST_NAME that, because the process of "search for the line...". "has not been performed at that time there (he turns"on the charge - after the Header"), will always return the same value CUSTOMER_ID from when the page was first loaded. The next/previous buttons, however, moved the front/rear P21_CUSTOMER_ID only one value (this became obvious when this field was changed from 'Hidden and protected' to 'Text'). Therefore, the data on the page was for "Albert" but was it to CUSTOMER_ID for any document was previous to the Albert one. Thus, moving next/previous always caused a mixture of real data.

  I changed the "Fetch values 2" process to depend on P21_CUSTOMER_ID is NULL. In this way, the CUSTOMER_ID value found ONLY by code when the page is loaded for the first time. Subsequently, it is controlled by the next/previous feature.

  Andy

• Sudden error-&gt; ORA-20505: error DML

  Hi all
  
  I noticed today that all pages of an application, that uses automatic row Fetch (DML), suddenly stopped working and displayed the following error:
  
  
  Update:
  
  ORA-20505: DML error: p_rowid = ModTest, p_alt_rowid is OPC_COD, p_rowid2 =, p_alt_rowid2 is. ORA-20503: current Version of the data in the database has changed since the user initiated the update process. current checksum = checksum of the '54CFD3E0DBD50510D86894EA9DB09357' = '0 '.
  
  Deletions:
  
  
  
  ORA-20510: current Version of the data in the database has changed since the user initiated the update process.
  
  
  
  There is no problem with the Insert, it works very well, which makes things more confusing. No matter what ideas on what could be causing this sudden failure?
  
  
  
  Cordially Pedro.

  Pedro,

  For some reason, your page templates had this:

  [an error occurred while processing the directive]
  

  .. .that #FORM_CLOSE # channel shouldn't be commented.

  Scott

• ORA-20505: error in DML: p_rowid AAARr/AAOAAAAh9AAB =, p_alt_rowid = PK, p_row

  HI, Hi, I'm running Application Express 4.0.1.00.02 and Oracle 11 g I can't do updates. As a result of updates in the following: ORA-20505: error in DML: p_rowid = AAARr/AAOAAAAh9AAB, p_alt_rowid is PK, p_rowid2 =, p_alt_rowid2 is. ORA-01733: virtual column not allowed here. Insert or delete error is: ORA-01733: virtual column not allowed here. The pk in my opinion have a rowid column and do not have a sequence number. ManyThanks.

  ROWID is a virtual column in view of Oracle. You must identify a column or set of columns in the table for Oracle to TRY and maintain order in the data...

  Thank you

  Tony Miller
  Webster, TX

  Never argue with a fool. They do you drag down to their level, then beat you with experience.

• ORA-00257: Archive error

  Hi all
  
  ORA-00257: archiver error. Connect internal only, until this just released.
  
  My Question is why oracle does not allow to connect as a user of normal database like Scott during the archiving log is full, I know, log archiving is generating for the ddl/DML statements.
  y at - it archive log is generated in the course of a user, process is connected to the instance.
  Why oracle not connect to the database and everything for the ddl/DML statements, it can make the rite of error message, until I can go look for some records to the database (select statements) should allow.
  
  Please let me know the reason!
  
  Thank you
  
  Shan

  You ask "even if the DB is in State at time why I can't connect with a user in the role of read-only?"

  I think that Oracle will not take the risk.

  The only reason I can think of right now is "there could be enabled for user verification and wirte in the audit log, to DML on the basis of data"

• DML Error Logging guard MOM

  SQL> select * from v$version;
  
  BANNER
  ----------------------------------------------------------------------------
  
  Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
  PL/SQL Release 11.2.0.2.0 - Production
  CORE    11.2.0.2.0      Production
  TNS for Solaris: Version 11.2.0.2.0 - Production
  NLSRTL Version 11.2.0.2.0 - Production

  Problem: Trying to insert into mytable and implement DML error logging. But the logging of errors never comes into play instead process fails
  with

  ORA-01843: not a valid month

  Why is this happening? I thought that can be direct-path insert is the reason behind it. But Tom Kite itself uses DPI.
  http://tkyte.blogspot.com/2005/07/how-cool-is-this.html
  
  Any advice?

  INSERT /*+ APPEND */  INTO mytable
  SELECT   A,
           TO_DATE(TRIM(SUBSTR(str,1, INSTR(str, ' to ') - 1)), 'Mon DD YYYY')   csd,
           TO_DATE(TRIM(SUBSTR(str, INSTR(str, ' to ') + 4, INSTR(str, '-') - (INSTR(str, ' to ') + 5))), 'Mon DD YYYY')   ced,
           B,
           C,
           D
           
    FROM   (SELECT   DISTINCT 
                     p1,
                     p2,
                     p3
            
              FROM P
              
           ) pc1 
           INNER JOIN tbl1 ON (...)
           INNER JOIN tbl2 ON (...)
           INNER JOIN tbl3 ON (...)
             
  ORDER BY A, B, C
  
  LOG ERRORS ('my errors') REJECT LIMIT UNLIMITED;

  Logging of DML errors will record errors that occur on the LMD. It is in this case on the insert.

  Your error occurs on the execution of the query (which you try to insert the result).
  The query must be valid... And apparently this isn't: for some lines the to_date seems to fail.

• Logging of DML errors for Update statement

  Hello
  
  I am facing a problem regarding recording with instructions to update DML errors.
  
  Oracle: 10.2
  
  I am running after update DML:
  

  BEGIN 
  
  UPDATE 
  table_1  a
  SET a.Exp_DATE =a.EFF_DATE 
  WHERE  a.col_a1 != (SELECT b.colb1
                       FROM table_2  b
                       WHERE  a.msisdn =b.msisdn )
  LOG ERRORS INTO table_1_ERR REJECT LIMIT UNLIMITED;                         
                           
                           
                           
  END ;    

  I expect that "ORA-01427: einreihig subquery returns several lines" would be entered in the table of error LOG "table_1_err".
  but instead, I got error lance and entire dml has been restored.
  
  Please let me know if this exception is not captured by the logging of DML errors.
  
  Thank you
  Abhishek

  Abhi.k wrote:
  I expect that "ORA-01427: einreihig subquery returns several lines" would be entered in the table of error LOG "table_1_err".
  but instead, I got error lance and entire dml has been restored.

  Logging error tables are there to capture violations of constraints. What you have is a coding error. So no, he will not be captured.

• Logging of DML errors

  Hi, I use DMl error logging in my SQLs. I created my table of error help
  
  DBMS_ERRLOG.create_error_log EXEC ('TB_AGGR', 'TB_AGGR_ERR');
  
  I want to know if I change my TB_AGGR table, and then will be automatically modified error table. If this is not the case, as happens during the exceptions? Is it possible to make the altar in my table of error automatically?

  for the sake of others looking for a workaround for this solution:

  SQL> select * from v$version;
  
  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
  TNS for 32-bit Windows: Version 11.1.0.6.0 - Production
  NLSRTL Version 11.1.0.6.0 - Production
  SQL> create table log_err_test(a date);
  
  Table created.
  
  SQL> exec dbms_errlog.create_error_log('LOG_ERR_TEST');
  
  PL/SQL procedure successfully completed.
  
  SQL> declare
    2  ll_limit number := 1;
    3  begin
    4  insert into log_err_test(a)
    5  select to_date(dummy,'dd/mm/yyyy') from dual
    6  log errors into err$_log_err_test
    7  reject limit ll_limit;
    8  end;
    9  /
  reject limit ll_limit;
               *
  ERROR at line 7:
  ORA-06550: line 7, column 14:
  PL/SQL: ORA-30645: reject limit out of range
  ORA-06550: line 4, column 1:
  PL/SQL: SQL Statement ignored
  

  solution:
  use dynamic sql statements:

  SQL> declare
    2  ll_limit number := 1;
    3  begin
    4  execute immediate 'insert into log_err_test(a)
    5  select to_date(dummy,''dd/mm/yyyy'') from dual
    6  log errors into err$_log_err_test
    7  reject limit ' || to_char(ll_limit);
    8  end;
    9  /
  
  PL/SQL procedure successfully completed.
  

  Amiel Davis

• ORA-39127: unexpected error in call to 'WMSYS '. "" "" LT_EXPORT_PKG '. "" SYSTEM_INFO_EXP ".

  While the export of database complete expdp following errors show?

  Start "SYSTEM". "" EXPORT_JOB_150506150137 ":

  Current estimation using BLOCKS method...

  Treatment of DATABASE_EXPORT/SCHEMA/TABLE/TABLE_DATA object type

  Total estimation using BLOCKS method: 2,906 GB

  Object DATABASE_EXPORT/TABLESPACE of treatment type

  Type of object DATABASE_EXPORT/PROFILE of treatment

  Treatment of DATABASE_EXPORT/SYS_USER/USER object type

  Treatment of type of object DATABASE_EXPORT/SCHEMA/TYPE/SCHOLARSHIP/OWNER_GRANT/OBJECT_GRANT

  Treatment of type of object DATABASE_EXPORT, SYSTEM_PROCOBJACT, PRE_SYSTEM_ACTIONS, PROCACT_SYSTEM

  ORA-39127: unexpected error in call to 'WMSYS '. "" "" LT_EXPORT_PKG '. "" SYSTEM_INFO_EXP ".

  ORA-44002: incorrect object name

  ORA-06512: at "SYS." DBMS_ASSERT", line 383

  ORA-06512: at "SYS." Dbms_metadata", line 10079

  Treatment of type of object DATABASE_EXPORT/SYSTEM_PROCOBJACT/PROCOBJ

  Treatment of type of object DATABASE_EXPORT, SYSTEM_PROCOBJACT, POST_SYSTEM_ACTIONS, PROCACT_SYSTEM

  SQL > select * from v version $;

  BANNER

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

  Oracle Database 11 g Enterprise Edition Release 11.2.0.4.0 - 64 bit Production

  PL/SQL Release 11.2.0.4.0 - Production

  CORE Production 11.2.0.4.0

  AMT for 64-bit Windows: Version 11.2.0.4.0 - Production

  NLSRTL Version 11.2.0.4.0 - Production

  SQL > select * FROM SYS. EXPPKGACT$ WHERE SCHEMA = "WMSYS";

  LEVEL OF SCHEMA PACKAGE CLASS #.

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

  LT_EXPORT_PKG 1 1000 WMSYS

  LT_EXPORT_PKG 2 1000 WMSYS

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

  expdp

  Export: Release 11.2.0.4.0 - Production Wednesday, may 6, 16:11:43 2015

  Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

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

  Operating system == > > Windows server 2008 R2 Enterprise Edition.

  RAJESH. PK

  Hello

  Conn / as sysdba
  create the table sys.exppkgact$ _backup in select * from sys.exppkgact$;
  remove the sys.exppkgact$ where package = "LT_EXPORT_PKG";
  commit;

  Run the new expdp

  'This eliminated error' now

  Thank you Top.Gun your fast support.

  Rajesh

• ORA-20001: System error: procedure sort_segment_order step 40

  ORA-20001: System error: procedure sort_segment_order step 40

  DECLARE

  lc_employee_number per_all_people_f.employee_number%TYPE; -: = "tan_01";

  ln_person_id per_all_people_f.person_id%TYPE;

  ln_assignment_id per_all_assignments_f.assignment_id%TYPE;

  ln_object_ver_number per_all_assignments_f.object_version_number%TYPE;

  ln_address_id PER_ADDRESSES. ADDRESS_ID % TYPE;

  ln_asg_ovn NUMBER;

  ld_per_effective_start_date per_all_people_f.effective_start_date%TYPE;

  ld_per_effective_end_date per_all_people_f.effective_end_date%TYPE;

  lc_full_name per_all_people_f.full_name%TYPE;

  ln_per_comment_id per_all_people_f.comment_id%TYPE;

  ln_assignment_sequence per_all_assignments_f.assignment_sequence%TYPE;

  lc_assignment_number per_all_assignments_f.assignment_number%TYPE;

  lb_name_combination_warning BOOLEAN;

  lb_assign_payroll_warning BOOLEAN;

  lb_orig_hire_warning BOOLEAN;

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

  -Assignment

  l_assignment_id NUMBER;

  l_effective_date DATE: = NULL;

  l_supervisor_id NUMBER;

  lb_correction BOOLEAN;

  lb_update BOOLEAN;

  lb_update_override BOOLEAN;

  lb_update_change_insert BOOLEAN;

  lc_dt_ud_mode VARCHAR2 (100): = NULL;

  l_obj_version_num NUMBER;

  l_organization_id NUMBER: = 81;

  l_soft_coding_keyflex_id hr_soft_coding_keyflex.soft_coding_keyflex_id%TYPE;

  l_concatenated_segments VARCHAR2 (2000);

  l_comment_id per_all_assignments_f.comment_id%TYPE;

  l_effective_start_date per_all_assignments_f.effective_start_date%TYPE;

  l_effective_end_date per_all_assignments_f.effective_end_date%TYPE;

  l_no_managers_warning BOOLEAN;

  l_other_manager_warning BOOLEAN;

  ERROR_MESSAGE VARCHAR2 (4000): = NULL;

  current_records NUMBER;

  total_records NUMBER;

  error_records NUMBER;

  l_effective_date_valid NUMBER;

  error_message1 VARCHAR2 (4000): = NULL;

  v_ledger_id gl_ledgers.ledger_id%type;

  v_job_definition_id PER_JOB_DEFINITIONS.job_definition_id%type;

  v_position_definition_id per_position_definitions.position_definition_id%type;

  v_location_id hr_locations_all.location_id%type;

  v_emp_count number: = 0;

  -The Variables of the criteria of update for employees Assgment

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

  -ln_people_group_id NUMBER: = null;   -This will cause the error ORA-20001: System error: procedure step 40

  ln_people_group_id NUMBER: = hr_api.g_number;   -PEOPLE_GROUP_ID

  end;

  ln_special_ceiling_step_id PER_ALL_ASSIGNMENTS_F.SPECIAL_CEILING_STEP_ID%TYPE;

  lc_group_name VARCHAR2 (30);

  ld_effective_start_date PER_ALL_ASSIGNMENTS_F.EFFECTIVE_START_DATE%TYPE;

  ld_effective_end_date PER_ALL_ASSIGNMENTS_F.EFFECTIVE_END_DATE%TYPE;

  lb_org_now_no_manager_warning BOOLEAN;

  lb_other_manager_warning BOOLEAN;

  lb_spp_delete_warning BOOLEAN;

  lc_entries_changed_warning VARCHAR2 (30);

  Entry: HR_ASSIGNMENT_BK3. UPDATE_EMP_ASG_CRITERIA_B 10

  hr_api.validate_commit_unit 10

  Leave: HR_ASSIGNMENT_BK3. UPDATE_EMP_ASG_CRITERIA_B 20

  Enter hr_kflex_utility set_profiles 5

  hr_kflex_utility set_profiles 10

  hr_kflex_utility set_profiles 20

  hr_kflex_utility set_profiles 30

  hr_kflex_utility set_profiles 40

  hr_kflex_utility set_profiles 50

  Leaving hr_kflex_utility set_profiles 100

  Enter hr_kflex_utility set_session_date 5

  hr_kflex_utility set_session_date 30

  Leaving hr_kflex_utility set_session_date 100

  Inbound: upd_or_sel_keyflex_comb 10

  upd_or_sel_keyflex_comb 20

  Inbound: check_ignore_varray 10

  Seg3 $Sys_Def$                                                         101

  Inbound: ins_or_sel_keyflex_comb 10

  ins_or_sel_keyflex_comb 20

  Inbound: check_ignore_varray 10

  ins_or_sel_keyflex_comb 30

  Inbound: sort_segment_order 10

  sort_segment_order 20

  sort_segment_order 30

  sort_segment_order 40

  ins_or_sel_keyflex_comb 100

  Leaving upd_or_sel_keyflex_comb 140

  -RollBack ORA-20001: System error: sort_segment_order procedure step 40

  Cause: The sort_segment_order procedure created a mistake in step 40.

  Action: Contact your system administrator citing the sort_segment_order procedure and 40 of the step.

  Thank you all,

  I found the solution of adding at least one value in the key flexfield: "Flexfield group of people.

  Kind regards

  

• [ORA-00600: internal error code, arguments: [25027], [10], [0], [] [], [], [], [], [], [], []]

  Hi gurus,

  While the insertion to column records we get from blob "ORA-00600: internal error code, arguments: [25027], [10], [0], [], [], [], [], [], [], [], [], [] ' inner exception

  Details of the environment:

  Oracle Database 11 g Enterprise Edition Release 11.2.0.2.0 - 64 bit Production

  AMT for Linux: Version 11.2.0.2.0 - Production

  Hi gurus,

  We find the below workaround.

  The error is corrected by:

  Re-create the table using import-drop-exp.

  OR move the lob in a new tablespace. for example: Alter table move lob(&lob_column) store like (tablespace &tbsp);)

  Thank you

  VK

• Oracle Database Vault ORA-12578 connection error: open TNS:wallet failed (user OS to access the wallet)

  Hi all

  I create a portfolio of oracle and everything works fine until a script is launched by the OS oracle user. (same user that whoever created the store)

  I use authentication external store and inside my script, I do something like a sqlplus / @MYSECURE_TNS.

  However, when I run a script OS another user as a 'data_loading_user' I get the error: Oracle Database Vault ORA-12578 connection error: TNS:wallet open failed

  I would like to know, how I can activate any user on the local host access the portfolio safe to connect to the database.

  Here my current ENV:

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

  Oracle Linux 6.5

  Oracle a Standard 11.2.0.4

  Webtier Oracle 11g

  Database and thin client SQLNET. ORA

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

  SQLNET. WALLET_OVERRIDE = TRUE

  SSL_CLIENT_AUTHENTICATION = FALSE

  SSL_VERSION = 0

  WALLET_LOCATION =

  (SOURCE =

  (METHOD = FILE)

  (METHOD_DATA =

  (DIRECTORY = / u01/app/oracle/owm/wallets)

  )

  )

  Thanks in advance for any help.

  JS

  Hi all

  Tried something out of the blue, that has worked.

  I added the data_loading_user of the user to the group administrator (Group of BONES that created the wallet).

  The I added the read permission to the group, so the permission on the files below were 640:

  # > chmod 640 cwallet.sso

  # > 640ewallet.p12 chmod

  Thank you

  JS

• dbms_scheduler.create_window fails with ORA-27418: syntax error in the interval of recurrence or calendar

  I tried to create a window to test the activation of plans of RM. But I get this error.

  SQL > EXECUTE dbms_scheduler.create_window.

  > (-)

  > window_name = > 'day ', -.

  > resource_plan = > 'my_plan ', -.

  > start_date = > systimestamp + 1 /(24*60).

  > repeat_interval = > ' freq = > daily '.

  > time = > ' 0 01:00:00 '.

  > Comments = > ' C know if it works without a job "-"

  >);

  BEGIN dbms_scheduler.create_window (window_name = > 'day', resource_p)

  LAN = > 'my_plan', start_date = > systimestamp + 1 /(24*60), repeat_interv

  Al = > ' freq = > daily ', duration = > ' 0 01:00:00 ', comments = > ' C so she

  works without employment '); END;

  *

  ERROR on line 1:

  ORA-27481: 'SYS '. "' DAY ' has an invalid schedule

  ORA-27418: syntax error in the interval of recurrence or calendar

  ORA-06512: at "SYS." DBMS_ISCHED", line 486

  ORA-06512: at "SYS." DBMS_SCHEDULER', line 1295

  ORA-06512: at line 1

  I have tried many tips found on the web, nothing works.

  Any help would be greatly appreciated.

  Also, can you pls tell me if this command run once automatically activates the my_plan after 1 minute, 1 minute, after which, it will disable the my_plan? So, you do not need to create a JOB for this. If you create a window, that is, as a job creation to enable an RM plan?

  2734369 wrote:

  Wow, discovered the issue: the repeat interval is broken (I use a database of 12.1 in Windows 7). It must be uppercase. Very surprising in the windows to be case-sensitive.

  SQL >

  SQL > EXECUTE dbms_scheduler.create_window.

  >  (-

  > window_name-online 'day ', -.

  > resource_plan-online 'my_plan ', -.

  > start_date-online systimestamp + 1 /(24*60).

  > repeat_interval-online ' FREQ = DAILY; BYHOUR = 10; BYMINUTE = 30', -.

  > time-online ' 0 01:00:00 '.

  > Comments => ' C know if it works without a job "-"

  >  );

  PL/SQL procedure successfully completed.

  Problem is, after 1 minute, always that the plan is not activated?

  SQL > SEE THE RESOURCE_MANAGER_PLAN PARAMETER

  VALUE OF TYPE NAME

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

  resource_manager_plan chain

  Why the Plan is not activated after 1 minute. Have we not create a job (I don't think).

  I think you misunderstand the meaning of "start_date".  Please see the documentation on what this means exactly.

  This attribute specifies the first date and time where it is scheduled to open in this window. If the value start_date specified is in the past or is not specified, the window opens, from its inception.

  To repeat windows using an expression of the calendar to specify the repetition interval, the value of start_date is a reference date. The first time the window opens depends on the specified repeat interval and the value of start_date .

  (From Types and Oracle® packages of PL/SQL Database 11g Release 2 (11.2) reference E40758-03); dbms_scheduler, create_window.  DBMS_SCHEDULER

  Once you have done this, you will see that it is pretty useless to specify that you have.

  Your repeat_interval said "every day at 10:30.