8i - service up, cannot start database, error 1031?

Oracle 8i on a machine that has recently changed domains.
Services start ok.  Database not started.
Using DBA Studio, I connect as a sysdba and try to open the instance (or start, mount, etc) using same config files as before.  This fails almost immediately.
In the system event viewer we get the following message (verbatim)...
Have tried this with several user accounts.  Get paired messages in the event log, one with the above message and status "SUCCEEDED ( 0 ) " and this one that fails, same timestamp.

We have inherited this database and the account info may be wrong.

As far as I know the only thing that has changed is that the OS domain has changed.  Operating System is Windows 2000 Server.

Any ideas anyone please, about where to look or what the cause may be?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.


Run up a commad window;
Run Server Manager by typing "svrmgrl"
Connect as SYS using "Connect SYS/<Password>@<Instance> As SysDBA
Try to startup the instance using "Startup PFile=<your parameter file including path>

If that does not work then please paste the command line errors into this thread.


keithfearnleyAuthor Commented:
OK,  thanks for the comment, but it wasn't greatly helpful - the message was ORA-01017, "insufficient priviliges", despite correct user/password.

I have found the problem (I think), and it could be of note for others...

The OS administrator account has also changed - name and password - and the new administrator was not in user group ORA_DBA.
I put the new admin user into this group and I was then able to log into oracle dba studio as a sys_dba and start the database successfully.
So, I was logged into the OS as the admin user, who was not in the ORA_DBA group, and was not able to log in as a SYS_DBA under oracle.  This seems strange to me, but there may be a link-up to do with services (which are running as local account rather than explicit admin account), OS user and oracle user.

Any ideas - this is a low priority now, since it is sorted.  
The Coriolis book "Oracle 8 and Windows NT Black Book" was helpful to me by giving a hint on setting up nt-authenticated users as oracle DBAs.
RindbaekSenior ConsultantCommented:
Well congratulations, you beat me on the ora_dba group issue... ,-)

Connecting as internal or sysdba/sysoper can be setup in 2 different ways:  
  - to connect without the necessity to provide a password  
  - to connect with the necessity to provide a password

 Os authentication for administrators  
Caution is the word as when you implement this, you're security is as good   as the operating system's security.

LOCAL User Groups need to be created on the Windows NT Server/Workstation.  T
his is best done through Start->Programs->Administrative Tools->User Manager/User Manager for Domains.  

For the use of User Manager/User Manager for Domains, please refer to the O/S related manual  

The 'OSDBA' and 'OSOPER' groups on NT are simply groups with the   name "ORA_DBA", "ORA_OPER", "ORA_sid_DBA" or "ORA_sid_OPER", where  'sid' is the instance name.

Verify that your MS Windows NT Local or Domain User Account that you use to  administer the Oracle Instance/Database belongs to one of the following four  
MS Windows NT Local Groups on the MS Windows NT Server/Workstation:  
Local Group              Explanation  
 -----------                -----------  
ORA_OPER              SYSOPER database privileges, for all instances  
ORA_DBA                SYSDBA  database privileges, for all instances  
ORA_<SID>_OPER   SYSOPER database privileges, for the specified instance only  
ORA_<SID>_DBA     SYSDBA  database privileges, for the specified instance only

Connecting With a Password    
When the "init.ora file" parameter remote_login_passwordfile is set to     EXCLUSIVE or SHARED, Oracle can have a password file to maintain      
  - the password of internal    
  - the list of users and their passwords that have been granted administrator privileges    

The name of the password file has the format: "pwd<SID>.ora" and is situated by default in the <ORACLE_HOME>\Database-directory.    
The password is automatically created in the <ORACLE_HOME>\Database directory when an instance is created with the instance manager ORADIMxx.

Regarding the servirce oracleservice<sid>
If your service wont start check that the account used for starting it is a member of the ORA_DBA, sometimes there is a problem with "LocalSystem" since you cannot put it into the ORA_DBA group, but its just sometimes....

Does it answer your questions?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Oracle Database

From novice to tech pro — start learning today.