Installation media changing during install.

[Former Member]

Hello all,

The "Import ABAP" finally successfully completed all 111 imports! But then another problem occurred

almost immediately after the import. The error was a file not found error for the file "/tmp/sapInstall

/SAP_ERP_6.0_SR3_IDES_Inst._Master/IM_LINUX_X86_64/COMMON/INSTALL/MIGCHECK.SAR".

After confirming that the file was not where it was supposed to be...I copied the file from the installation

media's archive to its proper location.

INFO 2009-03-04 18:21:14.501
Execution of the command "/opt/IBMJava2-amd64-142/bin/java -classpath migmon.jar -showversion
-Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 0. Output: 
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.2)
IBM J9SE VM (build 2.2, J2RE 1.4.2 IBM J9 2.2 Linux amd64-64 j9xa64142-20070708 (JIT enabled)
J9VM - 20070530_2352_LHdSMr
JIT  - r7_level20070315_1745)

Import Monitor jobs: running 1, waiting 0, completed 110, failed 0, total 111.
Loading of 'T100' import package: OK
Import Monitor jobs: running 0, waiting 0, completed 111, failed 0, total 111.

INFO 2009-03-04 18:21:16.81
Execute step extractMigrationCheckerArchive of component|NW_Onehost|ind|ind|ind|ind|0|0|
NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0
|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0

ERROR 2009-03-04 18:21:16.156
CJS-30020  Cannot find file /tmp/sapInstall/SAP_ERP_6.0_SR3_IDES_Inst._Master/IM_LINUX_X86_64
/COMMON/INSTALL/MIGCHECK.SAR.

ERROR 2009-03-04 18:21:16.353
FCO-00011  The step extractMigrationCheckerArchive with step key|NW_Onehost|ind|ind|ind|ind
|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0
|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|
extractMigrationCheckerArchive was executed with status ERROR ( Last error reported by the step
:Cannot find file /tmp/sapInstall/SAP_ERP_6.0_SR3_IDES_Inst._Master/IM_LINUX_X86_64/COMMON
/INSTALL/MIGCHECK.SAR.).

I chose "Retry" after copying the file into the proper directory and the file not found error was no longer an

issue; however, there was a new error.

INFO 2009-03-05 09:13:04.617
An error occured and the user decided to retry the current step:"|NW_Onehost|ind|ind|ind|ind|0|0
|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0
|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0
|extractMigrationCheckerArchive".

ERROR 2009-03-05 09:13:04.812
CJS-00030  Assertion failed: in 
function SAPCAR(sarfile, options) {
    this.base = Archiver;
    if (sarfile != undefined) {
        var fmgt = new FileMgt();
        var exedir = installer.getInstallationParameter("INSTPARA_EXE_DIR") || ".";
        var extension = (new ProcessMgt()).getExe();
        var exe = exedir + "/SAPCAR" + extension;
        ASSERT(arguments.callee, fmgt.isExisting(exe), "SAPCAR not found at path '" + exe + "'");
        if (installer.onOS400()) {
            var real_exe = fmgt.getFSPath("./SAPCAR" + extension).getCanonicalPath();
            if (!fmgt.isExisting(real_exe)) {
                fmgt.getNode(exe).copy(real_exe);
            }
            exe = real_exe;
        }
        this.base(exe, sarfile, options);
        this.createRe = /^a +(.*)$/;
        this.extractRe = /^x +(.*)$/;
        this.appendRe = this.createRe;
        this.testRe = /^.*:[0-9]{2} +(.*)$/;
    }
}
SAPCAR not found at path '/tmp/sapinst_exe.15779.1236182977/SAPCAR'

ERROR 2009-03-05 09:13:04.836
MUT-03025  Caught ESAPinstException in Modulecall: in 
function SAPCAR(sarfile, options) {
    this.base = Archiver;
    if (sarfile != undefined) {
        var fmgt = new FileMgt();
        var exedir = installer.getInstallationParameter("INSTPARA_EXE_DIR") || ".";
        var extension = (new ProcessMgt()).getExe();
        var exe = exedir + "/SAPCAR" + extension;
        ASSERT(arguments.callee, fmgt.isExisting(exe), "SAPCAR not found at path '" + exe + "'");
        if (installer.onOS400()) {
            var real_exe = fmgt.getFSPath("./SAPCAR" + extension).getCanonicalPath();
            if (!fmgt.isExisting(real_exe)) {
                fmgt.getNode(exe).copy(real_exe);
            }
            exe = real_exe;
        }
        this.base(exe, sarfile, options);
        this.createRe = /^a +(.*)$/;
        this.extractRe = /^x +(.*)$/;
        this.appendRe = this.createRe;
        this.testRe = /^.*:[0-9]{2} +(.*)$/;
    }
}
SAPCAR not found at path '/tmp/sapinst_exe.15779.1236182977/SAPCAR'.

