$dsn = "dbi:Oracle:ABCD12";
[download]

NAMES.DEFAULT_DOMAIN = COMPANYDOMAIN.COM
[download]

With

$dsn = "dbi:Oracle:DS8CC2";
[download]

or

$dsn = "dbi:Oracle:DS8CC2.ORACLEOUTSOURCING.COM";
[download]

the error becomes

DBI connect('DS8CC2','',...) failed: ORA-01031: insufficient privilege
+s (DBD ERROR: OCISessionBegin)
[download]

and

DBI connect('DS8CC2.ORACLEOUTSOURCING.COM','',...) failed: ORA-01031: 
+insufficient privileges (DBD ERROR: OCISessionBegin)
[download]

respectively.

But as I mentioned, there's no issue while connecting directly using sqlplus '/as sysdba' and $TNS_ADMIN/sqlnet.ora does have the entry:

NAMES.DEFAULT_DOMAIN = ORACLEOUTSOURCING.COM
[download]

Your original post gave error 12545 which is often related to naming. Now you are getting permission errors. So getting closer since you are now reaching the database.

Oracle docs indicate that error 1031 "insufficient privileges" is when you try to change username or password without appropriate privilege. As other have mentioned check you are in the correct groups to use the sysdba permission and that the user also is granted that in Oracle.

1. it's a real PITA to set up
2. it's quite touchy about releases.

It's Oracle 10g running on Enterprise Linux AS4. I am running the script on the DB node itself.

my $dbh = DBI->connect($dsn, "", "", { ora_session_mode => ORA_SYSDBA 
+});
[download]

my $dbh = DBI->connect($dsn, "system", $sysdba_password, { ora_session
+_mode => ORA_SYSDBA });
[download]

According to the DBD::Oracle documentation the username and password are supposed to be blank.

Also the username and password should be empty, and the user executing the script needs to be part of the dba group or osdba group.

Which according to me seems correct as while connecting sqlplus '/as sysdba' we do not provide any username/password.

OK, timtowtdi I guess :-)

$ sqlplus

SQL*Plus: Release 9.2.0.6.0 - Production on Wed Aug 5 13:29:01 2009

Copyright (c) 1982, 2002, Oracle Corporation.  All rights reserved.

Enter user-name: system as sysdba
Enter password: 

Connected to:
Oracle9i Enterprise Edition Release 9.2.0.6.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.6.0 - Production

SQL>
[download]

-- Time flies when you don't know what you're doing

my $database = 'TEST_DB';
my $DSN = "dbi:Oracle:$database";
my $dbh = DBI->connect( $DSN,
                          $DBUSER,
                          $DBPASS,
                          {AutoCommit => 1, RaiseError => 1}) or die "
+Can't connect DB [$!]";
[download]

.../oracle/product/10.2.0/client_1/network/admin/tnsnames.ora

TEST_DB =
  (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(Host = 192.168.1.1)(Port = 1526))
    (CONNECT_DATA =
      (SID = TESTDB)
    )
  )
[download]

DBI connect('TEST_DB','user',...) failed: ORA-01031: insufficient priv
+ileges (DBD ERROR: OCISessionBegin)
[download]

Is the user running the script a member of the dba, osdba or ORA_DBA group (depending on OS and configuration)?

#!/usr/bin/perl

use strict;
use warnings;
use DBI;
use DBD::Oracle qw(:ora_session_modes);

my $dbhost = "my.server.name";
my $dbuser = "sys"; # not "system" or "/"
my $dbpass = "password";

my $sid = "SIDNAME";

my $dbh = DBI->connect(
  "dbi:Oracle:host=$dbhost;sid=$sid", 
  $dbuser, 
  $dbpass, 
  { ora_session_mode => ORA_SYSDBA }
);

if ($dbh) {
  print "Connected\n";
} else {
  die $DBI::errstr;
}

$dbh->disconnect;
[download]

Update: No TNS file, no ORACLE_SID environment variable.

Hi,

Your solution work because technically you are supplying the username and password which simulates connecting from the network to the database

I believe the issue here is if you are going to use the script to run locally on the server, there should not be a need to supply username and password because you are already on the server itself. The main idea for this is to not having to specify passwords on your scripts for security reason.

I know that this is an old thread, but I was having the same problem and Google popped it to the top of the list when I searched for 'perl oracle connect as sysdba'. Just in case anyone else starts looking for an answer to this, the solution is to use a dsn of 'dbi:Oracle:' and undef for the username and password. Provided that you are running as oracle (or are a member of the dba group) on the host where the database is running and you have the ORACLE_SID variable set properly and you use the ora_session_mode => ORA_SYSDBA pair in the connection hash you will connect OK. At least that worked for me.