StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POoci_connect Blank Page in PHP
text
Body
copied!<h2><strong><em>UPDATE (5/21/2010) SUCCESS!</em></strong></h2> <p>So after MUCH $head->desk()'ing, I've solved it.</p> <p>Remember kids, be wary of the instant client version you use, dependent on the virtualization settings!</p> <p>I had been installing the generic Instant Client (not aware our ESX servers sit on AMD processors, not Intel) and that worked fine internally (the CentOS install was 32-bit since our internal ESXi servers aren't 64-bit). Well lo-and-behold, even if you have a 32-bit install running on a virtualized server which is sitting on an AMD64, it still matters what instant client you install.</p> <p>It was the last thing I thought to check but as it appears, everything is running fine now.</p> <p>I would like to thank everyone who helped me run through every possible test to figure this out but in the end, it was my fault for not realizing the differences in the virtualizations.</p> <hr> <p><strong><em>UPDATE (5/21/2010)</em></strong> I thought this bug had escaped me when I installed it on a new VM internally but I have now found a narrowing link.</p> <p>I was trying to install this on our production server when I posted this. After a week of no progress and in need to get back to development, I outfitted a VM on our internal server with a brand new install of Crap... CentOS, and fresh installs of instant client and oci8.</p> <p>Worked perfectly.</p> <p>However we just uploaded an exact copy of the VM to our production servers and it magically no longer works. Tried reinstalling everything, no avail.</p> <p>So the only things I could narrow it down to is a firewall issue (although I get the same issue when trying 127.0.0.1) or possibly an ESX (our production servers) server issue, internal servers are running ESXi.</p> <p>Any thoughts?</p> <p><strong><em>UPDATE (3/8/2010)</em></strong> I installed Xdebug and have it tracing my code. This is the output I am getting:</p> <pre><code>TRACE START [2010-03-08 17:53:05] 0.2090 327864 -> {main}() /data/aims3/http/octest.php:0 0.2091 327988 -> ini_set(string(14), string(1)) /data/aims3/http/octest.php:3 0.2093 327920 -> error_reporting(long) /data/aims3/http/octest.php:4 0.2094 328048 -> oci_connect(string(8), string(8), string(25)) /data/aims3/http/octest.php:6 </code></pre> <p>The trace halts at that point.</p> <p>I have installed everything the same way on a local server and it works fine. To say I am at a complete loss would be putting it lightly.</p> <hr> <p><strong>*NOTE</strong>: I ran make test and it returned FAIL on every test. I never ran this on my working machine to see if it reports the same errors. Any idea why make test would report FAIL but make doesn't report any error?</p> <p>I've installed the Oracle Instantclient with no reported errors along with the OCI8 PECL package and at a loss. Whenever I try to open a connection with oci_connect, it halts my entire PHP script.</p> <p>EXAMPLE:</p> <pre><code><?php ini_set ("display_errors", "1"); error_reporting(E_ALL); echo "before"; $conn = oci_connect("username", "password", "host"); echo "after"; ?> </code></pre> <p>Returns a complete blank page. The module is loaded (seen in phpinfo) and everything installed with no errors.</p> <p>I am at a complete loss.</p> <p>CentOS: 5.4</p> <p>Apache: 2.2.3</p> <p>PHP: 5.3.1</p> <p>InstantClient: 11.2</p> <p>oci8: 1.4.1</p> <p>Any thoughts?</p> <p><strong>NOTES</strong></p> <p>Apache Error Log reports nothing</p> <p><strong>Attempted Debugging:</strong></p> <p>1:</p> <pre><code><?php ini_set ("display_errors", "1"); error_reporting(E_ALL); echo "before"; if(!function_exists('oci_connect')) die('Oracle Not Installed'); echo "after"; ?> </code></pre> <p>Returns: </p> <pre><code>beforeafter </code></pre> <p>2:</p> <p>Changing host to //host</p> <p>Returns:</p> <p>Same error</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload