Demonstrating that my variables are set correctly and that sqlplus
makes the connection:
$ sqlplus $my_user/$my_pw@$my_db_sid
SQL*Plus: Release 10.2.0.1.0 - Production on Fri Mar 12 11:23:04
2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit
Production
With the Partitioning, Oracle Label Security, OLAP and Data Mining
Scoring Engine options
SQL>
And using sqlpython:
$ sqlpython "oracle://${my_user}:${my_pw}@${my_db_sid}"
/bin/sh: xclip: not found
Connection failure.
Opens the DB connection. Some sample valid connection strings:
[connect help deleted by wam]
SQL.No_Connection>
Note that even though I have a connection failure, the help message
for connect still is displayed, even though my URL is correct (or at
least it appears to be).
I then tried connecting with the specific connection parameters:
Using sqlplus:
$ sqlplus "${my_user}/${my_pw}
@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=$my_ip)
(PORT=1521)))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=
$my_db_name)))"
<snipped>
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit
Production
With the Partitioning, Oracle Label Security, OLAP and Data Mining
Scoring Engine options
SQL>
Using sqlpython with URL syntax:
$ sqlpython "oracle://${my_user}:${my_pw}@${my_ip}:1521/$
{my_db_name}"
/bin/sh: xclip: not found
Connection failure.
Opens the DB connection. Some sample valid connection strings:
[snip]
SQL.No_Connection>
Using sqlpython with option syntax:
$ sqlpython --oracle -U ${my_user} --password ${my_pw} -H ${my_ip} -
p 1521 -d ${my_db_name}
/bin/sh: xclip: not found
Existing connections:
SQL.No_Connection>
Note that in that last invocation, I didn't snip any output at all.
There was no "Connection failure" message. There was no help message
displayed. But, there also was no valid connection. Any assistance or
pointers would very much be appreciated.
-- William
P.S. This is all being run from an Ubuntu 9.10 (Karmic) system with
the Oracle Client 10G Express Edition (oracle-xe-
client_10.2.0.1-1.0_i386.deb) installed.
-- William
--
You received this message because you are subscribed to the Google Groups "sqlpython" group.
To post to this group, send email to sqlp...@googlegroups.com.
To unsubscribe from this group, send email to sqlpython+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/sqlpython?hl=en.
I am also running oracle but cannot connect and do not get any error
message of the failure:
<code>
[me@MacBook software]$ sqlplus $dbuser/$dbp...@test.worldSQL*Plus:
Release 10.2.0.4.0 - Production on Sat Mar 20 22:00:07 2010
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit
Production
With the Partitioning, Real Application Clusters, OLAP, Data Mining
and Real Application Testing options
SQL>
</code>
now with sqlpython :
<code>
[me@MacBook software]$ sqlpython oracle://moodle:m00...@test.WORLD
/bin/sh: xclip: command not found
Connection failure.
Opens the DB connection. Some sample valid connection strings:
</code>
My environment :
<code>
[me@MacBook software]$ sudo easy_install sqlpython
Password:
Searching for sqlpython
Best match: sqlpython 1.7.1
Processing sqlpython-1.7.1-py2.6.egg
sqlpython 1.7.1 is already the active version in easy-install.pth
Installing sqlpython script to /usr/local/bin
Installing editplot_sqlpython script to /usr/local/bin
Using /Library/Python/2.6/site-packages/sqlpython-1.7.1-py2.6.egg
Processing dependencies for sqlpython
Finished processing dependencies for sqlpython
[me@MacBook software]$ echo $ORACLE_HOME
/Users/binneyd/software/oracle/instant_client
[me@MacBook software]$ echo $TNS_ADMIN
/Users/binneyd/software/oracle/network/admin
[me@MacBook software]$ echo $SQLPATH
/Users/binneyd/software/oracle/instant_client
</code>
I have tried a lot of variations but all ending up at the same place
so nor sure where to go from here since there is not real error
message?
cheers dave
On Mar 18, 4:35 am, Catherine Devlin <catherine.dev...@gmail.com>
wrote:
> > sqlpython+...@googlegroups.com<sqlpython%2Bunsubscribe@googlegroups .com>
> > .
> > For more options, visit this group at
> >http://groups.google.com/group/sqlpython?hl=en.
>
> --
> - Catherinehttp://catherinedevlin.blogspot.com/
> > Note that even though I have aconnectionfailure, the help message
> > There was no "Connectionfailure" message. There was no help message
> > displayed. But, there also was no validconnection. Any assistance or
> [me@MacBook software]$ sqlplus $dbuser/$dbp...@test.worldSQL*Plus:
<snip>
> Connected to:
> Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit
> now with sqlpython :
> [me@MacBook software]$ sqlpython oracle://moodle:m00...@test.WORLD
> /bin/sh: xclip: command not found
> Connection failure.
It's hard to diagnose the problems since you go from using shell
environment variables in the sqlplus invocation to using the literal
username and password in the sqlpython invocation. Assuming your
dbuser is moodle and the pw is actually m00dl3, then the only other
thing I see that might explain the issue is that you go from trying to
connect to test.world to connecting to test.WORLD. Beyond the change
in capitalization, I've not seen an oracle database name with a dot in
it before, which leads me to believe the database is likely named
'test' and the '.world' is probably a schema or a connection
parameter. You may want to try specifying that as test/world with
sqlpython, e.g.:
$ sqlpython oracle://moodle:m00dl3@test/world
Hope this helps.
-- William
But now that i have connected it seems to never actually get the
metadata so i cannot use any of the nice features anyway ;( ??
On Mar 22, 2:27 am, William McVey <w...@wamber.net> wrote:
It took a *long* time (over an hour) for the metadata to be retrieved
on my database as well using 1.7.1. I went ahead and cloned the source
repository so I could try older versions. Interestingly, in versions
1.5.0 and 1.6.0 (both of which appear to have used the cx_Oracle lib
as the main db backend) the 'ls' command got the metadata and
completed in under 10 seconds. I don't know if some pre-calculations
were happening on initial connect, but the entire session from
password entry to getting ls output was less than 5 minutes (probably
closer to 2). As soon as we cross into 1.7 land (where the backend was
replaced with gerald library), the time to retrieve and calculate the
metadata becomes crazy long.
-- William
P.S. Note that if you want to backrev to old versions of sqlpython,
you're going to need to remove your current versions of cmd2 and
install the version of cmd2 that was around at the time of the release
of sqlpython. Based on my testing, API differences between cmd2 are
such that the current version of cmd2 can't be used for old sqlpython.
For example, even though the setup.py for sqlpython 1.6.0 specifies
the needed version of the cmd2 library as 'cmd2>=0.4.7'. If you use
cmd2 0.6.1 with it, you'll get:
AttributeError: 'StubbornDict' object has no attribute 'sort'
Once you've removed the old cmd2, you can install a specific version
with 'pip install cmd2==0.4.7'
On Mon, Mar 22, 2010 at 7:46 AM, donkeyx <donke...@gmail.com> wrote:It took a *long* time (over an hour) for the metadata to be retrieved
> But now that i have connected it seems to never actually get the
> metadata so i cannot use any of the nice features anyway ;( ??
on my database as well using 1.7.1. I went ahead and cloned the source
repository so I could try older versions. Interestingly, in versions
1.5.0 and 1.6.0 (both of which appear to have used the cx_Oracle lib
as the main db backend) the 'ls' command got the metadata and
completed in under 10 seconds. I don't know if some pre-calculations
were happening on initial connect, but the entire session from
password entry to getting ls output was less than 5 minutes (probably
closer to 2). As soon as we cross into 1.7 land (where the backend was
replaced with gerald library), the time to retrieve and calculate the
metadata becomes crazy long.
-- William
P.S. Note that if you want to backrev to old versions of sqlpython,
you're going to need to remove your current versions of cmd2 and
install the version of cmd2 that was around at the time of the release
of sqlpython. Based on my testing, API differences between cmd2 are
such that the current version of cmd2 can't be used for old sqlpython.
For example, even though the setup.py for sqlpython 1.6.0 specifies
the needed version of the cmd2 library as 'cmd2>=0.4.7'. If you use
cmd2 0.6.1 with it, you'll get:
AttributeError: 'StubbornDict' object has no attribute 'sort'
Once you've removed the old cmd2, you can install a specific version
with 'pip install cmd2==0.4.7'