最近幾天，有用戶報(bào)告說某些報(bào)表顯示不正常，外部顧問說要打個(gè)補(bǔ)丁。打補(bǔ)丁？偶還沒弄過。后在網(wǎng)上查到資料，完整一點(diǎn)的是英文的，現(xiàn)在我把操作過程和大家分享一下。
????system:AIX-5L 5.3
????SAP:R/3 ECC6.0
????聲明：本人新鳥，壞事了別怪我。
???SAP建議是先將SPAM更新至最新，最新的SPAM包可以從http://serivce.sap.com/spam去獲取。這個(gè)過程我沒操作，因?yàn)槲腋杏X我的SPAM差不多了是最新的。
???整個(gè)補(bǔ)丁的操作過程大致分三步，一是上傳補(bǔ)丁，二是導(dǎo)入隊(duì)列，三是確認(rèn)。
???首先我們?nèi)SS下載補(bǔ)丁包，補(bǔ)丁包下載回來是一個(gè)CAR文件，很明顯，是個(gè)壓縮包，你可以解壓，也可以選擇不解壓，因?yàn)槲覀冇袃蓚€(gè)方法來上傳這個(gè)補(bǔ)丁。
???不管哪種方法，你都先進(jìn)入TC：SPAM,注意，請(qǐng)以DDIC用戶，登錄CLIENT 000
???步驟一：上傳補(bǔ)丁，這里開始講上傳的兩種方法??load support package
???方法一，不解包：進(jìn)入SPAM，選擇菜單??support package --> load packages --> from front end, 然后系統(tǒng)會(huì)彈出對(duì)話框，讓你選擇CAR包的路徑。選中你想打補(bǔ)丁的CAR包，點(diǎn)確定，系統(tǒng)會(huì)再彈一個(gè)對(duì)話框，告訴你這個(gè)包內(nèi)有兩個(gè)文件，文件名是什么，不管它，點(diǎn)擊decompress,對(duì)這個(gè)CAR文件解包。
???方法二：解包，使用SAPCAR -xvf來對(duì)car文件操作，解壓后有兩個(gè)文件，擴(kuò)展名分別是ATT和PAT. 將這些文件轉(zhuǎn)移到系統(tǒng)的/usr/sap/trans/EPS/in 目錄，服務(wù)器安裝在WINDOWS系統(tǒng)的用戶請(qǐng)根據(jù)實(shí)際情況調(diào)整具體目錄。若不清楚，就用第一種方法吧。
?????文件解壓后，我們開始上傳，SPAM,選擇菜單??support package --> load packages --> From application server ,不管啥，點(diǎn)確定就是了。它會(huì)告訴你，從這個(gè)目錄下導(dǎo)入了什么東西的。
????通過上述方法，你可以重復(fù)導(dǎo)入很多補(bǔ)丁，導(dǎo)完后再操作下面的步驟是可行的。
????步驟二：導(dǎo)入隊(duì)列?import queue
????首先我們可以確認(rèn)下目前各模塊補(bǔ)丁打到哪個(gè)level了，進(jìn)入SPAM界面，stat下邊有個(gè)display level按鈕,點(diǎn)它，會(huì)彈出很多component的對(duì)話框，找到你要打補(bǔ)丁的component,看目前l(fā)evel是哪個(gè)，一個(gè)原則上，從低往高level打，反了估計(jì)系統(tǒng)也會(huì)讓你打不了。
????點(diǎn)擊上方屏幕的 display/define ,也會(huì)彈出一個(gè)類似的對(duì)話框，還是點(diǎn)擊你要打補(bǔ)丁的component，它會(huì)列出剛導(dǎo)入了哪些補(bǔ)丁文件，點(diǎn)擊要導(dǎo)入的補(bǔ)丁，這時(shí)對(duì)話框消失，你在queue欄位中，可以看到隊(duì)列號(hào)了。點(diǎn)擊菜單support package->import queue點(diǎn)擊確定(點(diǎn)那個(gè)小車效果也一樣)，系統(tǒng)就開始導(dǎo)入了。 等吧，完事后會(huì)彈出對(duì)話框告訴你完成了，要你確認(rèn)的，開始轉(zhuǎn)入第三步。導(dǎo)入完了可以看STAT的狀態(tài)燈，應(yīng)該是黃色的。
????步驟三，確認(rèn)
????點(diǎn)擊support package--> confirm ,狀態(tài)燈應(yīng)該轉(zhuǎn)成綠色了。
????好了，一個(gè)補(bǔ)丁就完成了。
????整個(gè)過程大體就是這樣，你有多個(gè)補(bǔ)丁就重復(fù)步驟二到步聚三就好。有問題或更好的建議請(qǐng)回復(fù)。
????另外附上原始資料：

