in reply to Better DBD::Oracle error messages

One thing you can do is check out the trace method in the DBI doccumentation; that won't help much with those nasty ORA-3.837613847631E08 type error messages much, though. I still have to keep a copy of the Oracle documentation handy (try technet.oracle.com if you don't have a local copy).

If there are even better ways, I'd like to hear them too.

HTH

Philosophy can be made out of anything. Or less -- Jerry A. Fodor

Replies are listed 'Best First'.
Re: Re: Better DBD::Oracle error messages
by elwarren (Priest) on Apr 21, 2001 at 00:04 UTC
    On *nix machines oracle provides the command line oerr utility. It can be very handy. Usage is simple, just give it your error code and it gives you (somewhat) more info:
    $ oerr ora 12450
    12450, 00000, "LOB datatype disabled in LBAC initialization file"
    // *Cause:  You tried to specify a LOB datatype for a column or attribute,
    //          but the use of the LOB datatype has been disabled.
    // *Action: Change the LBAC initialization file to allow the creation
    //          of LOB columns and attributes.