Home » RDBMS Server » Security » / as sysdba
/ as sysdba [message #123442] Mon, 13 June 2005 08:54 Go to next message
balavignesh
Messages: 180
Registered: March 2005
Senior Member
hai,

in our oracle 9i server on linux the oracle gets started when os restarted.but now it is not getting up as the "/ as sysdba" is not accessible since it blows insufficient privileges.

we know the passwd of sys user and connect as sysdba but we are in need of / passwd as that passwd is used to get the db up at the time of restart using dbstart shell script in linux.that / passwd is not getting right and hence the problem.now , how to revert the passwd back or else what is the solution..? plz help.

regards
bala
Re: / as sysdba [message #123443 is a reply to message #123442] Mon, 13 June 2005 09:00 Go to previous messageGo to next message
Mahesh Rajendran
Messages: 10694
Registered: March 2002
Location: oracleDocoVille
Senior Member
Account Moderator
My understanding about your problem is,
your dbstart / dbshut in linux is not working.
Am i right?
If so,
1. When you reset sys password, did you also reset the
passwordfile?. Always do a clean shutdown. Reset the
passwordfile using orapwd. Startup.
2. Are you using any advanced security options / sqlnet encryption.
( The specific entries in sqlnet.ora will NOT let the dbstart to connect / as sysdba.) Same applies with srvctl in RAC environment.
3. Make sure the user issuing this has proper rights and
environment. Use `oracle` OS user to do this ( preferably). and
all the users issuing dbstart/dbshut should be included in dba
group.




Re: / as sysdba [message #123462 is a reply to message #123443] Mon, 13 June 2005 10:45 Go to previous messageGo to next message
balavignesh
Messages: 180
Registered: March 2005
Senior Member
hai ,

i have reset the passwd using orapwd as

orapwd file=name password=newpassword

shutdown and restart , now sys is getting up as earlier but still /as sysdba is not getting up.what to do..?

bala
Re: / as sysdba [message #123469 is a reply to message #123462] Mon, 13 June 2005 12:02 Go to previous messageGo to next message
Mahesh Rajendran
Messages: 10694
Registered: March 2002
Location: oracleDocoVille
Senior Member
Account Moderator
dbstart/dbshut read the oratab file
Did you make proper entries in oratab?
Re: / as sysdba [message #124001 is a reply to message #123469] Wed, 15 June 2005 16:41 Go to previous messageGo to next message
balavignesh
Messages: 180
Registered: March 2005
Senior Member
hai,

no proper entries are entered in oratab file..it is as like when it was ok.help out

bala
Re: / as sysdba [message #124002 is a reply to message #124001] Wed, 15 June 2005 16:43 Go to previous messageGo to next message
Mahesh Rajendran
Messages: 10694
Registered: March 2002
Location: oracleDocoVille
Senior Member
Account Moderator
without entries in oratab file how could the dbstart/dbshut work?.
dbstart will fail.
Re: / as sysdba [message #124006 is a reply to message #124002] Wed, 15 June 2005 16:52 Go to previous messageGo to next message
balavignesh
Messages: 180
Registered: March 2005
Senior Member

if so,
how to set those entries now..?

plz help

Re: / as sysdba [message #124009 is a reply to message #124006] Wed, 15 June 2005 17:02 Go to previous messageGo to next message
Mahesh Rajendran
Messages: 10694
Registered: March 2002
Location: oracleDocoVille
Senior Member
Account Moderator
following is a typical oratab file.
at the end entries are seperate by : 'colon'.
ORACLE_SID:ORACLE_HOME:Y/N

bash-2.03$ cat /var/opt/oracle/oratab
#

# This file is used by ORACLE utilities. It is created by root.sh
# and updated by the Database Configuration Assistant when creating
# a database.

# A colon, ':', is used as the field terminator. A new line terminates
# the entry. Lines beginning with a pound sign, '#', are comments.
#
# Entries are of the form:
# $ORACLE_SID:$ORACLE_HOME:<N|Y>:
#
# The first and second fields are the system identifier and home
# directory of the database respectively. The third filed indicates
# to the dbstart utility that the database should , "Y", or should not,
# "N", be brought up at system boot time.
#
# Multiple entries with the same $ORACLE_SID are not allowed.
mutation:/u01/app/oracle/product/9.2.0:Y
Re: / as sysdba [message #124134 is a reply to message #124009] Thu, 16 June 2005 10:05 Go to previous messageGo to next message
balavignesh
Messages: 180
Registered: March 2005
Senior Member
see, there is no such file or directory in our server

cat /var/opt/oracle/oratab

the oratab file is in /etc/oratab with

oracle_sid : /mnt/ora_system/oracle/9.2.0:Y

so what to do now...?plz help

bala
Re: / as sysdba [message #124139 is a reply to message #124134] Thu, 16 June 2005 10:14 Go to previous messageGo to next message
Mahesh Rajendran
Messages: 10694
Registered: March 2002
Location: oracleDocoVille
Senior Member
Account Moderator

the /var/opt/oracle/oratab location is mine.
Look for yours as referenced in your dbstart/dbshut.
>>oracle_sid : /mnt/ora_system/oracle/9.2.0:Y
replace oracle_sid with YOUR ORACLE_SID
then do dbstart/dbshut.

[Updated on: Thu, 16 June 2005 10:43]

Report message to a moderator

Re: / as sysdba [message #124153 is a reply to message #124139] Thu, 16 June 2005 10:49 Go to previous message
balavignesh
Messages: 180
Registered: March 2005
Senior Member
see ,

it is already set as
oracle_sid:$oracle_home:y

the scenario is dbstart/dbshut are working if we manually type dbstart/dbshut in the prompt.but after restarting the server, it is not picking up automatically by LINUX blowing insufficient privileges due to passwd change and it also set right.however connect / as sysdba is not getting up with the sysdba's old passwd which we set right using orapwd tool.so, if connect / as sysdba is set right ,then it will up automatically.plz help in this issue as we could not come everytime when the server is restarted to make the db up.

bala
Previous Topic: wrap multiple files in a single command
Next Topic: Finding database ....
Goto Forum:
  


Current Time: Sat Aug 15 10:05:36 CDT 2020