SAPOSCOL -- Not implemented for INTERN

[Former Member]

Dear All,

Our production server has 2 application server. In 0S07, when I click the button of Status and Log File of the SAPOSCOL, it return the error message :

Not implemented for INTERN

Internal error. Cannot open: /dev_coll

It happens on the db server and the second application server, but the first seems okay.

I could open the dev_coll using (sid)adm through console,

the content:

14:51:10 11.02.2009 LOG: Profile : no profile used

14:51:10 11.02.2009 LOG: Saposcol Version : [COLL 20.95 700 - AIX v11.15 5L-6

4 bit 080317]

14:51:10 11.02.2009 LOG: Working directory : /usr/sap/tmp

14:51:10 11.02.2009 WARNING: : Kernel parameter iostat is FALSE.

14:51:10 11.02.2009 WARNING: : For accurate disk statistics, ensure that

kernel is

14:51:10 11.02.2009 WARNING: : set to continuously maintain DISK I/O h

istory, e.g.,

14:51:10 11.02.2009 WARNING: : # chdev -l sys0 -a iostat='true'.

14:51:10 11.02.2009 WARNING: : The saposcol process is not running with

effective root

14:51:10 11.02.2009 WARNING: : authority. Virtual Memeory parameter se

ttings can not be captured.

14:51:10 11.02.2009 WARNING: : Please change executable permissions if

you wish to capture this information.

*

*

*

The same content for the db server that's not working and the first application server that's working.

I've tried to restart the saposcol (through console, while I tried using os07, error "Not implemented for INTERN"), but the problem was not solve.

Thank you very much for every help.

[former_member603052]

Hey

The service SAPOSCOl should be running with username ROOT in all servers.Only ROOT can collect total information of system.

Regards,

Kalyan

[former_member194078]

Hi,

For self execution of saposcol by the time of starting sap instance owner should be root:sapsys with permission of 4710.

Regards,

Himanshu.

[Former Member]

Try running saproot.sh to fix the permission for SAPOSCOL. SAPOSCOL needs permission 4775.

Go to Kernel Directory ( /usr/sap/<SID>/SYS/exe/run )

[root ]# ./saproot.sh

Regards,

Jazz

[Former Member]

Hello,

Please check and correct the permissions on saposcol executable.

BTW, you can do this by > saproot.sh script.

Hope this helps.

Manoj Chintawar

Edited by: Manoj Chintawar on Feb 11, 2009 9:13 AM

[Former Member]

Dear All,

Thanks for the input.

I've set the correct permission for saposcol, now the second app server works normal.

But, it doesn't solve the problem of db server.

I've restarted saposcol for few times.

Also, the data provided by saposcol on db server generated using OS07, ex. filesystems, disks, un-characterized. I mean, filesystem data provided non-alphabetical. So I can't understand what the filesystem stand for. (Non-alphabetical just like multiple boxes).

But it's okay for numbers.

Please help.

[Former Member]

Hai,

You can try to stop the OSCOL and then clear the shared memory, then try starting it.

If this does not help, try applying the new OSCOL, check SAP Note: 19227.

To clear the shared memory, login as sidadm in os level, goto 'exe' directory then execute 'saposcol -d' this will take you into saposcol dialog mode. Then type help and enter, here you will get the options to clear the shared memory.

Regards,

Yoganand.V

[Former Member]

Hello,

I've clean the share memory, and upgrade the saposcol to the newest one, but the problem hasn't solved yet..

Best regards,

May