The following is procedure to show you step-by-step process of applying different
support packages into your system.
It is always advisable to first verify the SPAM/SAINT version in the system. Check in
http://service.sap.com/ocs for the latest version of SPAM/SAINT. If you do not have
the latest SPAM/SAINT version then download the latest SPAM/SAINT package.
There are certain support packages, which require certain level of SPAM/SAINT. For
such packages, you first have to update the SPAM/SAINT
SPAM/SAINT update and support packs are applied thru Transaction code SPAM.
The SPAM/SAINT update and support packs files are .CAR files, which need to be
unpacked.
Supports packs for Applications area (i.e. changes made to the objects of various
functional modules of SAP) are also know as HOTPACKS
BASIS Support Packs make changes to the BASIS system.
HR Support Packs make changes to the HR Module. Earlier it was known as Legal
Change Patches (LCPs)
Similarly we also have ABAP/4 Support Packs for the changes made to the ABAP/4.
Most of these support packs are in the form of .CAR files, which are available in SAP
Marketplace (http://service.sap.com). You have to download the support packages
required for your system from the Internet or from the SAPServX server.
The following procedure is a step-by-step procedure for applying these Support
Packs.
1. Download the required .CAR files from SAPNet or SAPServX server
2. Put them in a temporary directory either in /usr/sap/trans/tmp or any other
folder which you can create (say, patch)
3. Change to the directory /usr/sap/trans (UNIX) or \usr\sap\trans (NT)
4. Use the command CAR -xvf
extension>
5. The command CAR is case sensitive
6. The command CAR will decompress the CAR file and put two files (with
extensions .ATT and .PAT in the /usr/sap/trans/EPS/in directory.
7. Logon to the SAP system in client 000 as user DDIC
Applying Support Packs and Plug-ins
http://www.sappoint.com
8. Once in the system execute the transaction code SPAM
9. Depending on what version are you in do the following :
For 4.5x : Goto Tools à Upload à Patch
For 4.6x : Goto Support Packages à Load Packages à From Application
Server
10. You will get a pop up box with the list of the patches in the queue. Both the
applied patches and the new ones will be listed
11. Hit the Back button to come to the main screen
12. Click on the Display/Define button on the screen
13. You will get a pop up screen with the unapplied patches.
14. Select the patch or group of patched that you want to apply and hit the enter
key/icon.
15. The patch number will be defined in the queue box.
16. Again depending on the version, you do the following :
For 4.5x : Goto Tools à Apply à Patch
For 4.6x : Goto Support Packages -->>> Import Queue
or click the apply patch / import queue icon on the application toolbar
17. After the patch is successfully applied, you will have to CONFIRM the patch
application.
18. Again depending on the version, you do the following :
For 4.5x : Goto Tools à Confirm
For 4.6x : Goto Support Packages à Confirm
Or click the confirm icon on the application toolbar
19. The light in the status box should turn green.
20. After the patch(es) are applied, execute the transaction code SPAU.
This transaction code will check for the changes made by the patches as
well as by the user via OSS notes etc to the system
You can compare the changes and decide to keep the changes made to the
system via OSS notes or return the objects to original.
At times depending on the situation, you may have to reapply the OSS notes
after returning back the object to original
Before applying the patches, check for the SPAM version. It is always advisable to
have the latest SPAM version running on the system. You can download the latest
SPAM version from the SAPNet or SAPServx server. There are patches, which require
a certain level of SPAM version in order to be applied.
Applying Support Packs and Plug-ins
http://www.sappoint.com
Some of the Possible Errors during Support Package Application
The solutions provided below may or may not work for you. They worked for
me under the circumstances that I got these errors.
CANNOT_CREATE_COFILE
If while applying a patch, you get an error CANNOT_CREATE_COFILE delete the
concerned file of the patch from the /usr/sap/trans/cofile and /usr/sap/trans/data
directory.
After deleting the files restart the process. The patch application may work
EPS in IS IN OLD FORMAT
If you are unable to upload the queue and you see a message like EPS in IS IN OLD
FORMAT , check for the SPAM version and do a SPAM update. Delete the concerned
files (i.e. the .ATT and .PAT files from the /usr/sap/trans/EPS/in directory) and then
decompress the .CAR file and continue with applying the support packs.
OBJECTS_LOCKED_?
There are also times when a patch will fail because an object that it is trying to
modify is locked by a change request.
In such cases, identify the object and the change request and then using SE03
search for the object. Once you have identified the change request unlock the object
and then Continue with the SPAM transaction.
Sometimes the SPAM/SAINT Update process comes out with error. In such
case just go ahead and start the SPAM update process again and it should
go through fine.
Applying Support Packs and Plug-ins
http://www.sappoint.com
Applying Plug-ins
Plug-ins are applied on the R/3 side using the transaction code SAINT
Before applying the plug-ins check the plug-ins that are installed on your system.
Also verify the type of plug-in that you have i.e. if you have plug-in file which is for
installation or if it is for upgrade. If the file that you is for upgrade then be sure to
have the earlier version of the plug-in and its related patches installed in the system
prior to applying the upgrade plug-in.
If you are updating the plug-in then verify that the earlier lower version of the plugin
and its patched are already installed in the system. For example, 4.6B IDES
system comes with PI_1_1999. The plug-in PI_A_1999 is also already applied. If the
PI_1_1999 plug-in is not installed then you will have to install it and its two
patches first before applying PI_1_2000 plug-in.
You will have to upgrade the PI plug-in to PI_1_2000 and then apply related patches.
There six patches in all for PI_1_2000.
The plug-ins is also available as .CAR files.
For Example the .CAR file name for plug-in PI_1_2000 is Pi_nd17b.car
When you apply this plug-in 4.6B IDES system, you may get an error in
ADDON_CONFLICT phase. When you get the error in this phase, follow the note
204461. Basically you will have to download couple of transports (PI_SAINT.CAR
and PI_SAINT_2.CAR) from SAPServ4 and apply them into the system.
If you still get errors even after applying the transports, keeping on clicking on the
Continue icon till you get over the errors.
The following process shows you the steps for applying plug-ins.
1. You should apply the plug-ins in client 000 as any other user other than
SAP* or DDIC. Create a user in client 000 with SAP_ALL profile.
2. Log on the client 000 as the newly created user.
3. Execute the transaction SAINT
4. Upload the plug-in by going thru the menu,
5. Once the files are uploaded. You will get two boxes on the screen. The top
box will contain the list of Plug-ins already applied in the system. The bottom
box will contain the list of plug-in, which are available to be applied.
6. Select the plug-in PI_1_2000 from the second box and click on the Continue
button.
7. In the next screen put the cursor on the Plug-in box and click on the Continue
button
8. After the plug-in is installed successfully, you will be asked to do SPAU checks
or Continue. Click on Continue icon.
9. After that you will get the 4th screen of the SAINT process, click FINISH on
the screen that you get.
10. After the plug-ins is installed, apply patches for the plug-in using the
transaction SPAM. (The process is described in the previous section).

總結(jié)

以上是生活随笔為你收集整理的SAP如何打补丁的全部內(nèi)容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網(wǎng)站內(nèi)容還不錯(cuò)，歡迎將生活随笔推薦給好友。