Have you made sure your environment points to the new Oracle libraries and not
old or nonexistent places? We just complete something similar
9i(Sparc)-ia64(11G) and lots of environment variables needed to be changed to
reference the correct location.
For instance :
my $dbcon= DBI-connect(dbi:mysql:dbname=dbcontactos,root,);
my $sql = $dbcon-prepare(select name,pass from Utilizador where
name='?' and pass='?');
$sql-execute($user,$pass);
if($sql == 1){
redirect to other page
}
if($sql == 0){
stay in the login page
}
Not quite sure what you
Look at http://www.stunnel.org/ . Set up an a forwarding stunnel on your
machine to connect to a listening stunnel on the remote machine.
All ports work basically the same way so consult the examples section on
the site for details. The basic mechanism works as follows (both client
and server
compiling/installing DBI.
-M
-Original Message-
From: Sanjay Tripathi [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 28, 2007 10:17 AM
To: Matthew Ramadanovic; Satya Shiv Mohanty
Cc: dbi-users@perl.org
Subject: RE: Perl DBI Urgent
Matt,
As your suggestion, I did like that
[EMAIL
Why not just do something like this:
#!/usr/bin/perl
eval {
use DBI;
};
if ($@) {
print Couldn't use DBI : [EMAIL PROTECTED];
} else {
print Loaded DBI successfully\n;
}
eval {
use DBD::Oracle;
};
if ($@) {
print Couldn't use DBD::ORACLE : [EMAIL PROTECTED];
} else {
print Loaded DBD::Oracle
Folks,
Some of these posts remind me that a few weeks ago I came across
a Solaris 8 server that had functioning sqlplus access to a separate
oracle server and perl 5.8.7.
The vendor was trying to load a compiled version of DBI from their
installation media. Their install would claim
I had this problem on Solaris 8 and the solution was to make sure your
LD_LIBRARY_PATH environmental variable included the path for the 32 bit
drivers (which at least for that version it doesn't by default). I
mailed myself a snippet back then after resolving the issue (below). I
think this one
I don't know about 10 but on 9.2.0.4 you need to make sure to set up
your environment correctly. I usually have to set all of the following
variables with values like so :
LD_LIBRARY_PATH=/export/home/oracle/product/9.2.0/lib:/export/home/oracl
I can understand frustration but your request is too nebulous for those who
do have the skills to help you troubleshoot. I connect to Oracle from many
different Windows installs daily and have never seen the problems you have
described without other identifiable machine configuration issues (as in
Have you tried only using the / character or even not using them at all?
C:\PPM i c:/temp/DBD_Oracle-1-872-1136408691
Or
Cd c:\ppm
Ppm i DBD_Oracle-1-872-1136408691
Works fine on XP SP2.
-M
-Original Message-
From: Christopher T. Brown [mailto:[EMAIL PROTECTED]
Sent: Tuesday,
Can you log in via sqlplus from the \OCI directory? Also did you make sure
you set the proper environmental variables in your environment? On XP you
need (at least)
NLS_LANG=american_america.we8iso8859p1 (or you may have funky script issues)
ORACLE_HOME=c:\orahome1 (or whatever yours is)
My guess is that you probably need to set some environmental variables. I
was running into this problem with a stored proc and got around it by having
my perl script call another after setting the variables :
$ENV{ORACLE_HOME} = '/export/home/oracle/9.x'; #or whatever
$ENV{ORACLE_SID} =
The problem here is whose system variables? (IE the system the database
is designed on or where it will eventually live or where it will live
once its original host dies etc. .). Since you can't always control all
of these variables I have found that when I HAVE to use access that
things are
I'll bet at least one person on this group has a copy of this book :-)
When I was REALLY unfamiliar with DBI I found the FAQ, usenet, and this
group to be the most useful (in that order).
Tim's book initially seemed to me was like an explanation about how the
rocketship was built rather than
14 matches
Mail list logo
