Sapcar Manifest

Skip to end of metadataGo to start of metadata
  1. Sapcar Extract Manifest
  2. Sapcar Manifest Signature.smf

This document describes how to upgrade a SAP JVM 6.1 or 8.1 for the Diagnostics Agent.

A New Installation of SAP Business Objects 4.1 SP7 with default Tomcat 7.0 Installation comes with (-Xmx) = 2048M & MaxPermSize = 384M. However in some cases when there are multiple users login & execution of reports are happening then this memory is quite low & you can see the performance issue in your BO server where Adaptive Processing Server started responding very slow & sometime it’s. SAP HANA creates redo log backups automatically at regular intervals By default and in during a log backup, only the actual data of the log segments for each service with persistence is written from the log area to service-specific log backups in the file system or to a third-party backup tool. Unpack the archive in to the extraction directory, passing the option –manifest SIGNATURE.SMF to SAPCAR SAPCAR -xvf IMDBSERVER1001227-10009569.SAR -manifest SIGNATURE.SMF p.s.

  • This sounds like a really odd thing to do and you're probably going to run into other issues, but I think there's a way to disable file and registry virtualization by means of your application manifest file. My program has quite a few odd options (such as the BSoD trigger, that you enable in the registry).
  • SAPCAR –xvf IMDBSERVER20.SAR –manifest SIGNATURE.SMF. Select option 1 to install new database. Referring above screenshot, select required.

The Diagnostics Agent cannot patch its SAP JVM automatically. The following paragraph provides detailed information about how to upgrade a SAP JVM.

  1. Log on as <SID>adm with <SID> being the system ID of the Diagnostics Agent (e.g. DAA).

  2. Download the desired SAP JVM by using one of the following links: SAP JVM 6.1, SAP JVM 8.1

  3. Create a new directory for the new SAP JVM/usr/sap/<SID>/SYS/exe/jvm/<PLATFORM>/sapjvm_<VERSION> with <PLATFORM> being the operating system platform and <VERSION> being the full version identifier, e.g. /usr/sap/DAA/SYS/exe/jvm/linuxx86_64/sapjvm_8.1.033.
  4. Change to the newly created directory, with the cd command.

  5. Use SAPCAR -xvf <JVM_ARCHIVE_PATH> to extract the downloaded SAP JVM.

  6. Open the SAP JVM manifest file (sapjvmmanifest.mf) with a text editor, to verify the version. Make sure the line 'sapjvm version' matches the name of the directory you created. Otherwise, rename the directory.

  7. Open /usr/sap/<SID>/SYS/profile/<PROFILE> with <PROFILE> being the filename of the profile, e.g. DAA_SMDA98_myagentshost and edit the properties:

    • _CPARG1
    • SAPJVM_VERSION
    • DIR_SAPJVM
  8. Restart the Diagnostics Agent by executing the command stopsap && startsap
  9. Optionally, remove files and folders in the directory /usr/sap/<SID>/SYS/exe/jvm/<PLATFORM>of SAP JVM versions that are no longer used.

This post explains that how to perform SAP database refresh on HANA SPS 10. Please follow below steps to refresh SAP HANA in your environment.

Scenario:

QAS (HANA Quality) System Refresh (for ECC 6 EHP7) with PRD (HANA Production) backup

SAP HANA system copy Procedure via Database Redirect Restore

Below is the HANA System copy (SWPM) using Backup/Recovery method from Production to Quality.

— SID of HANA Production is PRD –> Schema of PRD is SAPPRD

— SID of HANA Quality is QAS –> Schema of QAS is SAPQAS

IMPORTANT NOTE!!!!

Read SAP note 1844468 – Homogeneous system copy on SAP HANA

If you perform the System copy as per the note 1844468 – Homogeneous system copy on SAP HANA

Highlights:

  1. Take the backup of HANA production database.
  2. Copy/Move the backup from source to target (production to quality) system using scp command. Ensure that target host file system is having enough space for Backup.
  3. Download the latest SWPM.
  4. Download HANA Kernel.
  5. Prepare the SAP HANA License of quality.
  6. Perform pre refresh steps from target (quality) SAP system.
  7. Execute SWPM.

