最近做了很多次system copy，同構，異構，數據庫轉換，數據庫版本升級，OS平臺變更等等. 碰到各種問題，但這過程也挺磨練人，作爲一名合格的Basis顧問，要經的起折磨，折磨的多了，麻木了，也就成佛了. 願與大家共勉.
下面將一些常見的錯誤解決方法和大家分享下：
1. hostname 過長導致disp+work 無法啓動: 主機名應低於20位字符，否則就會出現此類情況.
2. ERROR 2012-04-1421:32:08MOS-01012PROBLEM: 'E:\usr\sap\Z3S\SYS\exe\run/startsap name=C11 nr=20SAPDIAHOST=xxxx' returned with '-1' which is not a defined as a successcode.
將dw更新下大多能解決問題.
3. Migration Key 錯誤 : 如果你確認申請的沒錯, 但系統始終提示錯誤, 可以將sapinst目錄清空後重新安裝.
4. SAP installation OCIServerattach failed rc = 1034 以及 (IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed : 這些大多是share memory太小, 調整下就可以過了.
5. ERROR:invalid checksum in data file"E:sapinstalldisk1EXPORT1/DATA/SAPAPPL1.001" current table was"COIX" .
安裝介質拷貝的有問題, 重新拷貝後繼續安裝.
6. 碰到一些自定義表無法導入: 如果數據不多，可以修改tsk文件跳過, 待系統恢復後利用sql重新導入數據即可.
在系統拷貝前, 一定要先做規劃再動手, 多參看SAP System Copy Guide, 三思而後行. SAP 提供了多種拷貝的方法, 找到最適合自己實際情況的那一種, 做好系統規劃, 不放過任何一個可能遇到的問題, 那就離勝利不遠了！
希望這些解決思路能拋磚引玉. 多一份思考, 多一份收穫！願大家在basis的道路一馬平川.
附: James Yan 前輩寫的ECC6 Post - Installation 步驟
1. Reboot theserver and log in as<SID>adm.Checkthe Oracle environment setup is correct and Brtools is working.
2. StartSAPusingthe Microsoft Management Console. Use standard R/3 troubleshooting procedures(check trace files, etc.) if theSAPsystem does not start up.
3. Log on toclient 000 with an administrative account other thanSAP* or DDIC. If no otheruser accounts exist, log on to the system withSAP* or DDIC and create a newuser account (TxSU01). Create thenew
user account with profilesSAP_ALL andSAP_NEW.
A _xp_,O0Note:You may have to create new companyassignments in Tx SUCOMP first.
4. Purge Source System
Data
Some data from the source system cannot be used by thetarget system. Purge this data as follows:
· Deletecancelled/finished jobs.RunTxSE38,report RSBTCDEL with optiondelete withforced modefor all users.
· Purge allentries in the following tables: TPFET, TPFHT, DDLOG, ALCONSEG, ALSYSTEMS,DBSNP, MONI, OSMON, PAHI, SDBAD, SDBAH, SDBAP and SDBAR (suggested to run“truncate table…” commands at the database level)
· In TxSM58, delete all entries in the system.
5. Transport Management System (TMS).
· Run TxSE06and choose the optionDatabase Copy. Answeryesto all of the prompts.
· RunTxSTMSand configure the Transport System.If this system is part of a multiple system landscape, use virtual systems asplaceholders until the physical system is installed. When the physical systemis installed, remove the virtual systems from the TMS landscape and configurethe server in its place.
6. Initial Checks:Run the followingtransactions:
· TxSM28 (SICK)– Initial consistency check.Correct errors if any exist.
· TxSM50/51– Check processes. Documentcurrent kernel patch level.
· TxSM21– System log. Look for errors andcorrect as necessary. If you receive the errorIn table TCPDB, there are 0 entries, run report RSCPINST asdirected in note# 42305. However, this should not be the case, as the sourcesystem would already contain TCPDB entries for Unicode.
· TxDB02– Check database consistency assoon as possible. Check the Database Recovery Model (should be “Full”) and, ifnecessary, change using SQL Enterprise Manager.
7. System Licensing:
Request a permanent license throughOSS.Install the new license using the operating systemsaplicensecommand or through TxSLICENSE.
8. System Patching (Optional):
· Installthe SPAM update and support packages to the latest levels or to match existinginstances in the same landscape.
9. RFCs:RunTxSM59and verify/adjust the RFC calls topoint to the correct systems or delete outright. It is likely the RFC connection<source system> (type R/3) can be deleted.
10. Client Administration:Dependingon the source system, some steps may not be required. However, all steps shouldbe reviewed for applicability.
· Tx BDLS:Run this transactionto adjust remaining client specific data to the new logical systems created inBD54. (This job may take some time). Log on to the remaining client, run TxBDLS, specify the old logical system(<sourceSID>CLNT<nnn>), and the new, non-existent logical system(<target SID>, and run. You’ll find that the new logical system has beencreated in the table TBDLS (use Tx BD54)
· Tx BD54:Create new logicalsystems as needed for new clients in the target system – format is <targetsystem>CLNT<nnn>. DO NOT delete source system clients as of yet.
· Tx SCC4:Create new clientsand/or adjust the logical system names and settings of current clients to thenew situation.
· Tx SCCL:If needed, perform.local client copies to the requirements of the target system.
11. Solution Manager
· If thenewSAPinstance is connected to aSAPSolution Manager system, download and installthe latest ST-PI and ST/A-PI plug-ins using Tx SAINT. Update the plug-inSupport Packages to the latest levels.
· Keep theST-PI and ST/A-PI versions and Support Package levels the same across instancesof the same landscape.
· Additionally,configuration changes in RZ20 and RZ21 should be checked and reconfigured ifneeded.
12. Spooling:UseTxSPADto adjust output devices to thetarget system hostname. Next, run a consistency check of TemSe objects in TxSP12(TemSe Data Storage ->Consistency Check)
13. System Time Zone:If required, changethe system time zone using TxSTZAC.Perform. this action in a client where modifications are allowed or use TxSCC4to temporarily change clientsettings to allow the time zone change.
14. Help:UseTxSR13to set up the R/3 documentationlink. Point to the local documentation server or theSAPhelp portal:http://help.sap.com.
15. Profiles/Operation Modes
· Run TxRZ10to import profiles of the activeserver (Utilities menu). Change the profile parameters as appropriate. For now,set the default login client (login/system_client = xxx) in the instanceprofile.
· Run TxRZ04and recreate the desired operationmodes with the target server profiles.
· Check/confirmthe proper configuration of operation modes in TxSM63.
16. Other Configuration:
· OSS1:configuretheOSSconnection parameters.
· SMLG:Check configurationand server assignment of logon groups.
· SM54 and SM55:Delete entries intables TXCOM and THOSTS.
· DB13:Delete and recreateany jobs in the calendar.
· SUCOMP:Adjust the system forthe proper company name(s) for the installation.
18. ABAP Loads:Use TxSGENto run a system generation topre-compile the ABAP loads. Select the optionGenerate All Objects of Selected Software Components. At a minimum,select the componentsSAP_ABA,SAP_APPL,SAP_BASIS, andSAP_HR. Watch theTablespace Free space.
19. Perform. a full backup of the target system.
The system installation is complete. You canbegin system configuration.