Sorry, but there is no way. / as sysdba is a SQL*Plus specific command. I opened a tar with oracle on the issue of being able to connect / as sysdba and using OCI to shutdown the database like the shutdown command in SQL*Plus. They told me that neither could be done. I created a user with very specific privileges and set very restrictive permissions on my script that contains that information. I also created packages to do specific things and granted execute on those packages to that user. That is the best solution that I have been able to come up with. I hope that helps.
Thanks Sam Gold -----Original Message----- From: Christian Merz [mailto:[EMAIL PROTECTED] Sent: Thursday, June 05, 2003 5:31 AM To: [EMAIL PROTECTED] Subject: Oracle connect internal/OS authentification Hello all, this topic has been discussed several times, i know. But i have not seen a solution by now. On UNIX i can open an Oracle DB "connect internal" connection by $ sqlplus "/ as sysdba" when i am in OS group 'dba' - there is no need to specify a password. Whichever type of connection i use with DBI i HAVE TO specify a password. But i certainly do not want to code my sys/system passwords in my skripts. Any short slution on this? Do i have to set up a password manager (host/instance/user/password) ? -> Which i would do only as an emergency solution. Thanx, Christian --------------------------------------------------------- What difference does it make to the dead, the orphans, and the homeless, whether the mad destruction is brought under the name of totalitarianism or the holy name of liberty and democracy? - Gandhi