PRD backup:

Take the backup of HANA PRD system

Perform a manual database backup of PRD (PRD HANA database) to File

In the HANA Studio, right click Backup –>(Choose) Back Up System…

Enter the required information:

Destination Type = File

Backup Destination = /backup (Note: Ensure you have enough free space in the /backup FS)

Backup Prefix = COMPLETE_DATA_BACKUP

Click Next

Review the Backup Settings

Click Finish when you are ready to start the HANA backup

Copy the HANA complete backup from PRD to QAS

Copy backup from source to target host using below SCP command.

Scp <Backup files> root@<HANA QAS IP>:<File path> later it prompt for password provide the root password of HANA QAS system.

Provided full permission to backup files in QAS.

It’s recommended to take a backup of QAS.

Download the latest Kernel from service market place which suites for your HANA environment

Please uncar SWPM prefixing with –manifest SIGNATURE.SMF to prevent below error.

“File ‘SIGNATURE.SMF’ cannot be found in the SAP HANA database installation kit”

Sapcar.exe –xvf SWPM10SP17_4-20009707.SAR –manifest SIGNATURE.SMF

Find the below link for more information:

Starting the actual Database restore process:

Sapcar Extract Manifest

Sapcar

Stop all SAP applications & SAP services on QAS

Launch sapinst:

In Software Provisioning Manager 1.0

Choose
1) <Your Product>
2) <Your Database>
3) System Copy
4) Target System
5) <System Variant>
6) Based on <Technical Stack>
Standard System

In present scenario:

Go to Software Provisioning Manager 1.0 –> SAP Business Suite 7i 2013 Support Release 2 –> EHP7 for SAP ERP 6.0 ABAP Support Release 2 –> SAP HANA Database –> System Copy –> Target System –> Distributed System –> Based on AS-ABAP –> (Choose) Database Refresh or Move

Click on Next

Fill with profile path

Enter the Master Password

Choose “Homogeneous System Copy (SAP HANA-specific Backup/Recovery)

Uncheck “Start Migration/Restore Manually”

Enter the following info:

Sapcar Manifest Signature.smf

Database ID DBSID = QAS

Database Host = <QAS Host name>

Instance number of the SAP HANA Database = 00

Password of the SAP HANA Database System Administrator = (If you want to provide the different password than master password, you can change it otherwise Do NOT change!!! Taken from the Master Password)

Provide UC Kernel NW740 SR2 location

Keep default values (for the DBACOCKPIT schema)

Click Next

Enter the Schema = SAPPRD (Enter the schema name from the source system in PRD)

Schema Password = (Do NOT change!!! Taken from the master password)

IMPORTANT NOTE!!!

In the Database Schema dialogs, enter the schema names and the passwords that match the data in the backup. For example, if you install a DEV system and use a backup of the PRD system for the installation, you must specify SAPPRD as the schema in the dialogs instead of SAPDEV. The same applies to the DBA Cockpit schema.

Enter the following:

Database <sid>adm = < Enter source systemSIDADM password >

Database <sid>adm Password = <Enter target system password>

SAPControl WSDL URL = (Keep the default value)

Backup Destination Type = File (We chose file because we are restoring from a backup file)

Enter the following:

Backup Location = /backup

Backup Name = COMPLETE_DATA_BACKUP_refresh

Choose if you want to install a new SAP HANA license in the target database system. A new license is required because the backup that is to be implemented in the target database system derives from another source database, that is the hardware or the database SID has changed.

It’s recommended to check the “interrupt before starting SAP system”

otherwise it starts the DB and SAP after the SWPM completion. If you missed this, recommended to comment BTC and Spool in QAS Instance profile, otherwise SAP start’s and run Production background jobs in QAS and the same will be printed in customer side. To avoid such a situation please do either any one.

Select Local Client directory as HANA Client software Patch. Perhaps you can select “central directory also” Depends on the requirement.

Sapcar manifest hana

Perform the Post System Refresh Activities as per the Homogeneous system copy guide.

We are not including Post refresh activity steps. This will be common like other refresh activity.

Note: Please comment BTC and Spool in QAS instance profile, to prevent production jobs to be run on QAS.