7 Replies Latest reply: Jul 2, 2014 10:21 AM by Matze1969 RSS

    ORA-24155 with define_chain_rule

    Matze1969

      Dear all,

       

      I try to set up a scheduler chain. Unfortunately I get the following error. I'm executing the following code (excerpt):

       

      sys.dbms_scheduler.create_chain(...);

      sys.dbms_scheduler.define_chain_step(...);

      ...

      sys.dbms_scheduler.define_chain_step(...):

       

      The following fails:

       

        sys.dbms_scheduler.define_chain_rule(

                                              chain_name    => 'IDIS_INFRA.INFRA_STAGE'

                                            , condition     => '"STG_BS_LAGE" FAILED'

                                            , action        => 'END '

                                            , rule_name     => 'IDIS_INFRA.END_BS_LAGE'

                                            , comments      => null

        );

       

      Database version is 11.2 (no patch).

       

      On my local database (also 11.2 no patch) and on Oracle XE 11g I can create the chain rule without error.

       

      What could be the reason?

       

      Kind reegards

      Matthias

        • 1. Re: ORA-24155 with define_chain_rule
          GregV

          Hi Matthias,

           

          What is the complete error message you get?

          • 2. Re: ORA-24155 with define_chain_rule
            Matze1969

            ORA-24155: Regel IDIS_INFRA.END_BS_LAGE befindet sich nicht in Regelgruppe IDIS_INFRA.SCHED_RULESET$2

            ORA-06512: in "SYS.DBMS_ISCHED", Zeile 4856

            ORA-06512: in "SYS.DBMS_ISCHED", Zeile 1578

            ORA-06512: in "SYS.DBMS_SCHEDULER", Zeile 1619

            ORA-06512: in Zeile 124

            24155. 00000 -  "rule %s.%s not in rule set %s.%s"

            *Cause:    the rule to be removed from the rule set is not in the rule set

            *Action:   do not remove a rule from a rule set that does not contain the rule

             

            But I havn't specified a rule set nor have I tried to remove the rule...so I do not understand this error mesage ;-)

            • 3. Re: ORA-24155 with define_chain_rule
              GregV

              Maybe some stuff from old rules. What does the following query return:

               

              select * from user_rule_set_rules;

              • 4. Re: ORA-24155 with define_chain_rule
                Matze1969
                SCHED_RULESET$1IDIS_INFRAABORT_PROCESSENABLED
                SCHED_RULESET$1IDIS_INFRASTAGE_TO_TRANSFORMENABLED
                SCHED_RULESET$1IDIS_INFRASTART_PROCESSENABLED
                SCHED_RULESET$2IDIS_INFRAEND_ABGKNENABLED
                SCHED_RULESET$2IDIS_INFRAEND_BS_FWENABLED
                SCHED_RULESET$1IDIS_INFRAEND_PROCESSENABLED

                 

                Ruleset 1 belongs to a different chain. When I drop the chain which contains END_ABGKN then also Ruleset 2 will be dropped. And as you see two rules were created for ruleset 2 althaugh I used the same procedure calls...

                • 5. Re: ORA-24155 with define_chain_rule
                  GregV

                  Hi,

                   

                  Maybe the DEFINE_CHAIN_RULE procedure tries to drop the rule prior to creating it, and it seems there's a conflict with some name. Can you try the same thing without specifying a value for the RULE_NAME parameter?

                  Also, what does the following return:

                  select * from user_scheduler_chain_rules;

                  • 6. Re: ORA-24155 with define_chain_rule
                    Matze1969

                    Hi,

                     

                    with RULE_NAME => null it works for all of my rules. When I specify rule names it just works for some of my rules, which I don't understand. But with knowing this fact it's ok for me. Thanks a lot!

                    • 7. Re: ORA-24155 with define_chain_rule
                      GregV

                      There's maybe a bug, but I couldn't find anything relevant in the Oracle Support KB about this problem.

                      Thanks for the feedback.