Export for system copy fails - Error 9 (Bad file number)

Question

Hello all,
I am attempting to perform the export phase for a hetergenous system copy on our BI system (BI 7.0 - NW2004s).  This system runs on HP-UX 11.11 using Oracle  10.2.0.2 and will be migrated to Windows Server 2003 and MS SQL Server 2005, once the export is complete.
While running sapinst to export the data from the source system, there are several input dialog screens that are skipped, which means I am not able to enter all the paramters used for the export.  After seeing this behavior from sapinst, I reviewed the sapinst.log and sapinst_dev.log files and find the warning/error "System call failed. Error 9 (Bad file number)".  I have included a portion of these files below.
I have reviewed notes 546006 and 583861, but these seem to refer to an Oracle error ORA-27121, but I am not receiving any Oracle errors in sapinst.log or the Oracle alert log.  I have looked for possible permission or ownership problems with any of the SAP or Oracle files, but have not found any that were incorrect.  Also, these errors do not specify which file sapinst is having problems with, so I do not have  a specific file or area to check.
If anyone has seen something similar to this and has any suggestions, I would greatly appreciate any help.
sapinst.log details:
INFO 2009-02-14 15:15:51.67
Execute step collect of component |NW_Export|ind|ind|ind|ind|0|0|NW_GetSidFromProfiles|ind|ind|ind|ind|1|0|NW_readProfileDir|ind|ind
|ind|ind|0|0
INFO 2009-02-14 15:15:52.737
Account bwpadm already exists.
WARNING 2009-02-14 15:15:52.747
System call failed. Error 9 (Bad file number) in execution of system call 'getgrent' with parameter (), line (292) in file (syuxcuse
r.cpp).
INFO 2009-02-14 15:15:52.757
Account 0 already exists.
WARNING 2009-02-14 15:15:52.777
System call failed. Error 9 (Bad file number) in execution of system call 'getgrent' with parameter (), line (292) in file (syuxcuse
r.cpp).
INFO 2009-02-14 15:15:52.777
Account 200 already exists.
WARNING 2009-02-14 15:15:52.827
System call failed. Error 9 (Bad file number) in execution of system call 'getgrent' with parameter (), line (292) in file (syuxcuse
r.cpp).
INFO 2009-02-14 15:16:04.937
Creating file /tmp/sapinst_instdir/NW04S/LM/COPY/ORA/EXP/CENTRAL/AS/EXP/ypcat.log.
INFO 2009-02-14 15:16:05.007
Output of ypcat passwd.byname is written to the logfile ypcat.log.
sapinst_dev.log details:
TRACE      2009-02-14 15:15:52.737
2009-02-14 15:15:52.743 NW._getSAPMount() done: /sapmnt
INFO       2009-02-14 15:15:52.737 [syuxcaccmg.cpp:227]
           bool CSyAccountMgtImpl::isExisting(ISyAccountMgt::eAccountType accountType, iastring sName)
Account bwpadm already exists.
TRACE      2009-02-14 15:15:52.747 [syuxcuser.cpp:1943]
           CSyUserImpl_getOsInfos(ILogBook *m_logBook, iastring sName, iastring sID, tSyUserInfo& msUserinfo)
getspnam(bwpadm) returned NULL.
WARNING    2009-02-14 15:15:52.747 [syxxsyshlp.cpp:78]
           syslib::printOSError(const iastring &, int, DWORD, const iastring &, CMessage::eLogMessage)
System call failed. Error 9 (Bad file number) in execution of system call 'getgrent' with parameter (), line (292) in file (syuxcuse
r.cpp).
Regards,
Rusty Robbins

Answer 1

Hello Peter,
Thanks for the reply. I did confirm the points you made, and have the details below.
1. check filesystem, if you have enough space, especially /tmp
All filesystems have available space, and /tmp has 310 MB available, before the start of sapinst.
2. check again alert log, trace log for Oracle,
I could not find any errors in the alert_SID.log or any unusual trace files.
3. How did you run sapinst? Are you using "root" account.
I am running sapinst as user root and I am following all the recomendations in the system copy guide (at least as far as I can tell.  ;p )
We have four BI systems in this landscape, and the other three have migrated successfully.  The procedure I am using, is the same as for the other 3 systems and uses the same SAP media directory that was used on the other systems.
One other item that may be part of my problem here, is that this system is the production system, and was originally installed as a high-availability system, using HP-UX Service Guard for clustering.  Currently, this system does not have fail-over enabled, but of course the cluster is still intact.  One required piece of the Service Guard enviornment is the use of a virtual hostname.  This seems to resolve successfully by sapinst, as I see the correct (virtual) hostname referenced several times.  While this is a clustered system (for fail-over purposes), the CI and DB are installed on the same host.  So it is not a distributed system, and if failover had been initiated, it would fail both the CI and DB instance, which is the same and only SAP instance.
This did raise one question in my mind, however.  I am attempting to extract this using the following menu path within sapinst.
SAP NetWeaver 7.0 Support Release 3  --> Software Life-Cycle Options --> System Copy --> Oracle --> Source System Export --> Central System --> Based on AS ABAP and AS Java
Since this does use Service Guard, but is not a distributed system, should I be using a different path in the sapinst tree, for the export?  I have only performed a migration using the above path, so I am not familar with the detailf of the other types, such as High-Availabitly or Distributed-System.
Regards,
Rusty