ERROR 2009-03-05 09:13:05.19
FCO-00011  The step extractMigrationCheckerArchive with step key|NW_Onehost|ind|ind|ind|ind|0|0
|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0
|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0
|extractMigrationCheckerArchive was executed with status ERROR ( Last error reported by the step:
Caught ESAPinstException in Modulecall: in 
function SAPCAR(sarfile, options) {
    this.base = Archiver;
    if (sarfile != undefined) {
        var fmgt = new FileMgt();
        var exedir = installer.getInstallationParameter("INSTPARA_EXE_DIR") || ".";
        var extension = (new ProcessMgt()).getExe();
        var exe = exedir + "/SAPCAR" + extension;
        ASSERT(arguments.callee, fmgt.isExisting(exe), "SAPCAR not found at path '" + exe + "'");
        if (installer.onOS400()) {
            var real_exe = fmgt.getFSPath("./SAPCAR" + extension).getCanonicalPath();
            if (!fmgt.isExisting(real_exe)) {
                fmgt.getNode(exe).copy(real_exe);
            }
            exe = real_exe;
        }
        this.base(exe, sarfile, options);
        this.createRe = /^a +(.*)$/;
        this.extractRe = /^x +(.*)$/;
        this.appendRe = this.createRe;
        this.testRe = /^.*:[0-9]{2} +(.*)$/;
    }
}
SAPCAR not found at path '/tmp/sapinst_exe.15779.1236182977/SAPCAR'.).

[root@xa4-myexaserv AS]# 

This is not the first time I've experienced the installation media "losing files" during an install. Is there a way to prevent this from happening (other than running it from a DVD or possibly a read-only file system)?

Is there a way to recover when this does happen?

Kind Regards,

Zach

-

---

RHEL 5.2

SAP_ERP_6.0_SR3_IDES_Inst._Master

RDBMS_MAXDB_7.6.03_Build_09

NW_7.0_SR3_Kernel_WINDOWS__LNX_X86

Java:

[root@xa4-myexaserv sapFiles]# java -version
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.2)
IBM J9SE VM (build 2.2, J2RE 1.4.2 IBM J9 2.2 Linux amd64-64 j9xa64142-20070708 (JIT enabled)
J9VM - 20070530_2352_LHdSMr
JIT  - r7_level20070315_1745)

-

---

UPDATE

I copied SAPCAR from /sapmnt/XA4/exe/ to the expected directory. Resulted in:

INFO 2009-03-05 09:59:56.366
An error occured and the user decided to retry the current step: "|NW_Onehost|ind|ind|ind|ind
|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0
|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0
|extractMigrationCheckerArchive".

INFO 2009-03-05 09:59:58.165
Execute step runPackageChecker of component |NW_Onehost|ind|ind|ind|ind
|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0
|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0

ERROR 2009-03-05 09:59:58.231
CJS-30020  Cannot find file DATA/SAPSTR.LST.

ERROR 2009-03-05 09:59:58.419
FCO-00011  The step runPackageChecker with step key |NW_Onehost|ind|ind|ind|ind
|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0
|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runPackageChecker
was executed with status ERROR ( Last error reported by the step :Cannot find file DATA/SAPSTR.LST.).
}

Is the best course of action to search for the missing files in other directories and archives and copy them

to the expected directory?

Edited by: Zachary Shay on Mar 5, 2009 4:00 PM

[markus_doehr2 · Accepted solution]

> This is not the first time I've experienced the installation media "losing files" during an install.

The reason for that is, that you use /tmp - which is cleaned up in regular intervals of files, that have no open handles.

I always do my installation like

mkdir /install
cd /install
<full-path-to-sapinst>

This will put all temporary files under /install and not under /tmp. This will

- prevent them from being deleted in /tmp

- survive the next reboot to look something up

Markus

[Former Member · Accepted solution]

Thank you Markus,

I am investigating this solution. I'll reply as soon as I test it out. ...never knew that about /tmp; I assumed it was always treated like any other folder unless it was mounted as tmpfs or something similar.

Thank you,

Zach

[Former Member · Accepted solution]

Markus,

Thanks for the insight. I did some research into how /tmp is handled by linux. Here is what I discovered:

/tmp behaves differently among the different distributions.  In the case of redhat there is a
daily crontask called *tmpwatch*.  Basically there is a threshold value for the atime attribute
of a file, and if the file hasn't been accessed within a certain time frame since the last running of
cron.daily...the "idle file" is deleted.  

Unfortunately for an SAP install, some steps take over a day to complete and this causes many files to not

be utilized for a long time. This results in any file stored in /tmp to be deleted by tmpwatch.

Thank you for letting me know that fully specifying the pathname will cause the "temporary install files" to be

placed in a directory other than /tmp. The sapinst_instdir and sapinst_exe.* directories were always being

generated within /tmp. Does the install assume the media is read-only if one executes from the directory

containing the executable? That would explain why it had been using /tmp instead of /tmp/sapInstall

/SAP_ERP_6.0_SR3_IDES_Inst._Master/IM_LINUX_X86_64...

Cheers,

Zach

[Former Member · Accepted solution]

Markus,

I have restarted the install and everything appears to be going well. Files were generated in /install as expected; however, sapinst_inst and sapinst_exe.XXXXXX were created in /tmp. Will this be a problem? Just to be safe I am removing the cron.daily "tmpwatch" task until installation is finished.

Thank you,

Zach

Edited by: Zachary Shay on Mar 6, 2009 6:04 PM

[markus_doehr2 · Accepted solution]

> I have restarted the install and everything appears to be going well. Files were generated in /install as expected; however, sapinst_inst and sapinst_exe.XXXXXX were created in /tmp. Will this be a problem?

No - because the sapinst executables and libraries are running as long as the installation is running. I've done lots of installations and it never caused a problem.

Markus