Re: [PHP-DB] Intermittent odbc_connect() problem with iodbc/openlink
Assuming you always connect to the server using the exact parameter values for odbc_connect(), this does not look like an easy one to solve. I also connect to a Sybase database on a Win2K server from PHP/Apache/Solaris. However, I don't use the odbc extension. I use the odbtp extension, which works very well, and has better support. So, you probably will have better results with odbtp, which is available at http://odbtp.sourceforge.net. On Wed, 16 Feb 2005, Crone, James wrote: I'm having intermittent problems with odbc_connect(). Here's the situation I'm trying to connect to a Sybase Adaptive Server Anywhere database running on Win2K from my web server using Solaris, Apache, PHP, iODBC, and OpenLink's ODBC universal data access driver for MSSQL/Sybase. About 75% of the time, my php scripts talk to the Sybase system fine. However, the other 25% of the time nothing really happens. IE reports a Page cannot be displayed error, while Firefox acts like it may do something for a fraction of a second, but then just stays on the currently loaded page. -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DB] Intermittent odbc_connect() problem with iodbc/openlink
Crone, James wrote: I'm having intermittent problems with odbc_connect(). Here's the situation I'm trying to connect to a Sybase Adaptive Server Anywhere database running on Win2K from my web server using Solaris, Apache, PHP, iODBC, and OpenLink's ODBC universal data access driver for MSSQL/Sybase. About 75% of the time, my php scripts talk to the Sybase system fine. However, the other 25% of the time nothing really happens. IE reports a Page cannot be displayed error, while Firefox acts like it may do something for a fraction of a second, but then just stays on the currently loaded page. I have tracing turned on in iODBC. When things work fine, a lengthy trace file is generated and everything seems to be in order. When things don't work, all I get is the following: [snip] No connect errors are generated either in the trace file or in the browser's display. It's almost as if the process just dies without saying anything about why it happened. [snip] What do your servers error logs say? This sounds suspiciously like the behavior one gets when php runs out of memory. If so, it should have an Unable to allocate # bytes type message in the error log. Check that, and increase memory_limit in your php.ini if this is the case. Cheers, -- - Martin Norland, Sys Admin / Database / Web Developer, International Outreach x3257 The opinion(s) contained within this email do not necessarily represent those of St. Jude Children's Research Hospital. -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DB] Intermittent odbc_connect() problem with iodbc/openlink
I'm having intermittent problems with odbc_connect(). Here's the situation I'm trying to connect to a Sybase Adaptive Server Anywhere database running on Win2K from my web server using Solaris, Apache, PHP, iODBC, and OpenLink's ODBC universal data access driver for MSSQL/Sybase. About 75% of the time, my php scripts talk to the Sybase system fine. However, the other 25% of the time nothing really happens. IE reports a Page cannot be displayed error, while Firefox acts like it may do something for a fraction of a second, but then just stays on the currently loaded page. I have tracing turned on in iODBC. When things work fine, a lengthy trace file is generated and everything seems to be in order. When things don't work, all I get is the following: -- ** iODBC Trace file ** ** started on Wed Feb 16, 20:29 ** Application 0001 ENTER SQLAllocEnv SQLHENV * 2f3158 Application 0001 EXIT SQLAllocEnv with return code 0 (SQL_SUCCESS) SQLHENV * 2f3158 (30af78) Application 0001 ENTER SQLAllocConnect SQLHENV 30af78 SQLHDBC * 2f315c Application 0001 EXIT SQLAllocConnect with return code 0 (SQL_SUCCESS) SQLHENV 30af78 SQLHDBC * 2f315c (2dbbc8) Application 0001 ENTER SQLConnect SQLHDBC 2dbbc8 SQLCHAR * 30c7e0 | PF32 | SQLSMALLINT -3 (SQL_NTS) SQLCHAR * 2f5b10 | viewaward | SQLSMALLINT -3 (SQL_NTS) SQLCHAR * ff0c4a28 | | SQLSMALLINT -3 (SQL_NTS) -- No connect errors are generated either in the trace file or in the browser's display. It's almost as if the process just dies without saying anything about why it happened. Any ideas? Thanks, Jim __ Jim Crone Electronic Communications Manager Bradley University E-mail: [EMAIL PROTECTED] Phone: 1-800-447-6460 Fax: 309-677-2797 Discover a university experience that will prepare you for a lifetime of personal and professional achievement at: http://admissions.bradley.edu/ http://admissions.bradley.edu/
