Thanks to all for supporting this to fix the issue. So issue is resolved by adding these 2 lines in "app.wsgi"
os.environ["LD_LIBRARY_PATH"] = "/opt/app/oracle/products/11.2.0/lib" os.environ["ORACLE_HOME"] = "/opt/app/oracle/products/11.2.0" Thanks again for helping to fix this issue. Its really a superb forum to fix the issue so quickly. :-) Regards, Kamal On Sun, Apr 24, 2011 at 7:58 PM, Ian <[email protected]> wrote: > On Apr 23, 12:29 pm, kamal sharma <[email protected]> wrote: > > No it was .profile of mine. Now I have set the LD_LIBRARY_PATH in > app.wsgi > > as mentioned below and when I print the os.environ in the beginning of > > views.py then it shows that newly added value. > > It's clear that your LD_LIBRARY_PATH is fine at this point, since the > library must be loaded in order to get the ORA-01804 error. The > problem, as Jirka and I have suggested, is that the rest of your > Oracle installation is still not visible to the process, which is > preventing the client from reading its data files. Why this is the > case is unclear without knowing more details about your system. Is > the Oracle directory readable by the WSGI user? Is the WSGI process > running inside a chroot jail? > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
