1. Get rid of all advertisements and get unlimited access to documents by upgrading to Premium Membership. Upgrade to Premium Now and also get a Premium Badge!

Ora-0143

Discussion in 'SQL PL/SQL' started by Kappa, Mar 5, 2013.

  1. Kappa

    Kappa Active Member

    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    55
    My problem:
    Every standard Oracle error message has in it's name the number of the error, which is the same that is returned by SQLCODE.
    You can define your own exception, associate it with an error that has already a predefined exception associated and use it.
    Why this is not the case for ORA-O1403?
    It's SQLCODE is 100.
    The only nonnegative SQLCODE.
    Can someone explain it to me?
    Thank You
     
  2. zargon

    zargon Community Moderator Forum Guru

    Messages:
    2,347
    Likes Received:
    348
    Trophy Points:
    1,430
    Location:
    Aurora, CO
    It was one of the first errors generated by Oracle Version 2 (the first commercial release) and it's original error code was 100. Later on, when the error code list grew and it was decided to assign negative sqlcode values the original assignment remained as, likely, the original code to assign that error had not changed. I expect it still hasn't.
     
    Kappa likes this.
  3. Kappa

    Kappa Active Member

    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    55
    Thank You, Sir.