Option to pre-install MaxDB using SWPM or other for System Copy ?
I am busy with a Unicode Conversion project which involves MaxDB and a System Copy.
During the import and installation of the target system we had several issues relating to parameters not being correct in MaxDB. This caused huge delays in the whole process and unnecessary downtime.
To avoid having to do these parameter changes after waiting for the target install to fail once it has built the database I want to pre-install MaxDB and upgrade it with the necessary parameter changes so that we can avoid issues experienced during the target installation and import of data. I also want to avoid having to wait for 1TB of database volumes to be built during the target install.
My question is then, where in SWPM or what is the best method to use to pre-install MaxDB so it can be used for SAP ? I do not see any option in SWPM to install MaxDB as a standalone database. Note, this is not a distributed system, just a standard Central instance installation. I just want the option to install and configure MaxDB first.
We will be using MaxDB 7.8 since this is what all databases are using in the landscape. After the Unicode Conversion we will upgrade to 7.9 and install the latest enhancements. I have the installation media for 7.8.02.31 - this will be patched to build 41 before the import.
Nelis Lamprecht replied
To answer my original question here are some suggestions:
1) During the import and configuration there is a chance to change your input parameters at a summary screen in SWPM. At this point in the install a DB parameter file is created in your working directory e.g.
You can change certain parameters in this file before continuing.
2) The other suggestion, but clearly not optimal, is to first install SAP and then uninstall it but uncheck the option to remove the database. You can then drop the schema and it is ready for a System Copy import.
SAP MaxDB Team - if you are listening, you need to provide an easy method to install MaxDB before installation of a SAP instance in System Copy! Your customers should not have to do the workarounds as above. You could easily provide a template in SDBSETUP or add it to SWPM. You also need to fix the default MAXSQLOCKS setting of 300000 which is insufficient.
By "fixing" this parameter issue I was able to reduce my import time by half. This downtime could be further reduced if the option to install MaxDB existed because I wouldn't have to wait for database volumes to be built and I could patch the DB beforehand with optimal settings.