Kbase P152462: Using PHP core dumps when running odbc queries
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
09/09/2009 |
|
Status: Unverified
SYMPTOM(s):
Using PHP core dumps when running odbc queries
FACT(s) (Environment):
PHP with 10.0B worked fine.
SQL Queries run with Test C program within proenv work fine.
UNIX
Progress 9.x
OpenEdge 10.x
CHANGE:
Migrating from 10.0B to 10.2A
CAUSE:
PHP or any similar 3rd party program must have access to the ODBC libraries shipped with Progress / OpenEdge.
FIX:
On Unix, review the slibod_env.
Make sure that all environment variables defined within the slibod_env are defined for PHP.
Within the script, slibod_env, there are specific definitions dependent on operating system.
For the sections which are operating system specific, only set those variables that are for the OS in use.
Example from the slibod_env which uses the "uname" function and a case statement to determine the proper variables to be set within the script:
OSNAME=`uname`
case "$OSNAME" in
"SunOS") # Sun Solaris v2.5.1/v2.6
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ODBC/lib
export LD_LIBRARY_PATH
;;
"HP-UX") # HP UNIX, v11.00, v10.20
SHLIB_PATH=$SHLIB_PATH:$ODBC/lib
export SHLIB_PATH
;;
"AIX") # IBM UNIX v4.2/v4.3
LIBPATH=$LIBPATH:$ODBC/lib
export LIBPATH
;;
"OSF1") # Digital UNIX
echo "WARNING: not setting shared library include path"
;;
"UnixWare") # Unixware 7
echo "WARNING: not setting shared library include path"
;;
"Linux")
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ODBC/lib
export LD_LIBRARY_PATH
PROLIBPATH=$LD_LIBRARY_PATH; export PROLIBPATH
;;
*) # SCO OpenServer/etc.
echo "WARNING: not setting shared library include path"
;;
esac