cancel
Showing results for 
Search instead for 
Did you mean: 

After db restore, restarted sapinst using a different installation media

Former Member
0 Kudos

Hi All,

We are currently performing a system copy installation using a db redirected restore.

First, we downloaded the latest patch level of SWPM10, and run SWPM sapinst until it reach the phase where we performed the db restore (performed by a third-party team). After the db restore, continued the installation, but unfortunately, the sapinst crashed with no clear reason/cause of the crashing in the logs.

We then decided to use our old installation medias (non SWPM), thus using SWPM sapinst, we uninstall the system, however, to save effort on the db restore, and roll-forward, we have excluded the database on the uninstallation. After uninstalling, stopped the database and performed "ipclean -a" command. Afterwards, run sapinst using the old installation media. In the db restore phase, since we have excluded database during the uninstallation, we just continued the session until completion, without encountering error. After the installation session, we were able to start the system.

Since we have around 10 systems we are looking at doing this appoach, can anyone advise if there will be any issue especially on the db state/db consistency?

Can you share what we could check in relation to the topic?

Thanks in advance.

Regards,

Philip

Accepted Solutions (0)

Answers (1)

Answers (1)

Reagan
Advisor
Advisor
0 Kudos

Hello


We are currently performing a system copy installation using a db redirected restore.


After uninstalling, stopped the database and performed "ipclean -a" command. Afterwards, run sapinst using the old installation media.

I believe the systems are running on Unix / Linux OS.

I fail to understand the reason why you are uninstalling the SAP system.

If this an ABAP only stack (assuming) then and you are restoring the database from a backup then what is the need to run sapinst ?

If the SAP systems are already installed and if you want to restore the backup of another system (eg: PRD to QUA) then you don't need to run sapinst.

It is understandable that you use sapinst if you want to create a new system with the database backup of another system.

If you are having a Java stack then it is required to run sapinst.


Since we have around 10 systems we are looking at doing this appoach, can anyone advise if there will be any issue especially on the db state/db consistency?

The DB state or consistency is based on the quality of the backup.

If you are using sapinst to set up a new system with the backup of another system then sapinst is basically adjusting the OS level configuration files and the kernel. It is not doing any import of the data.

If there are already 10 systems and you want to perform the homogeneous system copy for these systems with the backup of another system then the best option is to take a backup of the source system and restore it to the target system and perform the post system refresh tasks.

Regards

RB

Former Member
0 Kudos

Hi RB,

Yes, the system is running on UNIX OS. We are creating a new system from a db backup of another system, and for our case, from a production db backup.

Here's what happened... we have available installation medias available that came from the cd/dvd that are previously available in SMP. Upon reading the KBA 1813498, we found that most of our medias are became obsolete, thus, we decided to download SWPM and use the sapinst that is delivered with it. We downloaded and used the SP04 version for SWPM. Just like what we have read, the sapinst appears to be the same from the sapinst we are previously using from our old installation medias. This installation appears to be fine from the start of sapinst up the the phase of db restore, please see below screenshot. We then requested for the db restore since this will be performed by a separate team.

After the db restore, we continued this sapinst session by clicking "OK". However, when it reached the "Perform DB2 post-load activities" phase, the sapinst crashed.

Considering we have 10 systems to be built by this approach, and 8 of this systems already encountered the same error using the SWPM sapinst, we then decided to use our old approach (using our old installation media and the sapinst that comes with it).

We first tested this by un-installing 1 system (java stack), but while in the un-installation, we excluded the installation of db. Please note that the SAP instance that is uninstalled is the one installed using SWPM. Afterwards, we launched the sapinst from our old installation media, and in the "Exit to restore database", since we have not un-installed the database, we just proceeded by clicking "Ok", without requesting for db restore. While continuing, we don't encountered the issue we encountered using SWPM sapinst, and the installation completed, with no further issues.

However, this is the first time we encountered the issue and performed uninstallation w/o db, and installing SAP system using the same restored db, but the installer came from different folder/directory. That is where the question regarding the system and/or database integrity came from.

Hope this clears the question. Thanks.

Regards,

Philip