IMMEDIATE CHECKED

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • Gregor =?UTF-8?B?S292YcSN?=
    #1

    IMMEDIATE CHECKED

    Hi!

    I have two tables TABLE1 and TABLE2 each has it's own primary key. TABLE2
    has a foreign key to TABLE1 and TABLE1 has foreign key to TABLE2. Now I
    have done a LOAD FROM NUL REPLACE INTO TABLE1 and LOAD FROM NUL REPLACE
    INTO TABLE2 and both tables are in Set Integrity Pending state.

    If I do SET INTEGRITY FOR TABLE1 IMMEDIATE CHECKED first I get:
    SQL3608N Cannot check a dependent table "TABLE1" using the SET
    INTEGRITY statement while the parent table or underlying table
    "TABLE2" is in the Set Integrity Pending state or if it will be put
    into the Set Integrity Pending state by the SET INTEGRITY statement.
    SQLSTATE=428A8

    If I do SET INTEGRITY FOR TABLE2 IMMEDIATE CHECKED first I get:
    SQL3608N Cannot check a dependent table "TABLE2" using the SET
    INTEGRITY statement while the parent table or underlying table
    "TABLE1" is in the Set Integrity Pending state or if it will be put
    into the Set Integrity Pending state by the SET INTEGRITY statement.
    SQLSTATE=428A8

    Im in a magic loop here. :)))
    Is there a way to get out ? :))

    Best regards,
    Kovi
    --
    -~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
    | In A World Without Fences Who Needs Gates? |
    | Experience Linux. |
    -~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
    Tags: None
    • Gregor =?UTF-8?B?S292YcSN?=
      #2
      Re: IMMEDIATE CHECKED [Solved]

      Hi!

      I just dropped the foreign key from TABLE1 to TABLE2 and recreated it alter
      successfull SET INTEGRITY.

      Best regards,
      Kovi

      Gregor Kovač wrote:
      Hi!
      >
      I have two tables TABLE1 and TABLE2 each has it's own primary key. TABLE2
      has a foreign key to TABLE1 and TABLE1 has foreign key to TABLE2. Now I
      have done a LOAD FROM NUL REPLACE INTO TABLE1 and LOAD FROM NUL REPLACE
      INTO TABLE2 and both tables are in Set Integrity Pending state.
      >
      If I do SET INTEGRITY FOR TABLE1 IMMEDIATE CHECKED first I get:
      SQL3608N Cannot check a dependent table "TABLE1" using the SET
      INTEGRITY statement while the parent table or underlying table
      "TABLE2" is in the Set Integrity Pending state or if it will be put
      into the Set Integrity Pending state by the SET INTEGRITY statement.
      SQLSTATE=428A8
      >
      If I do SET INTEGRITY FOR TABLE2 IMMEDIATE CHECKED first I get:
      SQL3608N Cannot check a dependent table "TABLE2" using the SET
      INTEGRITY statement while the parent table or underlying table
      "TABLE1" is in the Set Integrity Pending state or if it will be put
      into the Set Integrity Pending state by the SET INTEGRITY statement.
      SQLSTATE=428A8
      >
      Im in a magic loop here. :)))
      Is there a way to get out ? :))
      >
      Best regards,
      Kovi
      --
      -~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
      | In A World Without Fences Who Needs Gates? |
      | Experience Linux. |
      -~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-

        Comment

        • Brian Tkatch
          #3
          Re: IMMEDIATE CHECKED

          On Thu, 01 Mar 2007 10:07:00 +0100, Gregor Kova?
          <gregor.kovac@m ikropis.siwrote :
          >Hi!
          >
          >I have two tables TABLE1 and TABLE2 each has it's own primary key. TABLE2
          >has a foreign key to TABLE1 and TABLE1 has foreign key to TABLE2. Now I
          >have done a LOAD FROM NUL REPLACE INTO TABLE1 and LOAD FROM NUL REPLACE
          >INTO TABLE2 and both tables are in Set Integrity Pending state.
          >
          >If I do SET INTEGRITY FOR TABLE1 IMMEDIATE CHECKED first I get:
          >SQL3608N Cannot check a dependent table "TABLE1" using the SET
          >INTEGRITY statement while the parent table or underlying table
          >"TABLE2" is in the Set Integrity Pending state or if it will be put
          >into the Set Integrity Pending state by the SET INTEGRITY statement.
          >SQLSTATE=428 A8
          >
          >If I do SET INTEGRITY FOR TABLE2 IMMEDIATE CHECKED first I get:
          >SQL3608N Cannot check a dependent table "TABLE2" using the SET
          >INTEGRITY statement while the parent table or underlying table
          >"TABLE1" is in the Set Integrity Pending state or if it will be put
          >into the Set Integrity Pending state by the SET INTEGRITY statement.
          >SQLSTATE=428 A8
          >
          >Im in a magic loop here. :)))
          >Is there a way to get out ? :))
          >
          >Best regards,
          Kovi
          Yep. Do both at the same time.

          SET INTEGRITY FOR TABLE1, TABLE2 IMMEDIATE CHECKED

          B.

            Comment

            • Gregor =?UTF-8?B?S292YcSN?=
              #4
              Re: IMMEDIATE CHECKED

              Brian Tkatch <N/Awrote:
              On Thu, 01 Mar 2007 10:07:00 +0100, Gregor Kova?
              <gregor.kovac@m ikropis.siwrote :
              >
              >>Hi!
              >>
              >>I have two tables TABLE1 and TABLE2 each has it's own primary key. TABLE2
              >>has a foreign key to TABLE1 and TABLE1 has foreign key to TABLE2. Now I
              >>have done a LOAD FROM NUL REPLACE INTO TABLE1 and LOAD FROM NUL REPLACE
              >>INTO TABLE2 and both tables are in Set Integrity Pending state.
              >>
              >>If I do SET INTEGRITY FOR TABLE1 IMMEDIATE CHECKED first I get:
              >>SQL3608N Cannot check a dependent table "TABLE1" using the SET
              >>INTEGRITY statement while the parent table or underlying table
              >>"TABLE2" is in the Set Integrity Pending state or if it will be put
              >>into the Set Integrity Pending state by the SET INTEGRITY statement.
              >>SQLSTATE=428A 8
              >>
              >>If I do SET INTEGRITY FOR TABLE2 IMMEDIATE CHECKED first I get:
              >>SQL3608N Cannot check a dependent table "TABLE2" using the SET
              >>INTEGRITY statement while the parent table or underlying table
              >>"TABLE1" is in the Set Integrity Pending state or if it will be put
              >>into the Set Integrity Pending state by the SET INTEGRITY statement.
              >>SQLSTATE=428A 8
              >>
              >>Im in a magic loop here. :)))
              >>Is there a way to get out ? :))
              >>
              >>Best regards,
              > Kovi
              >
              Yep. Do both at the same time.
              >
              SET INTEGRITY FOR TABLE1, TABLE2 IMMEDIATE CHECKED
              >
              B.
              Yes, much easier way. :)) I was looking at the syntax, but just didn't see
              that back arrow. :((

              Best regards,
              Kovi

              --
              -~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
              | In A World Without Fences Who Needs Gates? |
              | Experience Linux. |
              -~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-

                Comment

                • Brian Tkatch
                  #5
                  Re: IMMEDIATE CHECKED

                  On Thu, 01 Mar 2007 21:27:00 +0100, Gregor Kova?
                  <gregor.kovac@m ikropis.siwrote :
                  >Brian Tkatch <N/Awrote:
                  >
                  >On Thu, 01 Mar 2007 10:07:00 +0100, Gregor Kova?
                  ><gregor.kovac@ mikropis.siwrot e:
                  >>
                  >>>Hi!
                  >>>
                  >>>I have two tables TABLE1 and TABLE2 each has it's own primary key. TABLE2
                  >>>has a foreign key to TABLE1 and TABLE1 has foreign key to TABLE2. Now I
                  >>>have done a LOAD FROM NUL REPLACE INTO TABLE1 and LOAD FROM NUL REPLACE
                  >>>INTO TABLE2 and both tables are in Set Integrity Pending state.
                  >>>
                  >>>If I do SET INTEGRITY FOR TABLE1 IMMEDIATE CHECKED first I get:
                  >>>SQL3608N Cannot check a dependent table "TABLE1" using the SET
                  >>>INTEGRITY statement while the parent table or underlying table
                  >>>"TABLE2" is in the Set Integrity Pending state or if it will be put
                  >>>into the Set Integrity Pending state by the SET INTEGRITY statement.
                  >>>SQLSTATE=428 A8
                  >>>
                  >>>If I do SET INTEGRITY FOR TABLE2 IMMEDIATE CHECKED first I get:
                  >>>SQL3608N Cannot check a dependent table "TABLE2" using the SET
                  >>>INTEGRITY statement while the parent table or underlying table
                  >>>"TABLE1" is in the Set Integrity Pending state or if it will be put
                  >>>into the Set Integrity Pending state by the SET INTEGRITY statement.
                  >>>SQLSTATE=428 A8
                  >>>
                  >>>Im in a magic loop here. :)))
                  >>>Is there a way to get out ? :))
                  >>>
                  >>>Best regards,
                  >> Kovi
                  >>
                  >Yep. Do both at the same time.
                  >>
                  >SET INTEGRITY FOR TABLE1, TABLE2 IMMEDIATE CHECKED
                  >>
                  >B.
                  >
                  >Yes, much easier way. :)) I was looking at the syntax, but just didn't see
                  >that back arrow. :((
                  >
                  >Best regards,
                  Kovi
                  Neither did i!!! I posted this a little while back too. It is
                  especially useful for ignoring reference order.

                  B.

                    Comment

                    Previous template Next
                    Working...