By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,321 Members | 1,194 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,321 IT Pros & Developers. It's quick & easy.

Connectstring with SQL*Loader

P: n/a
I have a problem trying to run SQL*Loader after migrating to Oracle 9.
It used to run with no hicups on Oracle 8i, and I'm at my wits' end.
Any help?

I'm trying to run SQL*Loader from a command prompt (I'm on Oracle 9i
R1 and WinXP professional), and fail to connect to the database.

The command at the promt is like this:

sqlldr bbc/password@bbc control = C:\...path to controlfile

SQL*Loader then runs but fails with the message, that TNS cannot
resolve the servicename (ORA-12154).

I know, and have re-checked, that the service "bbc" IS defined.

If I then retry without naming the service, I would expect SQL*Loader
to connect to my local (default) database, which happens to be the
same as the one defined in "bbc". Same problem, same message.

I can, with absolutly no problem, run SQL*Plus from a commandline,
invoking it with the same connectstring. It works fine, both with and
without specifying the servicename.

I'm almost out of hair to tear out now. Anyone can give me a clue?

Best,

Bo Brunsgaard
Vitus Bering CVU.
Jul 19 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
"Bo Brunsgaard" <bb**********@hotmail.com> schrieb im Newsbeitrag
news:55**************************@posting.google.c om...
I have a problem trying to run SQL*Loader after migrating to Oracle 9. It used to run with no hicups on Oracle 8i, and I'm at my wits' end.
Any help?

I'm trying to run SQL*Loader from a command prompt (I'm on Oracle 9i
R1 and WinXP professional), and fail to connect to the database.

The command at the promt is like this:

sqlldr bbc/password@bbc control = C:\...path to controlfile

SQL*Loader then runs but fails with the message, that TNS cannot
resolve the servicename (ORA-12154).

I know, and have re-checked, that the service "bbc" IS defined.

If I then retry without naming the service, I would expect SQL*Loader to connect to my local (default) database, which happens to be the
same as the one defined in "bbc". Same problem, same message.

I can, with absolutly no problem, run SQL*Plus from a commandline,
invoking it with the same connectstring. It works fine, both with and without specifying the servicename.

I'm almost out of hair to tear out now. Anyone can give me a clue?

Best,

Bo Brunsgaard
Vitus Bering CVU.


Hi Bo,

is there any chance that your sqlldr and
the sqlplus that you use reside in different
oracle homes?

Just a guess...

Greetings,
Guido
Jul 19 '05 #2

P: n/a
"Guido Konsolke" <Gu************@triaton.com> wrote in message news:<10***************@news.thyssen.com>...
is there any chance that your sqlldr and
the sqlplus that you use reside in different
oracle homes?

Just a guess...

Greetings,
Guido


And a very good guess too!

Some time back, I installed Oracle Warehouse Builder. It installed in
a new Oracle Home. Behind my back, it installed a new SQLLDR.exe in
the new home. Then the $@ bugger altered the Windows path, so the
path to the new .exe comes BEFORE the old one. So when I try to
execute the program, it finds the version in the wrong ORAHOME, and
poooffff - there goes the neighbourhood.

Which, of course, explains why SQL*PLUS ran with no problems. OWB
didn't include a .exe of that one, so Windows faithfully looked
further on in the path and found it in the correct home

Thanks a lot, Guido.

/Bo
Jul 19 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.