This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Connect to Oracle as SYSDBA using ADO
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Oct 31, 2011
11:56 AM
Connect to Oracle as SYSDBA using ADO
I'm trying to connect to Oracle as the SYS user using ADO in an InstallScript function, but I keep getting an error saying I need to connect as sysdba.
I've followed the steps in this post but to no avail.
My connection string is Provider=OraOLEDB.Oracle;Data Source=MyDatabase;User ID=SYS;Password=password;
In the ISSQLDBMetaData table in Direct Editor, I've changed the following columns to these values:
AdoDriverName: {Oracle in client11_home1}
AdoCxnServer: DBQ=
ISAttributes: 6
AdoCxnAdditional: DBA Privilege=SYSDBA
When I connect as SYSTEM, without as sysdba, things work fine. But when I try as SYS, it fails to connect. If I add AS SYSDBA to the password field in my connection string, I get an invalid password error.
I'm not sure what I'm doing wrong. Help please.
I've followed the steps in this post but to no avail.
My connection string is Provider=OraOLEDB.Oracle;Data Source=MyDatabase;User ID=SYS;Password=password;
In the ISSQLDBMetaData table in Direct Editor, I've changed the following columns to these values:
AdoDriverName: {Oracle in client11_home1}
AdoCxnServer: DBQ=
ISAttributes: 6
AdoCxnAdditional: DBA Privilege=SYSDBA
When I connect as SYSTEM, without as sysdba, things work fine. But when I try as SYS, it fails to connect. If I add AS SYSDBA to the password field in my connection string, I get an invalid password error.
I'm not sure what I'm doing wrong. Help please.
1 Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Oct 31, 2011
05:07 PM
Apparently, the problem was in the connection string. OLEDB does not support connecting as SYSDBA, so I changed "Provider=OraOLEDB.Oracle" to "Driver={Oracle in client11_home1}" and "Data Source" to "DBQ", and I could then connect as SYSDBA.
