SQL10007N with connect over PHP Zend
- Dieses Thema hat 1 Antwort und 1 Teilnehmer, und wurde zuletzt aktualisiert vor 16 Jahre, 2 Monaten von
Anonym.
-
AuthorPosts
-
25. Juli 2007 um 5:26 Uhr #2789
AnonymInaktivHi all.
i have a big problem since 2 weeks to connect DB2 ESE V9 FP2 over Zend PHP Version 5.2.1. When i work on commandline or with db2cc everithing works fine.
Be shure I READ ALL ERROR descriptions what I find in internet !!!
If I Start my Webpage http://www.a-t-c.ch and want to login (this did a db2_connect or db2_pconnect then i get an error.
Persistent Connection to ATC failed.
08001 [IBM][CLI Driver] SQL10007N Message "0" could not be retrieved. Reason code: "3". SQLCODE=-1013In Error.log from Apche i find:
[Wed Jul 25 06:20:33 2007] [error] [client 127.0.0.1] PHP Warning: db2_prepare() expects parameter 1 to be resource, boolean given in /usr/local/Zend/apache2/htdocs/sites/login.php on line 23, referer: http://localhost/sites/men_left.phpAttached you find my php.ini and httpd.conf.
Who can help ?
Thanks a lot Gert
[PHP]
;;;;;;;;;;;;;;;;;;;
; About php.ini ;
;;;;;;;;;;;;;;;;;;;
; This file controls many aspects of PHP’s behavior. In order for PHP to
; read it, it must be named ‚php.ini‘. PHP looks for it in the current
; working directory, in the path designated by the environment variable
; PHPRC, and in the path that was defined in compile time (in that order).
; Under Windows, the compile-time path is the Windows directory. The
; path in which the php.ini file is looked for can be overridden using
; the -c argument in command line mode.
;
; The syntax of the file is extremely simple. Whitespace and Lines
; beginning with a semicolon are silently ignored (as you probably guessed).
; Section headers (e.g. [Foo]) are also silently ignored, even though
; they might mean something in the future.
;
; Directives are specified using the following syntax:
; directive = value
; Directive names are *case sensitive* – foo=bar is different from FOO=bar.
;
; The value can be a string, a number, a PHP constant (e.g. E_ALL or M_PI), one
; of the INI constants (On, Off, True, False, Yes, No and None) or an expression
; (e.g. E_ALL & ~E_NOTICE), or a quoted string ("foo").
;
; Expressions in the INI file are limited to bitwise operators and parentheses:
; | bitwise OR
; & bitwise AND
; ~ bitwise NOT
; ! boolean NOT
;
; Boolean flags can be turned on using the values 1, On, True or Yes.
; They can be turned off using the values 0, Off, False or No.
;
; An empty string can be denoted by simply not writing anything after the equal
; sign, or by using the None keyword:
;
; foo = ; sets foo to an empty string
; foo = none ; sets foo to an empty string
; foo = "none" ; sets foo to the string ’none‘
;
; If you use constants in your value, and these constants belong to a
; dynamically loaded extension (either a PHP extension or a Zend extension),
; you may only use these constants *after* the line that loads the extension.
;
;
;;;;;;;;;;;;;;;;;;;
; About this file ;
;;;;;;;;;;;;;;;;;;;
; This is the recommended, PHP 5-style version of the php.ini-dist file. It
; sets some non standard settings, that make PHP more efficient, more secure,
; and encourage cleaner coding.
;
; The price is that with these settings, PHP may be incompatible with some
; applications, and sometimes, more difficult to develop with. Using this
; file is warmly recommended for production sites. As all of the changes from
; the standard settings are thoroughly documented, you can go over each one,
; and decide whether you want to use it or not.
;
; For general information about the php.ini file, please consult the php.ini-dist
; file, included in your PHP distribution.
;
; This file is different from the php.ini-dist file in the fact that it features
; different values for several directives, in order to improve performance, while
; possibly breaking compatibility with the standard out-of-the-box behavior of
; PHP. Please make sure you read what’s different, and modify your scripts
; accordingly, if you decide to use this file instead.
;
; – register_globals = Off [Security, Performance]
; Global variables are no longer registered for input data (POST, GET, cookies,
; environment and other server variables). Instead of using $foo, you must use
; you can use $_REQUEST["foo"] (includes any variable that arrives through the
; request, namely, POST, GET and cookie variables), or use one of the specific
; $_GET["foo"], $_POST["foo"], $_COOKIE["foo"] or $_FILES["foo"], depending
; on where the input originates. Also, you can look at the
; import_request_variables() function.
; Note that register_globals is going to be depracated (i.e., turned off by
; default) in the next version of PHP, because it often leads to security bugs.
; Read http://php.net/manual/en/security.registerglobals.php for further
; information.
; – register_long_arrays = Off [Performance]
; Disables registration of the older (and deprecated) long predefined array
; variables ($HTTP_*_VARS). Instead, use the superglobals that were
; introduced in PHP 4.1.0
; – display_errors = Off [Security]
; With this directive set to off, errors that occur during the execution of
; scripts will no longer be displayed as a part of the script output, and thus,
; will no longer be exposed to remote users. With some errors, the error message
; content may expose information about your script, web server, or database
; server that may be exploitable for hacking. Production sites should have this
; directive set to off.
; – log_erro
25. Juli 2007 um 22:24 Uhr #3176
AnonymInaktivHI,
i find the problem in db2diag.log.The file (/opt/ibm/db2/V9.1/lib32/libdb2gcf.so.1) is there and also i
/home/db2inst2/sqllib/lib.How can i correct this problem ?
2007-07-25-23.45.07.008383+120 I302018G390 LEVEL: Info
PID : 25738 TID : 3079657152
FUNCTION: DB2 Common, Fault Monitor Facility, fmGetGcfModuleName, probe:30
MESSAGE : ECF=0x90000373 The gcf module to be loaded does not follow name
convention libgcf[XXX]
DATA #1 : String, 38 bytes
/opt/ibm/db2/V9.1/lib32/libdb2gcf.so.1
DATA #2 : String, 14 bytes
libdb2gcf.so.1
-
AuthorPosts
You must be logged in to reply to this topic.