Skip to content

ORA-20202: Invalid path format: NULL #39

Closed

Description

@vasso123

With a fresh utplsql install on a 11g database, when trying to run tests with utplsql-cli, I get this error:

$ ./utplsql run scott/tiger@devdbas:1521/dev.world -c
ORA-20202: Invalid path format: NULL
ORA-06512: at "UT3.UT_RUNNER", line 99
ORA-06512: at line 1

Closed Connection

I inspected the problem, and it seems that the a_paths array arrives empty in the ut_runner.run procedure, even though utplsql-cli sends 'scott' in it.

  • tested on Ubuntu 16.04
  • Oracle Java used:
$ java -version
java version "1.8.0_131"
Java(TM) SE Runtime Environment (build 1.8.0_131-b11)
Java HotSpot(TM) 64-Bit Server VM (build 25.131-b11, mixed mode)

Activity

  1. Prismapanda commented on Oct 26, 2017

    @Prismapanda

    I had the same problem with an Oracle 11g database. With XE everthing worked fine.

    The problem has been be solved by adding the orai18n.jar to the classpath (add it to /lib dir and in utplsql.bat). Maybe it should be added by default? This was really nasty to trace back.

  2. vasso123 commented on Oct 26, 2017

    @vasso123
    Author

    I'll try it tomorrow. How did you figured it out?

  3. jgebal commented on Oct 26, 2017

    @jgebal
    Member

    The Oracle Doc - JDBC FAQ mentions

    orai18n.jar - Contains the configuration information to support all Oracle character sets in Advanced Data Types (objects). If the database character set is one other than UCS2,ASCII, ISO_LATIN_1, UTF8 and AL32UTF8 and the application uses ADTs, then you must include this file in your classpath.

    utPLSQL-cli communicates wuth utPLSQL using API with ADT's.

    To support different character sets, we would need to include the file in our client bundle.
    Expecting users to download it themselves and put it on classpath might lead to issues and dissatisfaction.

    @viniciusam - any thoughts?

  4. viniciusam commented on Oct 26, 2017

    @viniciusam
    Member

    Yes, we should bundle the library with the client and I'm already working on a PR for that.

  5. vasso123 commented on Oct 27, 2017

    @vasso123
    Author

    Now it works for me also, thanks!

  6. added this to the v3.0.4 milestone on Nov 13, 2017
  7. self-assigned this
    on Nov 17, 2017
  8. added a commit that references this issue on Nov 19, 2017
    db15344
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions