on 09-06-2011 10:13 AM
Hi,
I just upgraded the SAP Kernel, and now I wanted to start sap with the new kernel.
I ran ./saproot SID, started saposcol (saposcol -l) and ran the sapstart. Unfortunately sap doesn't start and returns the error : no instance profile found.
I checked the default profile, everything sames to be clean.
Any idea
thanks in advanced
I had the same problem while installing the linux test drive. Solved by:
export SAPSYSTEMNAME=NPL
For some reason this evnironment variable was set to "npl" instead of "NPL".
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Many Thanks to all of you,
Problem was solved : the cause was a wrong start- and instance-profile name. I renamed the both profiles and started sap. It's working.
Regards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Victor,
1. Please, first make sure that the listner is running before starting sap, otherwise 'lsnrctl start' as db-owner-user.
2. startsap as sidadm.
3. if startsap doesn't work, then try
startsap pf=/sapmnt/SID/profile/SID_DVEBMGS00_hostname (00 is your Instancenr.)
4. if that doesn't help, try to edit startsap script under /sapmnt/SID/exe and replace 'VHOSTS=`hostname -s` with 'VHOSTS=your_server_hostname
Hope that it helps
Regards
According to step 3, I cannot find the /SID_DVEBMGS00_hostname
under /sapmnt/SID/profile/
And under this directory, I only see DEFAULT.PFL file.
and I also check it in the /usr/sap/slo/sys/profile, the result
is the same.
My netweaver version is 7.40.
This is the first time I install netweaver.
what is the problem with my installation? Do I miss some installing?
.
Hi
Neither under "/usr/sap/<SID>/DVEBMGS<##>/work" nor under under "/usr/sap/<SID>/DVEBMGS<##>/log" is a new entries relating to the last attempts.
The only actual log is the dev_coll log under /usr/sap/tmp
11:06:24 . WARNING: The saposcol process is not running with effective root
11:06:24 . WARNING: authority. Virtual Memeory parameter settings can not be captured.
11:06:24 . WARNING: Please change executable permissions if you wish to capture this information.
11:06:24 . WARNING: The partition does not have authority to observe shared pool utilization
11:06:24 . LOG: Initial trace level = 2
11:06:24 . LOG: Process Monitoring active.
11:06:24 . LOG: searching for Process Monitoring Templates in /usr/sap/tmp/dev_proc
11:06:24 . LOG: searching for Process Monitoring Templates in /usr/sap/tmp/procmon/
11:06:24 . LOG: INFO: /usr/sap/tmp/procmon does not exist or cannot be opened.
11:06:24 . LOG: INFO: Files for Process Monitoring in /usr/sap/tmp/procmon are ignored.
11:06:24 . LOG: INIT : Disk data collected for 27 disks (0 filtered)
11:06:24 . LOG: INIT : Network data collected for 3 interfaces
11:06:24 . LOG: INIT : Global CPU data collected.
11:06:24 . LOG: INIT : CPU data collected for 4 cpus
11:06:24 . LOG: INIT : File system data collected for 20 fs (0 filtered)
11:06:24 . LOG: INIT : Memory data collected.
11:06:24 . LOG: INIT : PARAM data collected for 1 parameters
11:06:24 . LOG: Shared Memory Size: 1870188.
11:06:24 . LOG: Shared Memory was created by process:14811218
11:06:24 . LOG: ==== Collector submitted. This is the parent process after fork.=====
11:06:27 . LOG: ==== Collector submitted. This is the child process after fork()=====
11:06:30 . LOG: Collector daemon started
11:06:30 . LOG: Don't use put-file (Taken on other system)
11:06:30 . LOG: Collector PID: 15335466
Thanks for your interest
regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi Orkun,
I started indeed sap by the user sidadm.
The last entries in the error logs show the stopsap before kernel upgrade.
I don't see any other logs for my last sapstart attempts.
Best regards
Latif
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
>
> I just upgraded the SAP Kernel, and now I wanted to start sap with the new kernel.
> I ran ./saproot SID, started saposcol (saposcol -l) and ran the sapstart. Unfortunately sap doesn't start and returns the error : no instance profile found.
> I checked the default profile, everything sames to be clean.
>
> Any idea
> thanks in advanced
Hi Abdellatif,
1) In order to be be safe side, do you starting the instance by sid<adm> user, correct?
2) Could you provide the full error log, here?
Best regards,
Orkun Gedik
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.