Forum Stats

  • 3,872,498 Users
  • 2,266,434 Discussions
  • 7,911,226 Comments

Discussions

Oerr: String to number conversion failed in Oerr. [FIXED in 21.4]

User_2DKLA
User_2DKLA Member Posts: 63 Blue Ribbon
edited Dec 17, 2021 3:16PM in SQLcl

Hello,

SQL> show version
Oracle SQLDeveloper Command-Line (SQLcl) version: 21.3.1.0 build: 21.3.1.281.1748 

SQL> oerr -v

19.3

SQL> oerr ora 39826

Oerr: String to number conversion failed in Oerr

There seems to be a range of error codes between 34500 (give or take a few) and 40000 which trigger the above error.

The oerr binary from the full Oracle client returns the error details successfully:

: $ORACLE_HOME/bin/oerr ora 39826

39826, 0000, "Direct path load of view or synonym (%s.%s) could not be resolved."
// *Cause:   A synonym or view could not be translated.
// *Action:  Verify that the view or synonym is valid.

This is different from trying a non-existent error code:

SQL> oerr ora 1067

Oerr: No match found in Oerr.

ORA-01067 does not exist, so the above "No match" answer is correct. In any case, "String to number conversion failed in Oerr" doesn't look right.

Remark: same behaviour in SQL Developer 21.2.1.

Just thought I'd mention it...

Regards,

Best Answer

Answers

  • User_2DKLA
    User_2DKLA Member Posts: 63 Blue Ribbon

    Re-tested with the latest version:

    SQL>  show version
    Oracle SQLDeveloper Command-Line (SQLcl) version: 21.3.2.0 build: 21.3.2.287.1503
    
    SQL>  oerr ora 39826
    
    Oerr: String to number conversion failed in Oerr.
    

    Same error.

    Regards,

  • User_2DKLA
    User_2DKLA Member Posts: 63 Blue Ribbon
    Answer ✓

    Hello,

    SQLcl 21.4 fixes it. Thanks! 😊

    As reported by oerr -v, the included messages are from Oracle Database version 21.3.

    (And I can see there is an ORA-01067 error in that version...)

    Regards,