OpenDatabase for SYSDBA

Hi
I have problem with connecting to Oracle database AS SYSDBA from VB Component. I need to connect as SYS to mounted standby database... Here is part of my source code:
set mobjOraSession = CreateObject("OracleInProcServer.XOraSession")
Set mobjOraDatabase = mobjOraSession.OpenDatabase("orcl_dms", "sys/heslo", 0&)
I need somewhere write, that I want to connect as sysdba, but where???
Can anybody help me????
Thanks

Hi,
I just joined the forum and found that you already faced the same problem as me. I was wondering if you found any solution to the connecting as SYSDBA problem. I changed my driver from Microsoft ODBC driver to OO40 driver, but still could not connect as SYSDBA.
Krishna

Similar Messages

  • Oracle Auditing for SYSDBA

    I have auditing turned off in 10g R2 but it's still logging audit files when I log in as sysdba. Is there any way to turn that off?
    SQL> show parameter audit;
    NAME                                 TYPE        VALUE
    audit_file_dest                      string      /odb03d/logs/database/adump
    audit_sys_operations                 boolean     FALSE
    audit_syslog_level                   string
    audit_trail                          string      NONE

    Most database systems engage in this type of behavior for actions regarded as critical to maintaining security. Basically, the database designers are telling you that they want to know when SYSDBA logged in if they ever have to provide support, especially on security matters.

  • Requirement for SYSDBA login while deploying

    Why do I have to login as SYSDBA when we need to deploy a .NET stored procedure?
    Normally, I can create Packages, procedures and everything without a SYSDBA login within the schema I created.
    Does this mean every stored procedure developer in an organization have to have SYSDBA priviliges? This does not make any sense.
    We are trying to make the conversion from PL/SQL Developer to Visual Studio .NET to develop/manage PL/SQL code, but stuff like this makes us stop.

    The users are already different. The purpose of this whole thing is to prevent network admin. users to login to oracle database as sysdba.

  • Steps to find the password for users as sysdba

    What are the steps to find the password for users in dba_users as sysdba?
    It is in encrypted form ? How can I view it ?
    Pls tell in steps ?

    I asked for sysdba
    When he can change password why can't he view ?Can you see the users password on a windows domain? No
    Can you see the users password on a Unix box? No
    Can you see the users password on a mail server? No
    Why would it be different in Oracle?
    Why is hacking coming here ?Because it's something against the way the software works.
    This can, and is, dangerous to let the administrator (Oracle, MsSQL, Win*, Unix,...) know the users password for so many reasons. For example:
    . Privacy
    . Etiquette
    . Password reuse (password reused for Bank account, etc)
    . [insert a whole bunch of other good reasons I'm not going to bother writing]
    And anyway it is useless!
    Yoann.

  • Sysdba default passwd for 9i

    Hi,
    Kindly tell me the default password for sysdba and mdsys for oracle 9i.
    Regards,
    Anand

    sys/change_on_install as sysdba
    mdsys/mdsys (locked)
    Regards
    Laurent Schneider

  • Password for SYSTEM or SYS

    HI,
    I have installed Oracle 10g DB on XP. After installation of ORACLE DB, "DATABASE CONFIGURATION ASSISTANT" dialog box came, but i mistakenly click on OK button instead of clicking on PASSWORD MANAGEMENT to set the password for SYSTEM / SYS.
    Now when i am trying to login using user id and password, SYSTEM or SYS with password either by Oracle or CHANGE_ON_INSTAL then error is coming as :
    ERROR: ORA-01017: invalid username/password; logon denied
    DB installation was done on my laptop for testing / learning purpose only.
    Would you pls. help to login as SYSDBA / SYSOPER using SYSTEM or SYS ID.
    Thanks

    HI,
    On UNIX the Oracle executable has two group names compiled into it,one for SYSOPER and one for SYSDBA.
    These are known as the OSOPER and OSDBA groups.Typically these can be set when the Oracle software is installed.
    In this case when you issue the command 'CONNECT / AS SYSOPER' Oracle checks if your Unix logon is a member of the 'OSOPER' group and if so allows you to connect. Similarly to connect as SYSDBA your Unix logon should be a member of
    the Unix 'OSDBA' group.
    Please check whether the user belongs to OSOPER group.
    thanks,
    Krishna

  • Corporate Online Training For Oracle DBA @ Suninfosysinc Software Solutions

    SUN INFOSYS SOFTWARE SOLUTIONS
    Sun Infosys is a leading software solutions provider based out of Highland Park , New Jersey and serving clients across North America . Sun Infosys' dedicated information technology professionals are committed to meeting your company's information technology needs. Our allegiance to this goal and our high quality service guarantees our client's success.
    Sun Infosys empowers the exchange, execution and integration of software consultancy projects with a strong edge for human resource management. By building strategic alliances with world-class companies, Sun Infosys serves a plethora of multinational businesses.
    ORACLE 10g DBA COURSE CONTENTS
    ●     Introduction
    ●     Course Objectives
    ●     Suggested Schedule
    ●     Lesson Objectives
    ●     Oracle Products and Services
    ●     Oracle Database g: Stands for Grid
    ●     Oracle Database Architecture
    ●     Database Structures
    ●     Oracle Memory Structures
    ●     Process Structures
    ●     Oracle Instance Management
    ●     Server Process and Database Buffer Cache
    ●     Physical Database Structure
    ●     Tablespaces and Data Files
    ●     SYSTEM and SYSAUX Tablespaces
    ●     Segments, Extents, and Blocks
    ●     Logical and Physical Database Structures
    ●     Course Examples: The HR Schema
    ●     Database Architecture: Summary of Structural Components
    ●     Installing the Oracle Database Software
    ●     Tasks of an Oracle Database Administrator
    ●     Tools Used to Administer an Oracle Database
    ●     Installation: System Requirements
    ●     Checking the System Requirements
    ●     Optimal Flexible Architecture (OFA)
    ●     Using Optimal Flexible Architecture
    ●     Setting Environment Variables
    ●     Oracle Universal Installer (OUI)
    ●     Installing the Oracle Software
    ●     Database Configuration Options
    ●     Executing Configuration Scripts
    ●     Completing Your Installation
    ●     Advanced Installation Options
    ●     Installation Option: Silent Mode
    ●     Practice Overview: Installing the Oracle Software
    ●     Creating an Oracle Database
    ●     Planning the Database
    ●     Databases: Examples
    ●     Database Configuration Assistant (DBCA)
    ●     Using the DBCA to Create a Database
    ●     Password Management
    ●     Creating a Database Design Template
    ●     Using the DBCA to Delete a Database
    ●     Summary
    ●     Practice Overview: Using the DBCA
    ●     Managing the Oracle Instance
    ●     Management Framework
    ●     Starting and Stopping Database Control
    ●     Oracle Enterprise Manager
    ●     Accessing Oracle Enterprise Manager Database Home Page
    ●     Using SQL*Plus and iSQL*Plus to Access Your Database
    ●     Using iSQL*Plus
    ●     Setting Up iSQL*Plus for SYSDBA and SYSOPER Access
    ●     Using SQL*Plus
    ●     Calling SQL*Plus from a Shell Script
    ●     Calling a SQL Script from SQL*Plus
    ●     Initialization Parameter Files
    ●     Simplified Initialization Parameters
    ●     Database Startup and Shutdown
    ●     Starting Up an Oracle Database Instance
    ●     Starting Up an Oracle Database Instance: NOMOUNT
    ●     Starting Up an Oracle Database Instance: MOUNT
    ●     Starting Up an Oracle Database Instance: OPEN
    ●     Shutting Down an Oracle Database Instance
    ●     Shutdown Modes
    ●     SHUTDOWN Options
    ●     Using SQL*Plus to Start Up and Shut Down
    ●     Viewing the Alert Log
    ●     Viewing the Alert History
    ●     Dynamic Performance Views
    ●     Dynamic Performance Views: Usage Examples
    ●     Dynamic Performance Views: Considerations
    ●     Summary
    ●     Practice Overview: Managing the Oracle Instance
    ●     Managing Database Storage Structures
    ●     Storage Structures
    ●     How Table Data Is Stored
    ●     Anatomy of a Database Block
    ●     Tablespaces and Data Files
    ●     Oracle Managed Files (OMF)
    ●     Space Management in Tablespaces
    ●     Exploring the Storage Structure
    ●     Creating a New Tablespace
    ●     Storage for Locally Managed Tablespaces
    ●     Tablespaces in the Preconfigured Database
    ●     Altering a Tablespace
    ●     Actions with Tablespaces
    ●     Dropping Tablespaces
    ●     Viewing Tablespace Information
    ●     Gathering Storage Information
    ●     Viewing Tablespace Contents
    ●     Enlarging the Database
    ●     What Is Automatic Storage Management?
    ●     ASM: Key Features and Benefits
    ●     ASM: Concepts
    ●     Summary
    ●     Practice Overview: Managing Database Storage Structures
    ●     Administering User Security
    ●     Database User Accounts
    ●     Predefined Accounts: SYS and SYSTEM
    ●     Creating a User
    ●     Authenticating Users
    ●     Administrator Authentication
    ●     Unlocking a User Account and Resetting the Password
    ●     Privileges
    ●     System Privileges
    ●     Object Privileges
    ●     Revoking System Privileges with ADMIN OPTION
    ●     Revoking Object Privileges with GRANT OPTION
    ●     Benefits of Roles
    ●     Assigning Privileges to Roles and Roles to Users
    ●     Predefined Roles
    ●     Creating a Role
    ●     Secure Roles
    ●     Assigning Roles to Users
    ●     Profiles and Users
    ●     Implementing Password Security Features
    ●     Creating a Password Profile
    ●     Supplied Password Verification Function: VERIFY_FUNCTION
    ●     Viewing and Modifying Initialization Parameters
    ●     Managing Schema Objects
    ●     What Is a Schema?
    ●     Accessing Schema Objects
    ●     Naming Database Objects
    ●     Specifying Data Types in Tables
    ●     Creating and Modifying Tables
    ●     Understanding Data Integrity
    ●     Defining Constraints
    ●     Constraint Violations
    ●     Constraint States
    ●     Constraint Checking
    ●     Creating Constraints with SQL: Examples
    ●     Viewing the Columns in a Table
    ●     Viewing the Contents of a Table
    ●     Actions with Tables
    ●     Dropping a Table
    ●     Truncating a Table
    ●     Indexes
    ●     Types of Indexes
    ●     BTree Index
    ●     Bitmap Indexes
    ●     Index Options
    ●     Creating Indexes
    ●     What Is a View?
    ●     Creating Views
    ●     Sequences
    ●     Creating a Sequence
    ●     Using a Sequence
    ●     Temporary Tables
    ●     Temporary Tables: Considerations
    ●     Data Dictionary: Overview
    ●     Data Dictionary Views
    ●     Data Dictionary: Usage Examples
    ●     Summary
    ●     Practice Overview: Administering Schema Objects
    Managing Data and Concurrency
    ●     Performance Management
    ●     Performance Monitoring
    ●     Performance Monitoring: Top Sessions
    ●     Performance Monitoring: Top Services
    ●     SQL Tuning Advisor: Overview
    ●     SQL Tuning Advisor Options and Recommendations
    ●     Using the SQL Tuning Advisor
    ●     Using the SQL Tuning Advisor: Example
    ●     SQL Tuning Advisor: SQL Statistics
    ●     SQL Tuning Advisor: Identifying Duplicate SQL
    ●     Using the SQL Access Advisor
    ●     Managing Memory Components
    ●     Enabling Automatic Shared Memory Management (ASMM)
    ●     Manually Setting Shared Memory Management
    ●     Using the Memory Advisor
    ●     Dynamic Performance Statistics
    ●     Troubleshooting and Tuning Views
    ●     Invalid and Unusable Objects
    ●     Summary
    ●     Practice Overview: Monitoring and Improving Performance
    ●     Backup and Recovery Concepts
    ●     Part of Your Job
    ●     Categories of Failures
    ●     Statement Failure
    ●     User Process Failure
    ●     Network Failure
    ●     User Error
    ●     Instance Failure
    ●     Background Processes and Recovery: Checkpoint (CKPT)
    ●     Background Processes and Recovery: Redo Log Files and LogWriter
    ●     Background Processes and Recovery: Archiver (ARCn)
    ●     Instance Recovery
    ●     Phases of Instance Recovery
    ●     Tuning Instance Recovery
    ●     Using the MTTR Advisor
    ●     Media Failure
    ●     Configuring for Recoverability
    ●     Control Files
    ●     Redo Log Files
    ●     Multiplexing the Redo Log
    ●     Archive Log Files
    ●     Archive Log File: Naming and Destinations
    ●     ARCHIVELOG Mode
    ●     Summary
    Practice Overview: Configuring for Recoverability
    ○     Performing Database Backups
    ○     Backup Solutions: Overview
    ○     Oracle Secure Backup
    ○     User Managed Backup
    ○     Terminology
    ○     Recovery Manager (RMAN)
    ○     Configuring Backup Settings
    Sun Infosys Software Solutions Offering Courses:
         Oracle 10g / 11g DBA
         SQL , PL/SQL
         Linux Administration
         Oracle OCA DBA
         Unix/Linux + Shell Scripting
    Phone: +001-732-675-7911 (U.S.A)
    E-mail : [email protected]
    Website: www.suninfosysinc.com

    I'll remember that company name to ensure that I neither use it nor recommend it.
    John.

  • Why does more users can login as sysdba than specified in password file

    I have multiple databases using same password file which has five entries for sysdba, but i have more than five users who have sysdba right and all of them can simultaneously login as sysdba, can any one explain why

    How do your users connect ? You may have any number of users connected locally as sysdba. Local connections are authenticated by OS, no password file is used.
    Moreover, the five entries of password file have to be intended as DISTINCT users, but you may have a much higher number of connections.

  • How connect as SYSDBA after installation

    Hello,
    i have oracle 10g, windows xp both fresh installation.
    After i installed oracle i want use the iSQL*Plus DBA url and Enterprise Manager Database Control URL to connect as SYSDBA, my instllation was basic= i set pass for all sys user. Sysem user works fine but sysdba doesnt work: Your username and/or password are invalid.
    I am member of ora_dba group. If it is not possible connect as sysdba using iSQL*Plus DBA what is the best way connect as sysdba?
    Thnx.
    Message was edited by:
    user503518

    To set up iSQLPlus for SYSDBA capability, you want to read Chapter 2 & 3 of the SQLPlus Reference manual. It provides step by step instructions. http://www.oracle.com/pls/db102/portal.portal_db?selected=3
    Note - the SQLPlus manual, not the SQL manual

  • How can I find exact username if I connected with sysdba privilege?

    I granted sysdba privilge to a database user. I can connect that user as sysdba. From that users session, 'show user' command showing "SYS" and also username from v$session is also showing "SYS". How can I find actual username used for connecting the database as sysdba?
    Steve Abraham

    user10247588 wrote:
    Thanks for the replay..
    But my requirement is that in our production system auditors want to give separate username for each administrators (they are not recommending sys and system).
    Normal dba privilege is not a problem. But for sysdba privilege every users are showing the user "SYS". How we can I identify which user is login to the database for a particular work if they connected as sysdba. How can I find which user did that (not just want the username "SYS", because all the administrators are identified by sys if they are connected as sysdba). If auditing is enabled how can I find the exact username. Because we are planning to give sysdba privilege to some of the administrators.
    Also, is there any option to find the username, if one user is initiate shutdown of the database?First Please close the thread and keep questioning in only one thread.
    then do not connect as sysdba

  • Unable to connect 11g database as a sysdba using toad 10

    Please i need an urgent help.
    First i will let you know about my environment.
    OS : HP-UX 11.3
    Database : 11g R1
    Toad : 10.6
    I have set the password file with more than 1 entries for sysdba. The below message will shows the entries of user entry in password file.
    SQL> select username,sysdba from v$pwfile_users;
    USERNAME SYSDB
    SYS TRUE
    TPAUSER TRUE
    When i try to connect to the database 11g using the user as sysdba i am getting error ora- 01031 : Insufficient privileges.
    Please help me out.
    Thanks in advance

    / as sysdba means, omit username and passowrd and use OS authentication. For OS authentication to work, the account must be a member of the OSDBA group, which is DBA on a Unix server, or ORA_DBA under Windows. Remote SQL*Net logins cannot use OS authentication, but can use the password file.
    The password stored in your password file may not be the same used for the Oracle Admin account. Please see the following link how to setup the password file:
    http://download.oracle.com/docs/cd/B28359_01/server.111/b28310/dba007.htm

  • Setting password while connecting as sysdba

    dear DBA experts,
    how do we set password for sysdba while connecting to database.since we dont have password while connecting as sysdba.pls help me out...pls give me some steps ........
    thanks n regards
    aryan

    The password for the sys user is already set at the time of the database creation and is stored in the password file , available at the *$oracle_home/dbs* (on Linux) platforms. But this file is not used and is bypassed if the o/s user, mostly oracle , is a part of a group called dba group. So if you want the password file to be used, simplest would be to remove the user Oracle from the dba group.
    HTH
    Aman....

  • About connection using sysdba

    Hi all :-)
    I have a little question.
    I can make the connection through
    the command:
    conn / as sysdba
    For security, I would like that the user obligatorily put the password for sysdba to enter in the databse.
    For example:
    conn sys/pwd as sysdba
    How can I do this?
    Thank you!

    Because you're assigned to ORA_DBA group and that's why from your computer (as a computer of Oracle Administrator) you can enter to database whith no password. But from other computers you are entering to database as sysdba whith passwor. To change this password
    use orawpd utilite
    C:\> orapwd file=filename password=password
    filename is a password file, password is the password which you want to give it to sys user.

  • Oracle Sysdba logon and password

    Hi, all the Oracle specialists:
    I tried to logon on an Oracle server which we don't know the password for sysdba.
    Usually when I get on to the Oracle server, I can log on as sysdba using the following command:
    svrmgr>connect / as sysdba
    or
    svrmgr>connect internal
    both returns me "insufficient priviledges". If I am the system administrator for the server, I should be able to log on to Oracle with no problems, are I wrong?
    Any suggestions will be highly appreciated.
    Maggie

    make sure the O/S user that you are using is part of the dba group. I think this group is called ORA_DBA on windows.
    you can try: connect sys/change_on_install as sysdba
    this will work if the sys password has not been changed

  • After installing MAWI error ORA-01031 when trying to connect as sysdba

    I've installed mawi 2.18 on a brand new 10.2.0.5 ORACLE_HOME.
    After installing the patch i cannot connect anymore to the database as sysdba: the error i got is:
    ORA-01031: insufficient privileges
    If i unset TWO_TASK (as stated in mawi install procedure) and replace it by ORACLE_SID it works.
    What's the correct setup to handle both sysdba connection and MAWI setup ?
    thanks
    Chris

    You could create two seperate env files. The EOF.env for TWO_TASK access and then another env file of yoru choice for SYSDBA access replacing TWO_TASK with ORACLE_SID and depending on whether you are using sysdba access or regular MW access you would execute the correct env file. I would also place the SYSDBA env file in the actual ORACLE_HOME directory.

Maybe you are looking for