Deep recursion on subroutine "DBD::Oracle::AUTOLOAD" installing Bugzilla 3.1.3 with Oracle

RESOLVED INVALID

Status

()

RESOLVED INVALID
10 years ago
10 years ago

People

(Reporter: nrospide, Unassigned)

Tracking

3.1.3
Other
Linux

Details

(Reporter)

Description

10 years ago
User-Agent:       Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 2.0.50727)
Build Identifier: Bugzilla 3.1.3 with Oracle

I already run checksetup.pl several times as soon as possible to create "localconfig" file. Then, when I put all the connections details for Oracle Database and then run again checksetup.pl the next message appears:
Reading ./localconfig...
Checking for          DBD-Oracle (v1.19)   ok: found v1.21
Deep recursion on subroutine "DBD::Oracle::AUTOLOAD" at lib/i386-linux-thread-multi/DBD/Oracle.pm line 92, <DATA> line 225.
Out of memory!


Reproducible: Always

Steps to Reproduce:
1.Run checksetup.pl and install all mandatory perl modules.
2.Modify localconfig with all Oracle database connection details.
3.Run checksetup.pl
Actual Results:  
I can't use bugzilla as a new installation with Oracle.

Expected Results:  
I'd like to use bugzilla with Oracle.
(Reporter)

Updated

10 years ago
Version: unspecified → 3.1.3

Comment 1

10 years ago
  This is almost certainly a problem somewhere in your system, not with Bugzilla. That error message sounds like a bug with DBD::Oracle. Search Google for help, and maybe also ask on the support-bugzilla mailing list, described here:

  http://www.bugzilla.org/support/
Status: UNCONFIRMED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → INVALID
(Reporter)

Comment 2

10 years ago
I solved this issue.
I didn't configure the enough environment variables abour my Oracle database from the user is running checksetup.pl.
Thanks.
Resolution: INVALID → FIXED

Comment 3

10 years ago
(In reply to comment #2)
> I didn't configure the enough environment variables abour my Oracle database
> from the user is running checksetup.pl.

Which is exactly why this bug is invalid. FIXED means that we fixed the problem thanks to a patch, which is not the case here.
Resolution: FIXED → INVALID
You need to log in before you can comment on or make changes to this bug.