SAP NW7 to EHP (1)


***************** Other Pages on the same topic…. **************************
1. Upgrade to EHP 1 from Netweaver 7.0
2. SAP NW7 to EHP (1)
3. SAP NW7 to EHP (2)
4. SAP NW7 to EHP (3)
5. SAP NW7 to EHP (4)
5. SAP NW7 to EHP (5)
******************************************************************************
So This is the first step where I choose system copying by creating database independent export. As because in my test setup where I did the upgrade activity was not having a tape drive attached and the necessary backup software what is available there in my production landscape. But it did benefit me in both way, I was able to carry the export in a portable drive which is occupying only around 12 GB of space instead of 400 GB if I would have used the database dependent system copy method. For creating the export we need to run the “sapinst” program from the installation master. This you can see in the image below. But I should tell here before hand that 

  • You do need to arrange for a downtime before this activity. If you are doing it flawlessly, this will take you around 5 to 12 hours.
  • Before starting the job, you shutdown your SAP instance (CI and dialogue instances only), do force at least 10 checkpoints, then shutdown your DB. Now backup all the archived log files so that if require you can bring them back to restore successfully.
  • Do a thorough statistics generation for all objects and also the system statistics using brtools…..Although I didn’t and i had to pay the price by sitting a lot of extra hours in front of my terminal doing nothing. If you do the statistics generation before hand you can deselect the option of statistics generation by SAPINST and this will really save you at least 4 hours for a considerable size of SAP database around 500 Gigs.
  • Please go through the related SAP system copy and upgrade material, and yes some SAP notes related to the same.
  • Once the normal downtime is  approved, lock all the user except the administrative e.g. DDIC, J2EE_ADMIN, SAP*, SAPCPIC etc and then from a userid which is having the SAP_ALL authorization you need to run following two reports
  • SMIGR_CREATE_DDL – This will create the .SQL files which is understood by R3Load during the import phase and this for those objects which are non standard or rather can be said as not available in normal SAP system..these are like bitmap indexes and partition tables. This is must, if any system has the related object it will create the necessary SQLs in the directory indicated, or it will not create the same if not required.
  • It will be better if you drop the temporary tables, although it will keep the system running slow for sometime for the queries run. This can be done by running SAP_DROP_TMPTABLES and the related SAP note no is 449891
  • Do a thorough statistics generation for all objects and also the system statistics using brtools…..Although I didn’t and i had to pay the price by sitting a lot of extra hours in front of my terminal doing nothing. If you do the statistics generation before hand you can deselect the option of statistics generation by SAPINST and this will really save you at least 4 hours for a considerable size of SAP database around 500 Gigs.
SAP NW 7.0 Export - EHP Upgrade - ./sapinst
So in tree select NW 2004s Additional life cycle tasks, based on dual stack, the database and central instance.
SAP NW 7.0 Export - EHP Upgrade - Choose Service 2
Once you select the same and click on next button, it will ask the profile directory as the parameter. By asking the profile
SAP NW 7.0 Export - EHP Upgrade - Profile Directory
The database dependent method helps you to do things faster, intact in this Basis job is much less comparing to the OS and backup administrators part. but this always needs higher resources like more hard disk space, more backup media and obviously same backup application software both in the source system as well as the target machine.
I chose database independent method, as because I didn’t have the backup and restore facility in my test atmosphere, and also I had a space crunch in the hard disk of both my source system and  target system. Apart from this, database independent method also keeps the option open to migrate in different OS or Database.
SAP NW 7.0 Export - EHP Upgrade - SAPINST - Define Parameters 1
Then it will ask the target location of the export. So prepare a separate location for the export, which you require when you are doing the import. I have created a partition sized same as the size of my database, but finally I found that the export size cam about 15 GB out of a 400 GB BW database. But it is always safe and better that you should have enough space available on the same machine. If space is on the network, it just elongates the time span.
Choice is also there to choose between ABAP and Java, I feel that you can separate out your java schema from the ABAP if you are in dual stack but I haven’t explored the same yet. I choose both and let it go…
SAP NW 7.0 Export - EHP Upgrade - SAPINST - Define Parmeters - Database Export
continue to SAP NW7 to EHP (2)
***************** Other Pages on the same topic…. **************************
1. Upgrade to EHP 1 from Netweaver 7.0
2. SAP NW7 to EHP (1)
3. SAP NW7 to EHP (2)
4. SAP NW7 to EHP (3)
5. SAP NW7 to EHP (4)
5. SAP NW7 to EHP (5)
******************************************************************************

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s