Skip to content

ORA-20202: Invalid path format: NULL #39

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
vasso123 opened this issue Sep 27, 2017 · 5 comments
Closed

ORA-20202: Invalid path format: NULL #39

vasso123 opened this issue Sep 27, 2017 · 5 comments
Assignees
@pesse
Milestone
v3.0.4

Comments

@vasso123
Copy link

vasso123 commented Sep 27, 2017 •
edited
Loading

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)
@Prismapanda
Copy link

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.

@vasso123
Copy link
Author

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

@jgebal
Copy link
Member

jgebal commented Oct 26, 2017

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?

@viniciusam
Copy link
Member

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

@viniciusam viniciusam mentioned this issue Oct 26, 2017
Merged
@vasso123
Copy link
Author

Now it works for me also, thanks!

@pesse pesse mentioned this issue Nov 12, 2017
Closed
@pesse pesse added this to the v3.0.4 milestone Nov 13, 2017
@pesse pesse mentioned this issue Nov 17, 2017
Merged
@pesse pesse self-assigned this Nov 17, 2017
@pesse pesse closed this as completed in #47 Nov 19, 2017
pesse added a commit that referenced this issue Nov 19, 2017
@pesse
Merge pull request #47 from utPLSQL/feature/compatibility_and_ora_libs
db15344 
Feature/compatibility and ora libs

Fixes several issues around compatibility

Fixes #44
Fixes #41
Fixes #39
Fixes #38
@pesse pesse removed the in progress label Nov 19, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pesse pesse

Labels
None yet
Projects
None yet
Milestone
v3.0.4
Development

No branches or pull requests
5 participants
@jgebal @viniciusam @Prismapanda @vasso123 @pesse