Skip to Content

AHA! Moments Series

Background:

In this series, I will discuss AHA! Moments I experienced while solving technical challenges. Each blog in this series will contain this section followed by Format of this blog and then finally details on AHA! Moment.

Format:

The format of this blog will be as follows:

AHA! Moment: This will explain the lesson learnt. I will try to keep this very short. This would be a “do’s/don’t’s” type of statement.

+Why: This section will give details why the moment was AHA! moment.</p><p>Example:+ I will give an example that helped me experience AHA! Moment.

AHA! Moment: +Why: </p><p>I tried installing second instance in Unix Server. /sapmnt/<SID>/profile was NFS mounted from CI server. After entering /sapmnt/<SID>/profile for profile directory’s name while running SAPINST, I received this error:</p><p>!https://weblogs.sdn.sap.com/weblogs/images/251714417/sapinst_Error_message.png|height=408|alt=image|width=663|src=https://weblogs.sdn.sap.com/weblogs/images/251714417/sapinst_Error_message.png|border=0!</p><p> I reviewed DEFAULT profile and the parameter rdisp/msserv_internal was already active. Profile directory had appropriate permissions and ownerships. I reviewed sapinst.log and ran truss command to see which file SAPINST was trying to read. truss output showed that it was trying to read /usr/sap/<SID>/SYS/profile/DEFAULT.PFL and not /sapmnt/<SID>/profile/DEFAULT.PFL. Because SAPINST couldn’t read DEFAULT.PFL, it assumed the parameter was not set.</p><p>Example: +

1) Dialog instance with system number 00 is already running for SID QS1

2) I tried to install second instance with system # 01 for SID BWQ

I started SAPINST. selected SAP Netweaver 2004s Support Release 2 -> Additional Life-Cycle Tasks –> Application Server –> Oracle –> Dialog Instance. In the following screen, I selected Custom. I typed /sapmnt/BWQ/profile for Profile Directory’s name in next screen. I received the error mentioned in the screenshot above. truss command’s output showed error: No such file or directory as shown below:

!https://weblogs.sdn.sap.com/weblogs/images/251714417/TrussOutput.png|height=420|alt=image|width=642|src=https://weblogs.sdn.sap.com/weblogs/images/251714417/TrussOutput.png|border=0!</body>

3 Comments
You must be Logged on to comment or reply to a post.
  • Thank you very much for writing this error to your blog.
    I’ve been looking at service.sap and thousands of other places without solved.

    And finally, I have learned a golden rule in the sap of the facilities of problems, to see the sapisnt.log … 🙂
    Thank you very much again.

    Best regards from Madrid (Spain)

    • “But why would you want to uninstall SAP ?”

      I’ve found that DI (aka NWDI) instances and the instances connecting to them are particularly sensitive to problems with ‘reinstallation’.  I find virtualisation and backups are useful 🙂 It’s often easier (sometimes, anyway) to restore the disk image(s) to the state they were in immediately prior to your install, rather than try to uninstall.