Please see below with more details; dbh declaration is of perl hash.
my %connection_hash = (); # keep open connections
$connection_hash{$dbname} = DBI->connect( $sid, $user, $pass,
{AutoCommit => $autocommit_flag}); for(keys %connection_hash){
lib_log::debug_msg("Connection hash of $_ is
These connection strings are not the same.
There really is not much to say about them without code samples that
include variable definitions.
On Wed, Oct 28, 2020 at 13:06 Srikantha wrote:
> Hello Fennel & David,
> Thanks a lot for your response. FInally I could sort out the segmentation
>
I forgot to mention, when I print what is there in the hash after
DBI->connect, I see an extra line(see o/p section) is coming up there.
*Regards*
*Srikantha*
*Mb-9980073640*
On Mon, Nov 2, 2020 at 6:49 PM Srikantha wrote:
> Basically below connection_hash is causing a core dump. Can you
Basically below connection_hash is causing a core dump. Can you please
guide me, how I can rewrite this? In the previous email, the Not working db
handle is using a hash method and which is what dumps core.
code:
my %connection_hash = (); # keep open connections
for(keys %connection_hash){
Hello Fennel & David,
Thanks a lot for your response. FInally I could sort out the segmentation
fault/Memory dump error after too many rounds of debugging.
Basically I can blame it on the Oracle connection but I may be wrong as
there are few minor changes(could be on connection_hash too) in the
I wonder what the difference between "$sid" and "dbi:$db_driver:$db" is. If
nothing, it would look like Oracle::DBD might have some kind of weakness
regarding multiple active connections, if the fault happens later instead
of right at connect time, like on the second time through, with a different
On Tuesday, October 27, 2020 1:18:29 PM EDT Bruce Johnson wrote:
> Or the client isn’t installed or the environment variables are not
> set properly, or, or...
>
> RHEL, Fedora and CentOS do NOT include DBD::Oracle in their
> pre-built perl modules. Like Gary I’ve always had to build it with
>
On Oct 26, 2020, at 7:31 PM, Garry T. Williams
mailto:gtwilli...@gmail.com>> wrote:
On Monday, October 26, 2020 11:47:54 AM EDT David Nicol wrote:
if the Oracle module is maintained by red hat, yum update should
help. If you built it in-house, you may need to yum update the perl
development
On Monday, October 26, 2020 11:47:54 AM EDT David Nicol wrote:
> if the Oracle module is maintained by red hat, yum update should
> help. If you built it in-house, you may need to yum update the perl
> development environment and reinstall.
This is good advice.
The original poster also should
I think the following links should cover all the pieces needed for
Perl/JDBC/Oracle
https://www.oracle.com/database/technologies/appdev/jdbc.html
https://metacpan.org/pod/distribution/DBD-JDBC/JDBC.pod
https://sdkman.io/
Perl can launch the java server using qx:
https://perlmaven.com/qx
This
Also consider switching to the JDBC module and using the Oracle JDBC driver.
The JDBC driver requires launching a Java server which perl accesses via
sockets which is available from CPAN but is not simply a drop in replacement
for other DBI / DBD modules.
I had to downgrade both perl and
if the Oracle module is maintained by red hat, yum update should help. If
you built it in-house, you may need to yum update the perl development
environment and reinstall.
On Fri, Oct 23, 2020 at 11:27 PM Srikantha wrote:
> Hello,
> We are having the below issue from one of the perl modules. We
Hello,
We are having the below issue from one of the perl modules. We are trying
to get Oracle query results via this perl package and that package is using
DBI.pm.
The perl script is executing end-end but at the end there is a segmentation
fault error. We have recently upgraded our RHEL version
13 matches
Mail list logo
