Results 1 to 7 of 7
  1. #1
    Join Date
    Oct 2003
    Posts
    17

    Unanswered: Most Common Oracle Error Messages

    Hi All,

    I was trying to find out the internet, if anyone had put the most common
    error messages that a DBA encounters..for other's reference. Could not find any.

    If you guys can add the errors here to this thread it will be greatly helpful
    for others ....

    Thanks,
    -Ash.

  2. #2
    Join Date
    Aug 2003
    Location
    Where the Surf Meets the Turf @Del Mar, CA
    Posts
    7,776
    Provided Answers: 1
    You can lead some folks to knowledge, but you can not make them think.
    The average person thinks he's above average!
    For most folks, they don't know, what they don't know.
    Good judgement comes from experience. Experience comes from bad judgement.

  3. #3
    Join Date
    Oct 2003
    Posts
    17
    Hey,

    I have the manual with me.

    I was more looking for frequently encountered error messages.

    Thanks for the reply though.

    -Ash.

  4. #4
    Join Date
    Aug 2003
    Location
    Where the Surf Meets the Turf @Del Mar, CA
    Posts
    7,776
    Provided Answers: 1
    >I was more looking for frequently encountered error messages.
    What do you plan on doing with them, once you have them?

    The only error messages which should matter to you,
    are the ones your application users see.
    You can lead some folks to knowledge, but you can not make them think.
    The average person thinks he's above average!
    For most folks, they don't know, what they don't know.
    Good judgement comes from experience. Experience comes from bad judgement.

  5. #5
    Join Date
    Oct 2003
    Posts
    17
    Ok...!

    I recently attended for an Oracle DBA Interview
    One of the questions they asked was...

    Please tell us the error messages that you have commonly encountered as a DBA...!

    Thanks anacedent...

    Now, Do you want to share your commonly encountered error messages...

  6. #6
    Join Date
    Aug 2003
    Location
    Where the Surf Meets the Turf @Del Mar, CA
    Posts
    7,776
    Provided Answers: 1
    ORA-01001
    ORA-01555
    ORA-01400
    ORA-01722
    ORA-01843
    ORA-01858
    ORA-03113
    ORA-03114
    ORA-04031
    ORA-06502
    just off the top of my head

    HTH & YMMV
    You can lead some folks to knowledge, but you can not make them think.
    The average person thinks he's above average!
    For most folks, they don't know, what they don't know.
    Good judgement comes from experience. Experience comes from bad judgement.

  7. #7
    Join Date
    Oct 2003
    Posts
    17
    I dont know how to resolve the first two.
    I have come across the rest.


    ORA-01001 invalid cursor
    Cause: Either a host language program call specified an invalid cursor or the value of the MAXOPENCURSORS option in the precompiler command were
    too small. All cursors must be opened using the OOPEN call before being
    referenced in any of the following calls: SQL, DESCRIBE, NAME, DEFINE,
    BIND, EXEC, FETCH, and CLOSE. The Logon Data Area (LDA) must be
    defined by using OLON or OLOGON. If the LDA is not defined, this message is issued for the following calls: OPEN, COM, CON, ROL, and LOGOFF.
    Action: Check the erroneous call statement.
    Specify a correct LDA area or open the cursor as required. If there is no problem with the cursor, it may be necessary to increase the MAXOPENCURSORS option value before precompiling



    ORA-04031 unable to allocate string bytes of shared memory
    ("string","string","string","string")
    Cause: More shared memory is needed than was allocated in the shared pool.
    Action: If the shared pool is out of memory, either use the DBMS_SHARED_
    POOL package to pin large packages, reduce your use of shared memory, or
    increase the amount of available shared memory by increasing the value of the
    initialization parameters SHARED_POOL_RESERVED_SIZE and SHARED_
    POOL_SIZE. If the large pool is out of memory, increase the initialization
    parameter LARGE_POOL_SIZE.



    ORA-01555 snapshot too old: rollback segment number string with name "string"
    too small
    Cause: Rollback records needed by a reader for consistent read are overwritten
    by other writers.
    Action: If in Automatic Undo Management mode, increase the setting of
    UNDO_RETENTION. Otherwise, use larger rollback segments.



    ORA-01400 cannot insert NULL into (string)
    Cause: An attempt was made to insert a NULL into the column
    "USER"."TABLE"."COLUMN".
    For example, if you enter:
    connect scott/tiger
    create table a (a1 number not null);
    insert into a values (null);
    Oracle returns:
    ORA-01400 cannot insert NULL into ("SCOTT"."A"."A1") : which means you
    cannot insert NULL into "SCOTT"."A"."A1".
    Action: Retry the operation with a value other than NULL.



    ORA-01722 invalid number
    ORA-01500 to ORA-02099 4-33
    Cause: The attempted conversion of a character string to a number failed
    because the character string was not a valid numeric literal. Only numeric fields
    or character fields containing numeric data may be used in arithmetic functions
    or expressions. Only numeric fields may be added to or subtracted from dates.
    Action: Check the character strings in the function or expression. Check that
    they contain only numbers, a sign, a decimal point, and the character "E" or "e"
    and retry the operation.


    ORA-01843 not a valid month
    Cause: A date specified an invalid month. Valid months are:
    January-December, for format code MONTH, and Jan-Dec, for format code
    MON.
    Action: Enter a valid month value in the correct format.



    ORA-01858 a non-numeric character was found where a numeric was expected
    4-52 Oracle9 i Database Error Messages
    Cause: The input data to be converted using a date format model was
    incorrect. The input data did not contain a number where a number was
    required by the format model.
    Action: Fix the input data or the date format model to make sure the elements
    match in number and type. Then retry the operation.




    ORA-03113 end-of-file on communication channel
    Cause: An unexpected end-of-file was processed on the communication
    channel. The problem could not be handled by the Net8 two-task software. This
    message could occur if the shadow two-task process associated with a Net8
    connect has terminated abnormally, or if there is a physical failure of the
    interprocess communication vehicle, that is, the network or server machine
    went down.
    In addition, this message could occur when any of the following
    statements/commands have been issued:
    n ALTER SYSTEM KILL SESSION ... IMMEDIATE
    n ALTER SYSTEM DISCONNECT SESSION ... IMMEDIATE
    n SHUTDOWN ABORT/IMMEDIATE/TRANSACTIONAL
    Action: If this message occurs during a connection attempt, check the setup
    files for the appropriate Net8 driver and confirm Net8 software is correctly
    installed on the server. If the message occurs after a connection is well
    established, and the error is not due to a physical failure, check if a trace file
    was generated on the server at failure time. Existence of a trace file may suggest
    an Oracle internal error that requires the assistance of Oracle Support Services.



    ORA-03114 not connected to ORACLE
    Cause: A call to Oracle was attempted when no connection was established.
    Usually this happens because a user-written program has not logged on. It may
    happen if communication trouble causes a disconnection. In addition, this
    message could occur when ALTER SYSTEM KILL SESSION or ALTER SYSTEM
    DISCONNECT SESSION were issued with the IMMEDIATE qualifier because,
    in those cases, the client’s connection to the database is terminated without
    waiting for the client to issue a request.
    Action: Try again. If the message recurs and the program is user written, check
    the program.


    ORA-06502 PL/SQL: numeric or value error string
    Cause: An arithmetic, numeric, string, conversion, or constraint error occurred.
    For example, this error occurs if an attempt is made to assign the value NULL
    to a variable declared NOT NULL, or if an attempt is made to assign an integer
    larger than 99 to a variable declared NUMBER(2).
    Action: Change the data, how it is manipulated, or how it is declared so that
    values do not violate constraints.

    If folks can add to this list it will be awesome.

    Thanks very much.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •