Error while installing SAP 4.6D on Solaries/Oracle 9.2-Segmentation Fault.

[Former Member]

Hi All,

We are installing SAP 4.6D on Solaries/Oracle 9.2 and getting below error.

Error Log:

WARNING 2011-02-08 13:05:26 OSUSERDBSID_IND_ORA SubstituteVariables:0

System is running Network Information Name Service (NIS) and thea

map 'passwd.byname' is shared. If any values must be changed an

error is reported and the administrator has to set the values

manually.

INFO 2011-02-08 13:05:26 OSUSERDBSID_IND_ORA SyOwnerAndGroupSet:200

Changing the group of file /oracle/PR1 to dba ...

INFO 2011-02-08 13:05:26 OSUSERDBSID_IND_ORA SyPermissionSet:100

Changing the permission of file /oracle/PR1 to 775 ...

It is also showing Segmentation Fault.

Please help on this.

Regards,

Venkata.

[Former Member]

Hi,

We had faced this issue a lot of times...when we did installation of 4.6D systems on Sorais 10 boxes.

We had also raised this issue with SAP but did not get final solution..however, everytime we restarted the installation after the error ...it used to past that stage in installation. At times, we had to completely delete all the files and start a fresh installation and thats how we finished that project... Looks like its a bug

Try restarting the installation or may be try a fresh installation....

Thanks,

Salman

[markus_doehr2]

>

> We had faced this issue a lot of times...when we did installation of 4.6D systems on Sorais 10 boxes.
> We had also raised this issue with SAP but did not get final solution..however, everytime we restarted the installation after the error ...it used to past that stage in installation. At times, we had to completely delete all the files and start a fresh installation and thats how we finished that project... Looks like its a bug 
> Thanks,
> Salman

If you try to install ancient/obsolete Software on a brand new operating systems there are always problems to be expected. Sun/Oracle guarantees on one side that older programs will run unchanged but there may still be small changes in the runtime (libc) that may affect those old programs. There are about 10 years of development between the program and the operating system, it's as if you were trying to install a 16bit Netscape on a Windows 7 PC - which may work technically.

You seem to use NIS, which is considered to be obsoleted anyway (by Sun/Oracle) and the implementation on Solaris 10 may differ from the Solaris versions that were officially released at the time of 46D and hence return codes may be to big and the programs segfault.

Markus

[markus_doehr2]

> We are installing SAP 4.6D on Solaries/Oracle 9.2 and getting below error.

Wow... installing 10+ year old Software can be a challenge...

What Solaris version are you running?

"Segementation fault" is an error in the R3SETUP program.

Markus

[Former Member]

Hi Markus,

We are trying to create a new SAP 4.6c system on Solaris 5.9 version SPARC 64 bit and Oracle 9.2.0.7 and later perform homogeneous system copy. As part of this, initially we are in process of creating the Central Instance where we are getting the Segmentation fault error.

INFO 2011-02-08 13:05:26 OSUSERDBSID_IND_ORA SyOwnerAndGroupSet:200

Changing the group of file /oracle/PR1 to dba ...

INFO 2011-02-08 13:05:26 OSUSERDBSID_IND_ORA SyPermissionSet:100

Changing the permission of file /oracle/PR1 to 775 ...

Segmentation fault

We are on SAP 4.6c with 4.6D Kernel. As we could not locate the 4.6D kernel in the SAP ServiceMarket place, we are

installing with 4.6D_EXT kernel (CD 4.6D EXT Kernel Oracle Tru64,LNX,SOL - CD no. 51020565).

To troubleshoot the issue we have done the following.

1. As per the installation document we have not set the env variable LD_LIBRARY PATH for root user. We have even tried the other way by setting the env variable.

2. Manually changed the permission /oracle/PR1 to dba and 775.

3. Reboot the server at OS level

4. Deleted the files in the installation directory and restarted it serveral times.

5. Reformated the filesystem.

But nothing seems to be working out, we still have the same error.

Regards,

Venkat

[markus_doehr2]

You may try to find out, where R3SETUP is coredumping:

# ulimit -c unlimited

Then start R3SETUP and run it until the program stops and coredumps. You can then evaluate the resulting core using

dbx core R3SETUP

(if you have the development tools installed)

or using

pstack core

This stack trace may give us (or SAP) an idea what may be wrong.

Markus

[Former Member]

Hi Markus,

We have set ulimit -c unlimited and later started R3SETUP. We got the segmentation fault error but we could not find any core file in the system. To check the core file we have used pstack core but does not return any value.

Regards,

Venkata

[volker_borowski2]

Hi,

did you prepare the system according to the OS-dependencies guide

with proper kernel parameters and codepages?

Volker