Oops! I was thinking about a different problem, and realized that I gave you some bad information. Please disregard the last message.
I will paste some of the installation instructions for the Oracle Full Client I wrote up for my organization: Create a Linux user called 'oracle'. Create the directory /client and set its ownership to oracle:oracle. This is where the Oracle client will be installed. Install Oracle client: Log in as user oracle Copy the Oracle *Full Client* install package to /tmp, unzip it, and run the installer: /tmp/client/runInstaller Select the 'Administrator' installation option Set the Oracle Base to /client/oracle/product/11.2.0 and the Software Location to /client/oracle/product/11.2.0/db Leave the Inventory Directory as the default: /client/oracle/product/oraInventory Leave the oraInventory Group Name as the default: oracle Install pre-requisite packages and scripts noted in the installation process... (Note that the "pdksh" library is a little hard to find. You can get it here: http://rpmfind.net/linux/rpm2html/search.php?query=pdksh) Execute the installation Now you'll need to fix some linking errors... To fix Oracle library linking: Navigate to /client/oracle/product/11.2.0/db/lib/ Remove file libexpat.so.1 As user oracle: Create a symbolic link: libexpat.so.1 --> libexpat.so.1.5.2 As root: Create a file called 'oracle.sh'. It should contain these two lines: export ORACLE_HOME=/client/oracle/product/*11.2.0*/db # Note, you may need to change the version number here to match your client version. export PATH=$PATH:$ORACLE_HOME/bin Move 'oracle.sh' to /etc/profile.d/ Add a line "LD_LIBRARY_PATH=/client/oracle/product/11.2.0/db/lib/" to /etc/sysconfig/httpd Every time apache is started it will set LD_LIBRARY_PATH specifically it. That way, LD_LIBRARY_PATH isn't set globally. All done! Hope this helps! On Wed, May 15, 2013 at 9:07 AM, Dylan Klomparens < dylan.klompar...@gmail.com> wrote: > This bug was filed as ticket 19720 ( > https://code.djangoproject.com/ticket/19720) and resolved. It should not > be a problem if you are using version 1.4.* or 1.5.* of Django. > Additionally, the fact that you get the same information when you attempt > to login with another SQL client leads me to believe there is something > about the database is not set up right. > > -- Dylan > > > On Wed, May 15, 2013 at 5:43 AM, Michael Van <fanlinsh...@gmail.com>wrote: > >> I have the same error when python managment runserver : >> cx_Oracle.DatabaseError: ORA-28547: connection to server failed, probable >> Oracle Net admin error >> and this Error infomation is the same when I type sqlplus try to login. >> My os is Xubuntu13.10, and I installed oracle-instance on ubuntu, >> so I think that the instance is somewhere error, but I don't konw where >> it is. >> >_< >> 在 2013年1月25日星期五UTC+8上午6时27分22秒，Dylan Klomparens写道： >> >>> I have a Django program that is connecting to an Oracle database. In my >>> settings.py file I have this configuration: >>> >>> DATABASES = { >>> 'default': { >>> 'ENGINE': 'django.db.backends.oracle', >>> 'NAME': 'xe', >>> 'USER': 'MY_USER_NAME', >>> 'PASSWORD': 'abcdefghijklmnopqrstuvwxyz', >>> 'HOST': 'db_server.example.com', >>> 'PORT': '1234', >>> }} >>> >>> I received a strange error when attempting to load the website: >>> >>> ORA-28547: connection to server failed, probable Oracle Net admin error >>> >>> After further investigation, I sniffed the TCP traffic between the >>> webserver and the database server. I discovered this text in the network >>> communication, which I reformatted for this post: >>> >>> (DESCRIPTION= >>> (ADDRESS= >>> (PROTOCOL=TCP) >>> (HOST=1.2.3.4) >>> (PORT=1234) >>> ) >>> (CONNECT_DATA= >>> (SID=xe) >>> (CID= >>> (PROGRAM=httpd@webserver_**hostname) >>> (HOST=webserver_hostname) >>> (USER=apache) >>> ) >>> )) >>> >>> So my question is: why is Django attempting to connect to the Oracle >>> database with different credentials than the ones I specified? Notably, it >>> is attempting to use user 'apache' instead of 'MY_USER_NAME'. The database >>> host IP, port, and SID are correct and what I specified. It just appears to >>> be the user name that is different. >>> >>> (As a side note, I suppose the password is transmitted separately in a >>> later portion of the log in process?) >>> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Django users" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/django-users/WnLejpFfUsE/unsubscribe?hl=en >> . >> To unsubscribe from this group and all its topics, send an email to >> django-users+unsubscr...@googlegroups.com. >> >> To post to this group, send email to django-users@googlegroups.com. >> Visit this group at http://groups.google.com/group/django-users?hl=en. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
