What causes these Oracle 11g errors :ORA-01034 &amp; ORA-27101?

If you're on M$Windows :
on a command prompt
ORADIM -EDIT -SID sid -STARTMODE auto -SRVCSTART system -SHUTMODE immediate
there are :
-STARTTYPE srvc,inst
and
-SHUTTYPE srvc,inst
too, but I can't test if they work on a EDIT command
try it

02.28.2008 at 05:57AM PST, ID: 21003663

I tried the following, but no success:

ORADIM -EDIT -SID xmlStore -STARTMODE auto -SRVCSTART system -SHUTMODE immediate

xmlStore is my SID.

02.28.2008 at 06:48AM PST, ID: 21004209

And with :
ORADIM -EDIT -SID xmlStore -STARTTYPE srvc,inst -SHUTTYPE srvc,inst
?

I haven't any Windows Oracle Server here to test, so I can't check if the spelling is correct.

02.28.2008 at 07:12AM PST, ID: 21004432

Rank: Genius

You do not mentioned the OS you use.
By a successful installation of Oracle there are two possibilities:
1. On Windows Oracle will start by rebooting
2. On Unix flavour OS it will not start by reboot. There is a way to force it to start
automatically, but it is a long way.

So you have to start the instance manually in the following way:

% lsnrctl start
% sqlplus /nolog
SQL>connect sys/manager@see_tnsnames.ora as sysdba
Connected
SQL>startup

02.28.2008 at 07:18AM PST, ID: 21004495

I'm using Windows Server 2003.

02.28.2008 at 07:34AM PST, ID: 21004694

The ORADIM -EDIT -SID xmlStore -STARTTYPE srvc,inst -SHUTTYPE srvc,inst solution didn't work either.

02.28.2008 at 07:47AM PST, ID: 21004849

In your ORACLE_HOME/database you should find a oradim.log file.
Open it, get the 10-15 last lines and past them
We may be able to check what's happening.

02.28.2008 at 10:11AM PST, ID: 21006448

SID for this example is PODS

----------------------------------------------------------------------------------------------------------------------
Wed Feb 27 08:59:09 2008
D:\PODSDB_BASE_LOCATION\product\11.1.0\PODS_HOME_LOCATION\bin\oradim.exe -startup -sid pods -usrpwd * -log oradim.log -nocheck 0
Wed Feb 27 08:59:13 2008
ORA-24327: need explicit attach before authenticating a user

Wed Feb 27 10:52:37 2008
D:\PODSDB_BASE_LOCATION\product\11.1.0\PODS_HOME_LOCATION\bin\oradim.exe -startup -sid pods -usrpwd * -log oradim.log -nocheck 0
Wed Feb 27 10:52:42 2008
ORA-24327: need explicit attach before authenticating a user

Wed Feb 27 11:42:08 2008
D:\PODSDB_BASE_LOCATION\product\11.1.0\PODS_HOME_LOCATION\bin\oradim.exe -shutdown -sid pods -usrpwd * -shutmode immediate -log oradim.log
Wed Feb 27 11:42:13 2008
ORA-24327: need explicit attach before authenticating a user

Wed Feb 27 13:03:18 2008
D:\PODSDB_BASE_LOCATION\product\11.1.0\PODS_HOME_LOCATION\bin\oradim.exe -startup -sid pods -usrpwd * -log oradim.log -nocheck 0
Wed Feb 27 13:03:26 2008
ORA-24327: need explicit attach before authenticating a user

Wed Feb 27 21:02:59 2008
D:\PODSDB_BASE_LOCATION\product\11.1.0\PODS_HOME_LOCATION\bin\oradim.exe -startup -sid pods -usrpwd * -log oradim.log -nocheck 0
Wed Feb 27 21:03:04 2008
ORA-24327: need explicit attach before authenticating a user

Thu Feb 28 08:48:32 2008
D:\PODSDB_BASE_LOCATION\product\11.1.0\PODS_HOME_LOCATION\bin\oradim.exe -startup -sid pods -usrpwd * -log oradim.log -nocheck 0
Thu Feb 28 08:48:36 2008
ORA-24327: need explicit attach before authenticating a user

Thu Feb 28 08:56:37 2008
D:\PODSDB_BASE_LOCATION\product\11.1.0\PODS_HOME_LOCATION\bin\oradim.exe -startup -sid pods -usrpwd * -log oradim.log -nocheck 0
Thu Feb 28 08:56:42 2008
ORA-24327: need explicit attach before authenticating a user

Thu Feb 28 09:21:30 2008
D:\PODSDB_BASE_LOCATION\product\11.1.0\PODS_HOME_LOCATION\bin\oradim.exe -startup -sid pods -usrpwd * -log oradim.log -nocheck 0
Thu Feb 28 09:21:36 2008
ORA-24327: need explicit attach before authenticating a user

Thu Feb 28 10:13:51 2008
D:\PODSDB_BASE_LOCATION\product\11.1.0\PODS_HOME_LOCATION\bin\oradim.exe -startup -sid pods -usrpwd * -log oradim.log -nocheck 0
Thu Feb 28 10:13:55 2008
ORA-24327: need explicit attach before authenticating a user

