cancel
Showing results for 
Search instead for 
Did you mean: 

START SAP

START SAP

HI,
I recover whole offline backup dbs and through sql prompt i open the db.initally there are some problems with control files but now my db is OPEN.
now by sidadm user i try to start the SAP by using command --startsap. but it returns error(Log file STARTDB.LOG) is attach.
to solve the error i did
--R3trans -d
which create another log file named trans

--even after DB can Open and file permissions are right i unable to start sap

-- sap ecc 5.0, oracle 9.2,HPUX os, is in use
-- any info requires then provide
plz help me in start sap

thanks ...!
15 REPLIES

Re: START SAP

Hi
trans log file is attach here




Thanks...!
Jean-Luc Oudart
Honored Contributor

Re: START SAP

can you post the alert log file (or extarct for today) to check any oracle error.

your log suggests there is an issue starting oracle.
#
Regards
Jean-Luc
fiat lux
Volker Borowski
Honored Contributor

Re: START SAP

Hi,

this message
DlLoadLib: dlopen()= Unable to find library 'libclntsh.so.9.0

Looks like some of your filesystem stuff
may not fully been recoverd from your crash.

Please check
- environment for user gmdadm, so in case the HOME of gmdadm was lost in your crash, you might need to re-adjust the environment.

- binaries of SAP Kernel
-> /sapmnt/GMD/exe...
should be present, if faulty, download corresponding kernel archives for your platform from SAPNET and extract freshly.

- Oracle client SW in /oracle/client/92x_64
if not present -> download from SAPNET.
Watch it when extracting, needs to be done in correct location. There is a special sapnote for installing the 9.2 client SW.



So far it looks like R3trans can not resolve some shared libs. Either they are not there or the library path does not resolve them due to faulty environment.

Interesting output would be (done as gmdadm)

ls -l /oracle/client/92x_64
env


Volker

Re: START SAP

hi sir

here is attachment of my alert_sid.log file
and trans.log file after changing some env path


plz go through it and reply as early as possible


thanks...!


Re: START SAP

hi

this is trans log file after some changes in env file



pankaj
Volker Borowski
Honored Contributor

Re: START SAP

ok,

and what changes did you do ?????

It still complains about not finding the
client shared libraray.
So you need to work on that.
Is the lib in place in the .../92x_64 dir?
Is the libpath pointing to that directory.
Did you check put the note for the client sw
(think it was #539922 )

Volker

Re: START SAP

hi
this is my env through oracle user(ORAGMD)


plz check it


pankaj

Re: START SAP

Hi this is my env through ADM user
(GMDADM)


pankaj

Re: START SAP

hi

this is env through root user

in this env i try to change
LD_libray_path=
LD_LIBRARY_PATH=/oracle/GMD/920_64/lib64:/usr/lib:/oracle/GMD/920_64/rdbms/lib:/oracle/GMD/920_64/network/lib

to
LD_LIBRARY_PATH=/oracle/GMD/920_64/lib:/usr/lib:/oracle/GMD/920_64/rdbms/lib:/oracle/GMD/920_64/network/lib

but it restore the original one
and error message is same
all the location are at the same place as mention..

pankaj

Re: START SAP

hi
this is my startdb.log
/home/gmdadm/startdb.log


pankaj

Re: START SAP

hi after doing R3trans -d
the new log file generated named trans.log
which is attach ...


pankaj
Volker Borowski
Honored Contributor

Re: START SAP

Hi,

the trans.log is not complaining about missing libs anymore. What did you do to fix it?

Environment for gmdadm and oragmd looks OK to me.

Environment for root is not relvant, because
you should not do anything with root which is realated to SAP.
Your root-Environment has a bug concerning
the SHLIB_PATH/LD_LIBRARAY_PATH and ORA_NLS33 setting, but again, it is not relevant, as you should not do anything with this.

So you did

su - oragmd
lsnrctl start
exit
su - gmdadm
R3trans -d

???

This seems weird to me. It should work.
What about your ORACLE_HOME location. Has it been affected by your previous disk corruption, or can you safely assume it is OK?

Does it work to do as gmdadm

sqlplus /
select * from SAPUSER
exit

If this does not work, does

sqlplus sapr3/sap
exit

work out ok as gmdadm.

If either of the two work, I am lost.
I'd start refreshing R3trans then.

Volker

Re: START SAP

Hi volkar..!
yes ORACLE_HOME=oracle/GMD/920_64
its ok....!

and yes i did
su oragmd
lsnrctl start

su gmdadm
(initially i did STARTSAP but it displayed too many messages related to db an R3trans )
so i did
R3trans -d
(it also gives error message which log file is already attach)one important thing that after performing this command or startsap,it at the same time if db stared then it shut automatically and gives error message

--ORA-01034: ORACLE not available
ORA-27121: unable to determine size of shared memory segment
HPUX-ia64 Error: 13: Permission denied

then i restared the SERVER
and start db again through sql (oragmd)
--DB open fine

now i did another option ie
R3trans -x
it display another set of error message which are attach here.

now as u told i login with gmdadm and sqlprompt and did
sql>startup
then it displyed same error
ORA 27121
and HP ux permission denied

BUT with Oragmd user
the db is already started and work fine.
ie su oragmd
sql>startup
alreday stared ....
sql>archive log list
it disply all details properly

so now with gmdadm db is not stared but oragmd it was alreday stared and work fine...

so wht to do now sir...??

plz reply sir.

Thanks

Jean-Luc Oudart
Honored Contributor

Re: START SAP

Hi

there is an issue using your listener. It's either down or your configuration (SAP) does not match the listener config.

When you access oracle directly it woks. You should try over SQLnet (eg sqlplus /@) to narrow down the pb.
>>> ETW000 [dblink ,00428] ***LOG BY0=>ORA-12541: TNS:no listener

Regards
Jean-Luc
fiat lux

Re: START SAP

HI....

I Got the solution.....

there is absence of tnsnames.ora and sqlnet.ora which are used for a connet are always loacted on the host on which the link of a client(such as R3) is requested. i refer
--sap note 491174
--sap note 445038
--sap note 395514
--sap note 583861
also change the permission and ownship of /$ORACLE_HOME/bin which is
--chmod 6751 oracle
--chown ora(sid) oracle
--chgrp dba oracle

the critical problem is solved...now


thanks to everyone

-- special thanks to volker..

thanks again


Pankaj..!