02.29.2008 at 12:00AM PST, ID: 21011673

Rank: Genius

Your instance should be OK.
I have installed 2 times Oracle 11g and for my big surprise
everything was perfect!!!

Please figure out the fiurewalls and antivruses on your compute.
Shut them down.

Investigate the NIC (network cards). Are they more then one? have they assigned STATIC IP addresses?
Oracle works only with static IPs. Did you point the right NIC if they are more then one?

02.29.2008 at 05:02AM PST, ID: 21012762

ORA-24327: need explicit attach before authenticating a user
is generally a message signifying that your installation hasn't been made with an administrator user.

Is it your case ?

02.29.2008 at 05:06AM PST, ID: 21012795

Yes, I installed it under an account that has admin access.

As for the NIC card, there is only one card with a static IP, but this machine is running on a VMware virtual machine. Will that affect anything?

Also, there is no firewall on the computer and I'm running Norton AV.

Thanks for all your help!

02.29.2008 at 05:07AM PST, ID: 21012800

By the way, plz give the content of the SQLNET.ORA file (in the same directory as the listner.ora and tnsnames.ora).

02.29.2008 at 05:10AM PST, ID: 21012827

Here you go:

# sqlnet.ora Network Configuration File: D:\PODSDB_BASE_LOCATION\product\11.1.0\PODS_HOME_LOCATION\network\admin\sqlnet.ora
# Generated by Oracle configuration tools.

# This file is actually generated by netca. But if customers choose to
# install "Software Only", this file wont exist and without the native
# authentication, they will not be able to connect to the database on NT.

SQLNET.AUTHENTICATION_SERVICES= (NTS)

NAMES.DIRECTORY_PATH= (TNSNAMES, EZCONNECT)

02.29.2008 at 06:57AM PST, ID: 21013731

Rank: Genius

Uncomment

# SQLNET.AUTHENTICATION_SERVICES= (NTS)

02.29.2008 at 06:58AM PST, ID: 21013748

Rank: Genius

----> I'm running Norton AV.

Please turn it off!

02.29.2008 at 07:00AM PST, ID: 21013755

Ok...will turn off AV.

Also, the SQLNET.ASQLNET.AUTHENTICATION_SERVICES= (NTS) is already uncommented. Did you want me to comment it?

Thanks!

02.29.2008 at 07:14AM PST, ID: 21013896

Rank: Genius

Sorry, comment it.
My mistake!

But if you really work with Oracle 11g I will reveal you the real cause what happens.
It is connected with a Listener Paragraph 22 situation.

I just climbed up from this trap! You are the first colleague I share how to rescue!

Congratulations!

Read this:

For STATIC registration of the Oracle service to the Listener:

Go to the remote 10g installation where the Oracle server resides.

Backup LISTENER.ORA file!!!!!!!

In ...\network\admin open listener.ora

see

SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = D:\Ora10g)
(PROGRAM = extproc)
)
(SID_DESC =
(SID_NAME = test)
(ORACLE_HOME = D:\Ora10g)
)
)

Add the entry
(SID_DESC =
(SID_NAME = test)
(ORACLE_HOME = D:\Ora10g)
)
with regard to the particular Oracle Home and SID Name.

In Oracle 11g you have to create from scratch in the listener.ora file the section

SID_LIST_LISTENER =
&..

mentioned above.

This is very important! Because if you shutdown some of your instances the dynamic registration of the instance in the Listener disappears and & when you try to connect again to this idle instance the listener politely informs you that it doesnt know about such service and you can not bounce the instance. Typical Paragraph 22 situation &..

Restart the listener:
c:>lsnrctl stop
c:>lsnctl start

Thats all.

Accepted Solution

02.29.2008 at 07:36AM PST, ID: 21014120

Thanks for the tip....just to make sure...are these the steps you want me to perform?

1. Comment the 'SQLNET.AUTHENTICATION_SERVICES= (NTS)' statement in the SQLNET.ORA file.
2. Backup the 'LISTENER.ORA' file
3. Open the 'LISTENER.ORA' file and add the following (I am running 11g, so this entry is not in the file and I must add it):
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = D:\Ora10g)
(PROGRAM = extproc)
)
(SID_DESC =
(SID_NAME = test)
(ORACLE_HOME = D:\Ora10g)
)
)

4. Stop the listener
5. Start the listener

02.29.2008 at 08:25AM PST, ID: 21014692

Except your Oracle_Home seems to be :
D:\PODSDB_BASE_LOCATION\product\11.1.0\PODS_HOME_LOCATION

(quite complicated by the way :-)

and your SID_NAME is POD (or XMLSTORE - I can't figure which)

02.29.2008 at 08:31AM PST, ID: 21014781

Rank: Genius

Yes!
I just faced this horable behaviour of 11g.
It dynamically registers und unregisters the service.
But when the services is not registered the DBA cannot
connect to the idle instance!!!!

02.29.2008 at 08:32AM PST, ID: 21014795

Why not use dynamic registration with local_listener parameter in your instances ?

02.29.2008 at 08:44AM PST, ID: 21014944