view the favorites table.

use table 'smen_buffc' to view the favorites table.

How do you find that an operation mode switch occurred?

Maintain profile parameter dynamic with function.

Here is the steps. I really do not recommend to use it especial on a cluster or production environment.

=====================================================================


You can change the parameter using the function module TH_CHANGE_PARAMETER
(transaction SE37 -> Single Test). Set the following parameters here:

Uppercase/Lowercase: X
PARAMETER_NAME: XXXXXXXXXXXX
PARAMETER_VALUE: <the required value>
CHECK_PARAMETER: 0

SAP editing function is activated to modiy table content.

T_code: SE16N

Input "&sap_edit" in the command dialog box, the SAP editing function is activated, so we could edit the table content.

Configure RFCCOM procedure

Normal 0 7.8 磅 0 2 false false false EN-US ZH-CN X-NONE MicrosoftInternetExplorer4

Configure RFCCOM procedure

1. Create the RFC destination with Transaction SM59

2. Register server program（option）

Run by <sid>adm.

rfcexec –g<program id> -a<gateway host name> -x<gateway service>

rfcexec -g RFCCOM.172.23.134.129 -a SAP-rix3600 -x sapgw00

rfcexec -D RFCCOM_SAPSRV01

rfcexec -g RFCCOM.172.23.134.20 -a SAP-rix3600 -x sapgw00

rfcexec -D RFCSERVER

rfcexec -g RFCCOM.172.23.134.20 -a SAP-rix6600-1 -x sapgw00

rfcexec –D RFCSERVER

3. Configure RFCCOM.cfg file with rfccom.exe, set RFCCOM.cfg file read-only;

Run rfccom.exe and keep it running.

4. Transaction SMGW, goto logon the clients, verify the program running.

5. Test the Connection RFCCOM_SAPSRV01 successful with transaction SM59,

Hide the User Menu

Hide the User Menu

Is there a way of masking or hiding the User Menus as we are using SAP Standard Menu instead of User Based Menus?

To put it simple, when the user logs on to the system he should have only the SAP Standard Menu.

You have two ways to control this :

1. Default hide for all the SAP users.

Goto SM30 and edit the table SSM_CUST and set ALL_USER_MENUS_OFF = YES and transport the same in production server.

or

2. Hide based on individual SAP users.

you can also try SM30 and maintain table USERS_SSM for individual users.

http://www.sap-img.com/basis/hide-the-user-menu.htm

How to modify multiple items in the SAP menu

Yogi Gunawan
09.16.2003
Rating: -3.84- (out of 5) Hall of fame tip of the month winner

To download SAP menu

PRGN_PRINT_AGR_MENU
EASYACCESS_PRINT_MENU

有关SAP time的虚惊一场

Transaction: CSADMIN

Content server administration时，发现Sever time和Start time都是在午夜时分，心想：难道有内贼乱搞服务器，由于Date是在数月之前，还不好追溯历史操作记录...但Basis只有我一个，不会啊？

后查SAP help,上面明明写着All times are specified in UTC.

忘了加上8小时，是咱干的活，虚惊一场。

How to Enable DLink 624M VPN pass through.

个人电脑通过ADSL拨号上网,可以连接公司VPN,但后经WIFI后(DLink 624M),无法连接VPN.解决方案如下:

Preparing a D-Link DI-624 router for your SBS network - Part 3

http://www.smallbizserver.net/Articles/tabid/266/articleType/ArticleView/articleId/210/Preparing-a-D-Link-DI-624-router-for-your-SBS-network--Part-3.aspx

• Click on the Tools tab, then click on the Misc button.
• By the VPN Pass Through Settings, click the radio button/s for enabled.
• Then click the green tick to Apply your setting.

• After the router restarts, click the 'Continue' button.

• VPN Pass Through is now enabled.

Create index with open on-line index creation

DB02>Configuration>On-line Index Creation

在生产库上不开这个开关就创建索引是不可能的,大批用户会因此而被锁,现在SQL 2005支持在线索引的创建,这真是一个好功能.

SAP默认是关闭,当然建完后再关上就是,动态开关.

SAP help library could not display.

SR13

Set the path.

If SAP help library still could not display,

Save the following script as reg file, and then import to regedit.

REGEDIT4
[HKEY_LOCAL_MACHINESOFTWAREMicrosoftHTMLHelp]
[HKEY_LOCAL_MACHINESOFTWAREMicrosoftHTMLHelp1.xItssRestrictions]
"MaxAllowedZone"=dword:00000001

Delete indexes to free database.

Transaction: SE11, DB02

用DB02根据Index Usage(DB02>Performance>Indexes>Index Usage),筛选出一些User seeks为0的用户自定义的Index,用SE11一一删除,节省出50GB空间.

下一步骤是挑一个空闲日,shrink database 或 shrink datafiles.

等来年空间紧张时,再来得筛选没人用的SAP的Index.

Trouble!!!

8月份,弟弟在大连出车祸.

一切都乱了.

...

今天又飞上去看他...

早日康复,小子.

To avoid to restart your pc after lotus notes crashed.

Kill nlnotes.exe

Kill ntaskldr.exe

Note 1095032 - ST02: History data not available for server

Summary

Header Data

Affected Releases

Correction delivered in Support Package

Related Notes

	1135491 - RSSTAT98 - Inconsistent host name when setting up SAPWLSERV

Business Document Navigator

To store document / image in SAP, we can use Business Document Navigator.
To go to the Business Document Navigator, choose Office -> Business Documents -> Documents -> Find (transaction code : OAOR).

SPRO:

SAP Customizing Implementation Guide -> SAP Netweaver -> Application Server -> Basis Services -> Business Document Service

When you are using transaction OAOR to store document manually, first you have to maintain table class in tcode SBDSV1

Portal Response time is taking high...

CAF:GP:MailConnector:run():insideCycle from J2ee_Guest user causes more CPU and Resources utilization is happening.

Followed procedure for stopping specified request:
Go to Visual Admin > Global Config > Services > caf/eu/gp/model
Set mailconnector.start_thread = false.
Needs a restart.

https://forums.sdn.sap.com/thread.jspa?threadID=1157363&tstart=0

https://forums.sdn.sap.com/thread.jspa?messageID=6622200&tstart=0

SAP® standard / special users

SAP® standard / special users

With the installation of a SAP® system, some standard users are created in the individual clients or system environments. Some of these users have already high authorizations from the beginning, and of course most of them have standard passwords assigned that are generally known.
These special users need special treatment and special protection.

1. SAP*
The user SAP* exists right after the installation in all clients. He has the composite profile SAP_ALL assigned and with that all relevant authorizations for the system set up.

SAP® has implemented a backdoor [coding] for this user.
If someone deletes the user SAP*, a login is possible with the standard password PASS including the corresponding SAP_ALL authorizations.

To prevent a login of the SAP* after a deletion, the parameter login/no_automatic_user_sapstar can be utilized.

With a parameter setting to 0 the login is possible.
Any value higher than 0, prevents a login after the deletion.

The standard password for this user directly after the installation is 06071992.
The standard password after deletion is PASS.

The preferable method to protect this user is the deactivation of SAP* :

- Remove all authorizations from this user.
- Lock the user account.
- Set the parameter login/no_automatic_user_sapstar
to 1.
- Activate the audit log for this user.

You can also consider to assign this user to a user administration group that is protected by a dual control principle.

This report RSDELSAP deletes the user SAP*in the client 066. The corresponding source code is not active but available.

2. DDIC
The user DDIC is established in the client 000 and 001 with the installation
[and copies of these].
This standard user is uitilized to cover installation and release updates including changes to the data dictionary. The use of the transport management system is restricted to Display only.
This is the protection against direct developments.
As the technical steps related to this process are initiated in the client 000, the DDIC only needs to be a dialog user in this client.
In all other clients he can be set to the user type “system”.
The standard password for this user directly after the installation is 19920706.

The report RDDPWCHK allows to check the password that is assigned to the user DDIC. In case the password matches, the dialog window will be closed. For mismatches the message False is displayed.
The counter for false login does not count these password detection attempts.

3. TMSADM
The user TMSADM is automatically created at the set up the change and transport management system in the client 000.
His user type is “Communication”, and he is utilized for transports by the CTS.
He has the profile S_A.TMSADM assigned that authorizes the use of RFC with display of the development environment e.g. as well as writing to the file system.
The standard password for this user directly after the installation is PASSWORD.

4. SAPCPIC
The user SAPCPIC is created as a “communication” user at the installation and is utilized especially for EDI. The standard profile S_A.CPIC restricts the access to the use of RFC.
This user is coded into the function module INIT_START_OF_EXTERNAL_PROGRAM together with his standard password. This needs to be considered in case of password changes for this user.
The standard password for this user directly after the installation is ADMIN.

5. EARLYWATCH
The user EARLYWATCH is created in the client 066 at the installtion. He can be utilized for remote control by SAP® and is only set up with some standard authorizations S_TOOLS_EX_A for performance monitoring. The user is to be locked in general, and can be unlocked upon request.

Evaluation
For the evaluation of the passwords you may use the report RSUSR003.

6. SAP* in J2EE
The user is established with full authorizations for the administration.
With regard to security, the user has no standard password assigned.
To utilize this user as emergency user the properties in the UME need to be maintained.
Setting the ume.superadmin.activated property to true will activate the use of this user for emergency cases.
Setting a password in ume.superadmin.password will then activate the user finally after the restart of the engine.
While the user SAP* is in use, all other users will be inactivated during this time.
When the system is fixed, the deactivation can be achieved by setting the ume.superadmin.activated property to false.

7. J2EE_ADMIN_
This user is the Java standard user with full administration authorization in this environment. The password is to be assigned during the set up.
High complexity is recommended for this password.

8. J2EE_GUEST
This user is a Java standard user who can be utilized for anonymous access.
The user is locked per default. The password is assigned during the installation.

9. SAPJSF_
This user is a standard communication user for LDAP [Lightweight Directory Access Protocol] data sources.

10. ADSuser
This standard user is utilized for the communication between Java and ADS
[Adobe Document Service].

11. caf_mp_scvuser
This standard user is utilized in the context of the Composite Application Framework (CAF) core transport system and communication with other Java services.

SAPSYS perform rollback

In APP server, SM21 check the system log, found a lot of "SAPSYS R6 8 Perform rollback"

https://forums.sdn.sap.com/thread.jspa?threadID=478722

This is normal and you will see it done by sapsys (internal) in your System Log SM21.

An SAP rollback is performed when a user backs out of a transaction losing previously entered data, therefore to maintain transactional consistency SAP does not partly save the data, it performs a rollback.

How to change SAP portal favicon?

PC散热

前一阵子玩三国无双时，发现一进入或玩没多久,电脑自动重启，但其它操作如上网，Office，QQ小游戏都没事，以为是游戏crack得不好，装其它大的游戏，一玩一样死直直。。。猜想可能是夏天到了，PC散热问题就显示出来。为不影响个人心情，足足数周没得玩啊，遂采取下列方法： 1，折机箱档板，整一PC就象没了壳的乌龟，无效； 2，由于是3D游戏，怀疑是显卡出问题，清理，无效； 3，发现显卡有电容爆浆，去宏远电脑城换电容，10元，无效； 4， 重装显卡驱动，无效； 5，装上N个降温软件，监测到有个TEMP2温度极高，开机就55了，摸摸CPU风扇，有点热，怀疑是CPU作怪，但降温软件，都是老东东，无效 6，清洗CPU，无效； 7，上电脑城买导热硅胶一瓶，生人5元，熟人就3元啦，将CPU就辅上一导，无效； 8，无意之中，烤机过程中摸摸主板这里哪里的，发现有一块散热片特热，估计降温软件TEMP2指得就是这里，看样子是北桥，查一下北桥的作用： 从视觉上看靠近CPU的那个芯片就是北桥芯片，而北桥芯片就是为了控制处理器与内存和显卡之间数据交流的处理芯片。 而南桥芯片就是离处理器较远的那一颗芯片，是为了控制和协调外存储设置和输入输出设备以及其他外设之间的数据交流的。 由于北桥芯片的工作量较大，所以一般上方会有一块散热片或是散热风扇。 由于北桥芯片在主板上承接着重要且决定性的作用，所以一般主板芯片组的型号一般是以北桥来命名的，比如你看到的某款主板的型号为 P45 G31 等等。 9，明白了，折开散热片一看，装机时的硅胶早就溶一芯片四周了，清洗后，辅上导热硅胶，装上散热片，开机，手摸上去感觉温度不高，再进游戏。。。嘿嘿

How to disable mass transports?

Copy form sap help.

http://help.sap.com/saphelp_nw04/helpdata/en/3f/d6f463e05611d3b4c1006094b9ea64/frameset.htm

Transport Control Parameters

The following parameters for the transport control program and the Change and Transport System (CTS) are set according to the chosen transport strategy:

You can display these parameters in the TMS system overview. To do this, position the cursor on the appropriate system and choose SAP System ® Display. The tab Transport tool contains all the profile parameters.

report RPUMKG00

Please advise your system administrator that all features must be regenerated.
Please note that this generation must take place in client 000 first, and then in all other clients (report RPUMKG00)

SAP Security Audit log size

SM19有两种audit方式: 静态和动态

SM19

,第一页是静态设置profile,filter...active, 最后提示重设instance.

静态audit还要在启动profile里设置rsau/enable=1(默认是0,不启用audit)

第二页是动态设置,设置filter后acitve即可启用AUDIT,不用设置rsau/enable=1.

用SM20或SM20N查看记录, SM18可以按日期删除记录.

How to configure a firewall for domains and trusts

Windows Server 2003 and Windows 2000 Server

WORD及EXCEL行列转换实现方法收藏(转)

WORD及EXCEL行列转换实现方法收藏 【IT168 实用技巧】在WORD操作中，我们有时需要将Word表格的行与列进行交换(也称为表格转换)，但Word本身并没有提供现成的功能可供使用，传统的办法是手工转换。不过这样一来，操作效率低，同时，还容易出错。最根本的原因是不符合我们现代办公的轻松、方便的理念。（相关文章：修复变成乱码的Word文档） 今天，为大家介绍两种方法，可以轻松实现WORD行列转换。以下两表为行列转换前的表一及转换后的表二。通过下列所讲方法，可将表一转换为表二的形式。 表一 表二 　　一、借助EXCEL法 　　1. 首先要在Word中右击表格左上角的十字标全选整个表格，然后执行右键菜单中的“复制”命令。（如图1所示） 图1 　　2. 接下来打开Excel，在任意单元格处点击鼠标右键，选择“选择性粘贴→文本”命令，将Word表格粘贴到Excel中。（如图2所示） 图2 　　3. 选中并右击复制图2中这些带有数据的单元格。 　　4. 然后切换到另一空白工作表中，右击并执行“选择性粘贴”命令。最后在弹出的对话框中勾选“转置”复选框后点击确定即可。（如图3所示） 图3 　　5. 此时，我们便会发现Excel表格中的行列已经按照我们的要求互换了，而且各个单元格的数据也分毫不差，这时再将转置好的表格拷贝回Word就行了。对于转换成功的表格，我们要重新设置一下新表格的边框，因为转换成功后的表格默认是没有边框的。 方法二、替换法 　　1.　首先选中表一的一列数据并复制，在一打开的空白Word文档中使用“编辑”菜单下的“选择性粘贴”命令，选择“无格式文本”进行选择性粘贴，然后打开“查找和替换”对话框。 　　2.　在“查找内容”框中输入“^p”(回车符)，在“替换为”框中输入“^t”（制表符），点击“全部替换”，现在你会发现一列数据变成了一行数据，再将全部数据选择性粘贴回所需表格中即可。(如图4所示)　 图4 　　3.　用同样的方法，将其它列中的数据转换到表格的相应位置中。 　　注：若将行变为列需在“查找内容”框中输入“^t”，在“替换为”框中输入“^p”。

How to customize the Login Screen in SAP Enterprise Portal

具体可参考:

http://syswebs.info/index.php?hl=f5&q=uggc%3A%2F%2Fwfov.oybtfcbg.pbz%2F2006%2F09%2Fubj-gb-phfgbzvmr-ybtva-fperra-va-fnc.ugzy

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/371e9d90-0201-0010-c39c-fd2956154ab3

这里要指出的是,可直接找到该文件,修改后重启portal即可

另外,如文件中的四位编码是unicode,非英文(比如中文)将文字转换成unicode再按格式拷贝就行.

例如,欢迎

xtit_WELCOME=u6B22u8FCE

Create a New Parameter ID

Create a Parameter Id

SE80 ==> Edit Object==> More==> New Parameter id==>New.

Data protector command: locked device.

omnidbutil -show_locked_devs

If this shows something and you are absolutely certain that the device is not is use you can free it up with:

omnidbutil -free_locked_devs

SAP Conter Server

Transaction: OAC0, CSADMIN,

http://help.sap.com/saphelp_nw70/helpdata/EN/c4/cefa3882cd8229e10000000a11402f/frameset.htm

SAPDB problem

We can not upload image to SAPDB, when one session upload holding, all the other session can not access image in SAPDB, but when we restart SAPDB, we could read the image,...Finally, we found the cause is the data area full used to 99%, so add new datafile to add free space, but found something interested.

1, datafiles, or call data volume cannot delete;(From google search, SAPDB 7.6 should be support possible),

2, there are parameters to limit the datafile number and all size, if you want to add datafile, it should tune first.

 查看全文

DOS命令＋Excel＝批量文件重命名

在《电脑爱好者》2005年第9期的《DOS快餐店》中介绍了使用DOS命令为文件快速重命名，如果要对文件进行批量重命名，是否就必须使用带有循环语句的批处理？其实可以用Excel和DOS命令结合，实现简单高效的批量文件重命名。
任务:在C:mypictures目录中包含以下文件:002.jpg、003.jpg、004.jpg、005.jpg。要将它们分别改名为泰山风景1.jpg、泰山风景2.jpg、泰山风景3.jpg、泰山风景4.jpg。
第一步:运行CMD打开“命令提示符”窗口，用cd命令进入文件所在目录(cd c:mypictures)，然后用“dir *.jpg /b>temp.bat”命令将当前目录中的JPG文件名输出到临时文件temp.bat中。
第二步:用“记事本”打开C:mypictures中的temp.bat，全选并复制该文件中的内容，然后打开Excel，定位到A1单元格，右击选择“选择性粘贴→确定”(见图)，在B1单元格中输入第一个文件的目标文件名(如“泰山风景1”)，通过拖拽B1单元格右下角的填充柄在B列生成文件名序列，即“泰山风景1”、“泰山风景2”、“泰山风景3”……
第三步:在C1单元格输入公式“="ren "&A1&" "&B1&RIGHTB(A1,4)”(不含外侧中文引号)，然后通过填充柄在C列生成序列。选中C列中所有生成的序列,复制到temp.bat文件中，覆盖原来的内容，保存退出。最后双击Temp.bat运行之，批量文件改名即告完成。

SMTP port

无意中的发现，发INT的邮件出不去了...

1, SMICM, goto services

原来SMTP服务不知为何被删除了，重新添加；但发现一个bug,无论为SMTP指定任何一个端口，如0，SMTP服务激活无误，对转发邮件无不良作用；

2，SCOT

只要在SCOT的SMTP设置中端口设置无误，port=25；

An error occurred while the wizard was checking the current Windows product license. Error Code: 8: 0x8007007f

I found there was an error on SAPDL580 server, the message from event log display "An error occurred while the wizard was checking the current Windows product license. Error Code: 8: 0x8007007f".

When I tried to login the server four times this morning, it refused me login and hung black screen, I had to hard boot the server.

And I checked the Microsoft help, it seams that the error was caused by install the windows SP2 with RDP by you last night. Some suggestion said it should be right after reboot, other said it should be uninstall the SP2.

SAPconnect Administration (Transaction SCOT)

SAPconnect Administration (Transaction SCOT)

You have to configure SAPconnect settings for every client that is used for send processes.

· Default Domain

Under Settings ® Default Domain, define the domain of the SAP system client. This allows for the following to take place:

· The SMTP plug-in logs on to the mail server using the domain as ID.

· The message ID of the outbound e-mails is assembled with this domain.

· If an SAP user who does not have an Internet mail address sends an e-mail, a sender address consisting of the SAP user name and this domain is generated.

· Nodes

Each client has an SMTP node. This node is created by the SAP system and cannot be deleted. The following steps need to be carried out to configure the node so that sending Internet mail is possible:

i. Make sure you are in the Node view.

ii. Double-click the node name.

iii. Choose Node in use.

iv. In the Mail Host and Mail Port fields, specify the mail server to which the outbound mails are to be sent.

v. Next to Internet, choose Settings.

vi. Enter the address area of the recipient addresses that are to be reached using this node. In general, * is used if all e-mails are to be sent using SMTP.

vii. Enter the output format for SAP documents. We recommend that you use the following settings:

viii. Confirm your selection.

If you also want to configure the node for sending faxes:

i. Next to Fax, choose Settings.

ii. Enter the address area of the recipient addresses that are to be reached using this node. In general, * is used if all faxes are to be sent using SMTP.

iii. Enter the output format for SAP documents. We recommend that you use the following settings:

iv. Enter the domain of the fax server or fax provider under Conversion into Internet Address. The system generates the local part of the Internet address automatically. The address therefore takes this format: FAX=+RecipientNumber@Domain.

v. Confirm your selection.

If you also want to configure the node for sending text messages (pager/SMS):

i. Next to Pager (SMS), choose Settings.

ii. Enter the address area of the recipient addresses that are to be reached using this node. In general, * is used if all text messages (pager/SMS) are to be sent using SMTP.

iii. Enter the domain of the text message (pager/SMS) server or provider under Conversion into Internet Address. The system generates the local part of the Internet address automatically. The address therefore takes this format: SMS=+RecipientNumber@Domain.

iv. Confirm your selection.

· Send Job

E-mails sent from an SAP application are first stored in a queue. A periodical background process, the SAPconnect send job, gets the e-mails from this queue and sends them over the Internet. To schedule this job in SAPconnect: Administration, proceed as follows:

i. Choose View ® Jobs.

ii. If no other job has been scheduled, choose Job ® Create.

iii. Enter a job name and confirm it.

iv. Select the variant SAP&CONNECTALL by positioning the cursor on it.

v. Choose Schedule Job.

vi. Choose Schedule periodically.

vii. Select the interval you require, such as 10 minutes.

viii. Choose Create.

· Inbound

If you want incoming e-mails that have a particular address or particular content to automatically start a program that processes these mails, you can configure this under Settings ® Inbound Processing.

If you want incoming e-mails that have a particular address or come from a particular sender to be automatically forwarded to another recipient or another distribution list, you can configure this under Settings ® Inbound Processing.

UPService Error

Describes:

The description for Event ID ( 4 ) in Source ( UPService ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: UPService: PDH FAILED

Solution:

This error can rack up considerable events in the Application Log. On my R&D system I get 7 per 5 minutes when it occurs, then it maybe 6 weeks prior to getting more.

Currently the best workaround for this event is to stop and "disable" the following 2 services under Service Control Manager.

"HP UtilProvider Data Collector"
"HP UtilProvider WMI Provider"

These two services are only used by HP Virtual Machine for Windows Guests (unlikely you'll be using) and HP Capacity Advisor (again unlikely you'll be using).

We are working on a fix for this issue which will be in a future version of the SmartSetup Media (SSM).

Registering a program on the Gateway

Many times I have come across error in SM59 transaction saying the program is not registered on the gateway

RFC connection test in SM59 might give error similar to this

———————————————————————————————————

Logon Connection Error

Error Details Error when opening an RFC connection

Error Details ERROR: program <program id> not registered

Error Details LOCATION: SAP-Gateway on host <hostname> / sapgw<instance no>

Error Details DETAIL: TP <program id> not registered

Error Details COMPONENT: SAP-Gateway

Error Details COUNTER: 16793

Error Details MODULE: gwr3cpic.c

Error Details LINE: 1694

Error Details RETURN CODE: 679

Error Details SUBRC: 0

Error Details RELEASE: 700

Error Details TIME: Mon Sep 17 13:08:02 2007

Error Details VERSION: 2

———————————————————————————————————

The program in the above error should be registered in the gateway for this connection test to complete successfully. The server program rfcexec is responsible for its registration on the gateway.

To register the program login into the OS level as sudo su - <sid>adm and execute the following command.

rfcexec –g<program id> -a<gateway host name> -x<gateway service>

rfcexec is the server program name, the <program id> can be obtained from SM59, it is case sensitive and should match with the entry in SM59. The <gateway host name> and <gateway service> can be obtained from the transaction SMGW. When this command is executed it goes to a hanging loop.

The connection will fail once this command is terminated or the user executing this command logs off

To avoid this, instead of using the above mentioned command an entry should be made in the file saprfc.ini

To do this, execute the following command

sudo su - <sid>adm

rfcexec –D<destination name>

<destination name> is the RFC destination name in SM59

So now we are done with registering the server program, but how do we check it is registered, once a server program is registered it is displayed in the Logged on clients in SMGW.

In transaction SMGW choose GOTO-> Logged on clients. There should be an entry for the server program in the screen that is displayed with system type Registered_TP (which indicates that the program is registered)

There can be many reasons due to which we might get this error saying server program is not registered, once such instance which I faced was where in the TREX server, a new RFC destination was defined, the TREX server creates a new program id each time this RFC destination is defined. This program id was not changed in TCP/IP connection is SM59 which was the reason why the destination was failing

Copyright belongs to

Madhu’s Weblog

http://qsneak.info/index.php?hl=f5&q=uggc%3A%2F%2Fznquhgrxhe.jbeqcerff.pbz%2F2008%2F08%2F10%2Fertvfgrevat-n-cebtenz-ba-gur-tngrjnl%2F

Change domain time

If yYou're using a recent Windows version, you can also use the ntp client that is built into the system. Just execute:

net time /setsntp:pool.ntp.org

With some versions of Windows you can also specify more than one server

net time /setsntp:"0.pool.ntp.org 1.pool.ntp.org 2.pool.ntp.org"

Then Synchronous on the other server immediately when you run,

net time /set /yes

If not, the other servers will be synchronous time per 15 minutes.

 查看全文


 作者 
 lkptantan

 (    basis  )
  
 :: 
最新回复
(0) ::

   静态链接网址 ::

   引用 (0)

   

微软认证:远程开启远程计算机的远程桌面

下面介绍仅仅使用windows的一些命令来实现这个过程。仅供参考了。
　　一。我们可以直接通过在客户端输入wmic命令，来远程开启服务器的远程桌面，命令如下：
　 　Wmic /node:"[full machine name]" /USER:"[domain][username]" PATH win32_terminalservicesetting WHERE (__Class!="") CALL SetAllowTSConnections 1
　　这里的"full machine name“也可以是IP，"domainusername”也可以是本机的帐号。
　　就这样轻松的开启了。。
　　二。可是，如果管理员是空密码，那就开启不了远程桌面了，windows默认是不能使用空密的远程桌面的。
　　如果使用wmic命令，会报错的。
　　这时候可以使用telnet来更改密码，telnet默认是不开启的，我们可以通过ipc$连接来开启，
　　整个过程如下，不多介绍了，都是很简单的命令：
　　1．建立IPC连接
　　net use IP password /user:administrator
　　2．把Telnet服务改成“自动”
　　sc IP config tlntsvr start= auto
　　注意:auto前面有一个空格
　　3．启动Telnet服务
　　sc IP start tlntsvr
　　4．Telnet到服务器
　　telnet IP
　　5．更改管理员密码
　　net user administrator password
　　6．使用wmic命令开启远程计算机的远程桌面
　　7．别忘了远程登录计算机后停用并禁用telnet服务！
　　一：开启远程计算机telnet服务。
　　二：telnet到远程计算机后，更改管理员密码。
　　三：回到本机命令行，运行命令打开远程计算机远程桌面

StorageWorks Command View EVA can not connected

Check the Services "HP Command View EVA" start normally or not.

Connection to partner timed out after 60s

500 Connection timed out

Error: -5
Version: 7000
Component: ICM
Date/Time: Thu Dec 18 09:36:37 2008
Module: icxxthr.c
Line: 2698
Server: SAP-SDFS_01
Error Tag: {-}
Detail: Connection to partner timed out after 60s

1, https://service.sap.com/sap/support/notes/885580

Timeout settings: There are several timeout values that are involved when using the internal ITS:

rdisp/gui_auto_logout: This parameter applies to all kind of user sessions in the R/3 (SAPGui and ITS services). This profile parameter should be set larger or equal to the session timeout of the ITS service (see below).

Session timeout of an ITS service: For each ITS service a dedicated timeout can be set. Call transaction SICF => /sap/bc/gui/sap/its/ => <Service> => Service options => Session-Timeout: <hh:mm:ss>.

Timeout values of the Internet Communication Manager (ICM): There are two kind of timeout values that can be set in the ICM: PROCTIMEOUT and TIMEOUT.

Syntax: icm/server_port_ = PROT=HTTP, PORT=<Port>,
TIMEOUT=<keep alive timeout>,
PROCTIMEOUT=-1

- PROCTIMEOUT: The PROCTIMEOUT argument of the ICM parameter icm_server_port_?? Defines the maximum processing time of a request in the kernel (the default value for processing time is 60 seconds). You should choose a value that fits to the runtime requirements of the ITS services you are using.

- TIMEOUT: The TIMEOUT argument of the ICM parameter icm_server_port_?? defines how long the connection between the browser and ICM should remain open (the default value is defined with the parameter icm/keep_alive_timeout and has the value 60). The parameter has no effect on the session/connection timeout but is used to optimize the performance of the HTTP connection (HTTP/1.1).

For further details, please refer to note #705013.

2, To do this, start Tcode SMICM.
Then Menu: Goto->Services->Menu->Go To->Service->Define. Specify a new port number, and a large “keep alive” time. When testing, just change the port number in the URL to use the newly defined one.

or RZ10.

Parameter : icm/keep_alive_timeout


Short description : keep alive timeout for inactive connections


Parameter description :

If no communication takes place over an existing connection for more
than a certain length of time, the connection is closed by ICM. The
standard value for the timeout is set with this parameter, but can
overridden for each service (see below).

A value of -1 deactivates the timeout. The connection is then never
closed by the ICM.
Caution:
Note that the user context in the work process is not closed after
this period of time. That timeout is defined using the profile
parameter %%rdisp/plugin_auto_logout%%.

Unit : Seconds

Application area: Internet Communication Manager

Default value : 60

Recommend Notes:

Note 705013 - Timeout for ICF services based on ITS

Note 737625 - Parameter recommendations for the ICM

Note 824554 - ICM and SAP Web Dispatcher Timeout Parameter

SAP Enterprise Portal 7 - Modify Default Ports

An SAP portal installation, by default, selects a port for http and https access based on your system number. For example, if your system number is ##, then the default port for portal access would be

* 5##00 for http access
* 5##01 for https access ( aka SSL )

Many Project teams wish to shorten this long url (http://yourserver.yourdomain.com:5##00irjportal). Fortunately, there is an easy way to modify the portal http and https ports and keep it to 80 and 81 ( or anything you wish).

Follow the below given steps to achieve this.
1. Start the j2ee visual administrator tool
2. navigate to cluster -> dispatcher -> HTTP Provider
3. Choose Ports
4. Change the port number to 80 for http and 81 for https
5. Thats it - You’re done!!!!

One extra step that’s required if you’re also running IIS (for example, if you’re using an ITS to communicate with an older R3 system or running TREX), you need to make sure that your J2EE ports do not conflict with any of the IIS ports (including the default web server). The best way of doing that is to ensure that the IIS default web server is pointing at different ports AND is stopped.

作者 lkptantan ( portal ) :: 最新回复 (0) :: 静态链接网址 :: 引用 (0)

Howto avoid irj/portal in the portal URL

Actually, its a bit of a cheat. What happens is that you’re telling the J2EE WAS that if there is no page specified (such as …/index.html), then open the page …/irj/portal.

1. Go to j2ee visual administrator
2. For each Server, Navigate to Cluster-> Server -> Services -> HTTP Provider
3. Enter /irj/portal in the Start Page Text Field
4. Click on Save Properties
5. Restart this service from visual administrator

Access http://yourserver.yourdomain.com and your portal login page should come up.

This means that your SAP J2EE Engine Start Page will still show up if you http://yourserver.yourdomain.com/index.html

Check the SAP(oracle) database version

C:Documents and SettingsAdministrator>set ORACLE_SID=C11

C:Documents and SettingsAdministrator>sqlplus /nolog

SQL*Plus: Release 9.2.0.4.0 - Production on ??? 11? 13 16:53:18 2008

Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.

SQL> connect / as sysdba
Connected.

SQL> select * from v$version;

BANNER
--------------------------------------------------------------------------------

Oracle9i Enterprise Edition Release 9.2.0.4.0 - Production
PL/SQL Release 9.2.0.4.0 - Production
CORE 9.2.0.3.0 Production
TNS for 32-bit Windows: Version 9.2.0.4.0 - Production
NLSRTL Version 9.2.0.4.0 - Production

SQL> 查看全文

ECC 6.0 install error on sap_add_dbccjob step

I am installing ECC 6.0 as ABAP with System Copy method on Windows Server 2003 Standard Edition with MS-SQL Server 2005 as Database Server. I am facing error at the phase "Create SAP stored Procedures" in the step 025 of 220 (sap_add_dbccjob).

Search sdn.sap.com, found a related thread,

Help with CRM 2007 Installation!

https://www.sdn.sap.com/irj/sdn/thread?threadID=800961&tstart=0&messageID=5158006

Try to disable Symantec Endpoint Protection, Worked!

LOAD_TYPE_VERSION_MISMATCH

When we imported a customize structure Z* which append for table RESB to QAS system, it worked; but imported to PRD system, so many users complained they could not run standard SAP programs, like CO13, CO14, CO15 etc.

Check with ST22, found a lot of ABAP runtime errors, LOAD_TYPE_VERSION_MISMATCH.

Search in service.sap.com, found 2 related notes,

Note 713492 - Additional time stamp check in structure administration

Note 1010590 - Structure components with width of more than 65535 bytes

It seams that this causes an memory overflow, and then leads to an error. Based on Note 1010590, the solution was import Support Package SAPKB70012 or higher, or implement the correction instructions. But the copy of PRD, QAS system was not happen the error. So we decided to restart the PRD to try to solve this.

Worked!

codepage 1100 is not released

上周六参加一个SAP培训的讨论会，看见培训用的服务器在英文（EN）登录时报错：codepage 1100 is not release，今天也有群里的朋友问到这个

在SAP找到这个note, Note 144680 - Character set (code page 1100) is not released

哪位朋友相信是手动搞定了这个问题，不知是不是用这个snote？

Why did SAP GUI for Windows 6.40 support end before SAP GUI for Windows 6.20 and 7.10 support does? The Microsoft

As of release 6.40 SAP usually ties the support duration for SAP GUI for Windows releases to the support duration for the development environment used. The reason for this is that we may require corrections from Microsoft for solving an issue in SAP GUI, but Microsoft does not provide us with corrections once support for a development environment is stopped.

• SAP GUI for Windows 6.40 was developed with Visual Studio 2003 which was de-supported by Microsoft on 14th of October 2008. Consequently SAP GUI for Windows 6.40 was also supported until this very day.

• SAP GUI for Windows 7.10 was developed with Visual Studio 2005 which will be de-supported by Microsoft on 31st of March 2011.
  Consequently SAP GUI for Windows 7.10 is supported until this very day.

• SAP GUI for Windows 6.20 is an exception to this rule. It was developed with Visual Studio 98 which is out of maintenance since September 2005. Since we had already announced support for this release to be "longterm" in order to allow customers to reduce their Frontend upgrades SAP GUI for Windows 6.20 is supported until 2010 even though we had to restrict the support (see note 929300).

If you want to know the details, pls check note 147519.

Pidgin 2.5.2 problem

1, If you are a chinese who use QQ, pls reinstall 2.5.1 to recover when you found that the pidgin always crashed when you start QQ;

2, After install 2.5.1, you should downgrade the gta to gtk-runtime-2.12.1-rev-b to repair the QQ display problem.

3, Pidgin support MSN, YAHOO, QQ, SKYPE, GTALK for me.

Pop a Message to specific SAP users

*
* Pop a Message to specific SAP users
*
* How to get a list of all the currently logged on users?
* How to popup an instant message on a user's monitor?
* How to get a specific user's details?
* Usage of 'POPUP_GET_VALUES' function module to get data from user
* without having to write GUI code
*
* Submitted by : SAP Basis, ABAP Programming and Other IMG Stuff
* http://www.sap-img.com
*
REPORT ZPOPUP NO STANDARD PAGE HEADING.
INCLUDE <ICON>.

DATA: BEGIN OF USR_TABL OCCURS 0.
INCLUDE STRUCTURE UINFO.
DATA: END OF USR_TABL.

DATA: L_LENGTH TYPE I,
T_ABAPLIST LIKE ABAPLIST OCCURS 0 WITH HEADER LINE,
BEGIN OF T_USER OCCURS 0,
COUNTER TYPE I,
SELECTION TYPE C,
MANDT LIKE SY-MANDT,
BNAME LIKE SY-UNAME,
NAME_FIRST LIKE V_ADRP_CP-NAME_FIRST,
NAME_LAST LIKE V_ADRP_CP-NAME_LAST,
DEPARTMENT LIKE V_ADRP_CP-DEPARTMENT,
TEL_NUMBER LIKE V_ADRP_CP-TEL_NUMBER,
END OF T_USER,
L_CLIENT LIKE SY-MANDT,
L_USERID LIKE UINFO-BNAME,
L_OPCODE TYPE X,
L_FUNCT_CODE(1) TYPE C,
L_TEST(200) TYPE C.

L_OPCODE = 2.
CALL 'ThUsrInfo' ID 'OPCODE' FIELD L_OPCODE
ID 'TAB' FIELD USR_TABL-*SYS*.

CLEAR T_USER. REFRESH T_USER.
LOOP AT USR_TABL.
T_USER-MANDT = USR_TABL-MANDT.
T_USER-BNAME = USR_TABL-BNAME.
APPEND T_USER.
ENDLOOP.

SORT T_USER.
DELETE ADJACENT DUPLICATES FROM T_USER.
LOOP AT T_USER.
T_USER-COUNTER = SY-TABIX.
SELECT V~NAME_FIRST

V~NAME_LAST
V~DEPARTMENT
V~TEL_NUMBER
INTO (T_USER-NAME_FIRST,
T_USER-NAME_LAST,
T_USER-DEPARTMENT,
T_USER-TEL_NUMBER)
FROM USR21 AS U
JOIN V_ADRP_CP AS V
ON U~PERSNUMBER = V~PERSNUMBER AND
U~ADDRNUMBER = V~ADDRNUMBER
WHERE U~BNAME = T_USER-BNAME.
ENDSELECT.
MODIFY T_USER.
ENDLOOP.
SORT T_USER BY NAME_LAST NAME_FIRST.
PERFORM DISPLAY_LIST.

TOP-OF-PAGE.
PERFORM DISPLAY_MENU.
* End of top-of-page

TOP-OF-PAGE DURING LINE-SELECTION.
PERFORM DISPLAY_MENU.
* End of top-of-page during line-selection


AT LINE-SELECTION.
IF SY-CUROW = 2.
IF SY-CUCOL < 19.
T_USER-SELECTION = 'X'.
MODIFY T_USER TRANSPORTING SELECTION WHERE SELECTION = ''.
PERFORM DISPLAY_LIST.
ELSEIF SY-CUCOL < 36.
CLEAR T_USER-SELECTION.
MODIFY T_USER TRANSPORTING SELECTION WHERE SELECTION = 'X'.
PERFORM DISPLAY_LIST.
ELSEIF SY-CUCOL < 50.
PERFORM TRANSFER_SELECTION.
PERFORM POPUP_MSG.
ELSEIF SY-CUCOL < 67.
PERFORM TRANSFER_SELECTION.
SORT T_USER BY NAME_LAST.
PERFORM DISPLAY_LIST.
ELSEIF SY-CUCOL < 81.
PERFORM TRANSFER_SELECTION.
SORT T_USER BY NAME_FIRST.
PERFORM DISPLAY_LIST.
ELSEIF SY-CUCOL < 93.
PERFORM TRANSFER_SELECTION.
SORT T_USER BY MANDT.
PERFORM DISPLAY_LIST.
ENDIF.
ENDIF.
* End of line-selection

*&---------------------------------------------------------------------*
*& Form DISPLAY_LIST
*&---------------------------------------------------------------------*
FORM DISPLAY_LIST.
SY-LSIND = 0.
FORMAT COLOR COL_NORMAL INTENSIFIED OFF.
LOOP AT T_USER.
WRITE: / SY-VLINE, T_USER-SELECTION AS CHECKBOX,
SY-VLINE, T_USER-MANDT,
SY-VLINE, T_USER-BNAME,
SY-VLINE, T_USER-NAME_FIRST(15),
SY-VLINE, T_USER-NAME_LAST(15),
SY-VLINE, T_USER-DEPARTMENT(20),
SY-VLINE, T_USER-TEL_NUMBER(20), SY-VLINE.
HIDE: T_USER-COUNTER, T_USER-SELECTION.
ENDLOOP.
FORMAT COLOR OFF.
WRITE: /(108) SY-ULINE.
ENDFORM. " DISPLAY_LIST

*&---------------------------------------------------------------------*
*& Form DISPLAY_MENU
*&---------------------------------------------------------------------*
FORM DISPLAY_MENU.
FORMAT COLOR COL_HEADING HOTSPOT.
WRITE: (91) SY-ULINE,
/ SY-VLINE NO-GAP, (4) ICON_SELECT_ALL NO-GAP, 'Select All',
SY-VLINE NO-GAP, (4) ICON_DESELECT_ALL NO-GAP, 'Deselect All',
SY-VLINE NO-GAP, (4) ICON_SHORT_MESSAGE NO-GAP, 'Send Popup',
SY-VLINE NO-GAP, (4) ICON_SORT_UP NO-GAP, 'Last Name' NO-GAP,
SY-VLINE NO-GAP, (4) ICON_SORT_UP NO-GAP, 'First Name' NO-GAP,
SY-VLINE NO-GAP, (4) ICON_SORT_UP NO-GAP, 'Client' NO-GAP,
SY-VLINE,
/(91) SY-ULINE,
/(108) SY-ULINE.
FORMAT HOTSPOT OFF.

WRITE: / SY-VLINE, ' ',
SY-VLINE, 'Cli',
SY-VLINE, 'User ',
SY-VLINE, 'First Name ',
SY-VLINE, 'Last Name ',
SY-VLINE, 'Department ',
SY-VLINE, 'Telephone ',
SY-VLINE,
/(108) SY-ULINE.
FORMAT COLOR OFF.
ENDFORM. " DISPLAY_MENU

*&---------------------------------------------------------------------*
*& Form TRANSFER_SELECTION
*&---------------------------------------------------------------------*
FORM TRANSFER_SELECTION.
DO.
READ LINE SY-INDEX FIELD VALUE T_USER-SELECTION.
IF SY-SUBRC <> 0.
EXIT.
ENDIF.
MODIFY T_USER TRANSPORTING SELECTION
WHERE COUNTER = T_USER-COUNTER.
ENDDO.
CLEAR T_USER.
ENDFORM. " TRANSFER_SELECTION

*&---------------------------------------------------------------------*
*& Form POPUP_MSG
*&---------------------------------------------------------------------*
FORM POPUP_MSG.
DATA: L_MSG LIKE SM04DIC-POPUPMSG VALUE 'Experimental Message',
L_LEN TYPE I,
L_RET TYPE C.

LOOP AT T_USER WHERE SELECTION = 'X'.
PERFORM GET_MESSAGE CHANGING L_MSG L_RET.
EXIT.
ENDLOOP.
IF L_RET = 'A'. "User cancelled the message
EXIT.
ENDIF.
* Get the message text
L_LEN = STRLEN( L_MSG ).
LOOP AT T_USER WHERE SELECTION = 'X'.
CALL FUNCTION 'TH_POPUP'
EXPORTING
CLIENT = T_USER-MANDT
USER = T_USER-BNAME
MESSAGE = L_MSG
MESSAGE_LEN = L_LENGTH
* CUT_BLANKS = ' '
EXCEPTIONS
USER_NOT_FOUND = 1
OTHERS = 2.
IF SY-SUBRC <> 0.
WRITE: 'User ', T_USER-BNAME, 'not found.'.
ENDIF.
ENDLOOP.
IF SY-SUBRC <> 0.
* Big error! No user has been selected.
MESSAGE ID 'AT' TYPE 'E' NUMBER '315' WITH
'No user selected!'.
EXIT.
ENDIF.
ENDFORM. " POPUP_MSG

*&---------------------------------------------------------------------*
*& Form GET_MESSAGE
*&---------------------------------------------------------------------*
FORM GET_MESSAGE CHANGING P_L_MSG LIKE SM04DIC-POPUPMSG
P_RETURNCODE TYPE C.
DATA: BEGIN OF FIELDS OCCURS 1.
INCLUDE STRUCTURE SVAL.
DATA: END OF FIELDS,
RETURNCODE TYPE C.

FIELDS-TABNAME = 'SM04DIC'.
FIELDS-FIELDNAME = 'POPUPMSG'.
FIELDS-FIELDTEXT = 'Message :'.
CONCATENATE ' - Msg from' SY-UNAME '.' INTO FIELDS-VALUE SEPARATED
BY ' '.
APPEND FIELDS.

CALL FUNCTION 'POPUP_GET_VALUES'
EXPORTING POPUP_TITLE = 'Supply the popup message'

IMPORTING RETURNCODE = P_RETURNCODE
TABLES FIELDS = FIELDS.

IF P_RETURNCODE = 'A'.
EXIT.
ELSE.
READ TABLE FIELDS INDEX 1.
P_L_MSG = FIELDS-VALUE.
ENDIF.
ENDFORM. " GET_MESSAGE

*-- End of Program

SAP Tutor Personal Player

here is a link to download

SAP Tutor Personal Player

Remove developer key from DEVACCESS table.

*&---------------------------------------------------------------------*
*& Report zdeldevkey.
*&
*&---------------------------------------------------------------------*
*& Remove developer key from DEVACCESS table.
*&
*&---------------------------------------------------------------------*

REPORT zdeldevkey.
TABLES: devaccess.

DATA: BEGIN OF i_dev OCCURS 0.
INCLUDE STRUCTURE devaccess.
DATA: END OF i_dev.

DATA: i_sel LIKE devaccess OCCURS 0 WITH HEADER LINE.

DATA: vg_check TYPE c,
vg_lsind LIKE sy-lsind,
vl_index TYPE i,
do_num TYPE i,
vg_num TYPE i.

SELECT-OPTIONS: s_uname FOR devaccess-uname.

If sy-uname <> 'KENLEE'.
exit.
Endif.


START-OF-SELECTION.
SELECT * INTO TABLE i_dev FROM devaccess WHERE uname IN s_uname.

LOOP AT i_dev.
WRITE: / vg_check AS CHECKBOX,
i_dev-uname,
i_dev-accesskey.
do_num = do_num + 1.
ENDLOOP.

SET PF-STATUS 'T001'.
*

AT USER-COMMAND.
CASE sy-ucomm.
WHEN 'DELE'.
PERFORM fm_delete_uname.
ENDCASE.
COMMIT WORK.
*&---------------------------------------------------------------------*
*& Form fm_delete_uname
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
* --> p1 text
* <-- p2 text
*----------------------------------------------------------------------*
FORM fm_delete_uname .
DATA: vl_tabix LIKE sy-tabix,
vl_read_line LIKE sy-tabix,
vl_ret TYPE c,
vl_page TYPE i.
DATA: vl_check TYPE c.
vl_read_line = 2.
vl_page = 1.

LOOP AT i_dev.
vl_tabix = sy-tabix.
vl_read_line = vl_read_line + 1.

CLEAR vl_check.
READ LINE vl_read_line OF PAGE vl_page
FIELD VALUE vg_check INTO vl_check.

IF vl_check = 'X'.
READ TABLE i_dev INDEX vl_tabix.
MOVE-CORRESPONDING i_dev TO i_sel.
APPEND i_sel.
ENDIF.
ENDLOOP.

CALL FUNCTION 'POPUP_TO_CONFIRM'
EXPORTING
titlebar = '确认'
text_question = '是否确认删除'
IMPORTING
answer = vl_ret
EXCEPTIONS
text_not_found = 1
OTHERS = 2.
IF sy-subrc <> 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.

IF vl_ret EQ '1'.
delete DEVACCESS from table i_dev.
commit work.
LOOP AT i_sel.
WRITE: /
i_sel-uname,
i_sel-accesskey.
ENDLOOP.
ELSEIF vl_ret EQ 'A'.
RETURN.
ELSE.
stop.
ENDIF.
ENDFORM. " fm_delete_uname

PS, so many thanks my ABAP workmates Owen Zeng.

Migrate EVA Command View to other machine.

Try to reinstall EVA command view on new machine instead of source machine.

It must to install EVA Command View on new machine(Server A) with local group method, with Domain group method will failled with login error "insufficient privilege", and then add the user to HP Storage Admins as member manually.

Login with the user, and the initial screen with pop the following message, select 'OK' to continue,

"Storage System Managed by Another Agent

Another management agent on server XXXXX at IP address 123.123.134.123 may be actively managing storage system sap_eva.

Only one agent is allowed to manage a storage system at a time.

To disable other management agents, simply click the OK button and management will be redirected to this agent.

Click the Cancel button to leave this page without changing the management agent for this system. "

Migrate log file to new disk

Normal 0 7.8 磅 0 2 false false false EN-US ZH-CN X-NONE MicrosoftInternetExplorer4

1, Shrink log file and backup database;

2, Create new disk for migrate log file;

3, Stop LXQ instance;

4, detach LXQ database;

5, Copy log file to new disk;

6, Attach LXQ database with new log file;

7, Startup LXQ instance and test;

8, Repeat 4-7, resume LXQ log file to original path;

Finished in 30 minutes.

SAP help files (.chm) not displayed correctly

Note 857216

http://support.microsoft.com/kb/896054

REGEDIT4
[HKEY_LOCAL_MACHINESOFTWAREMicrosoftHTMLHelp] 
[HKEY_LOCAL_MACHINESOFTWAREMicrosoftHTMLHelp1.xItssRestrictions]
"MaxAllowedZone"=dword:00000001

Method to start SAP Portal Server When MMC System Nodes Are Missing

自己也写过这个情况的记录，现在因为有朋友也出现这情况，一时找不到自己的文档，还是SDN上找一遍凑个数吧

Added by Swathi Rao Padma , last edited by Craig Cmehil on Sep 26, 2008 (view change) Labels: sap, ep EDIT Add Labels Enter labels to add to this page: Tip: Looking for a label? Just start typing.

Igswd.exe is not working

网上很多都说SAP note 824281有solution, 哪只是说有可能是profile的参数太长了，要改成短的。

其实运行IGS的实际命令是：

IGSP = -mode=all -sysname=＜SID＞ -sysno=＜XX＞

只要将这SID和NO填好即可。

sapcar.exe

C:TEMPsp46c>sapcar
usage:

create a new archive:
SAPCAR -c[vir][f archive] [-P] [-C directory]
[-A filename] [-T filename] [-X filename]
[-p value] [-V] file1 file2 ...

list the contents of an archive:
SAPCAR -t[vs][f archive] [file1 file2....]

extract files from an archive:
SAPCAR -x[v][f archive] [-R directory] [-A filename]
[-V] [file1 file2....]

verify the archive:
SAPCAR -d[v][f archive] [-V] [file1 file2....]

append files to an archive:
SAPCAR -a[v][f archive] file1 [file2....]

merge two archives:
SAPCAR -m[v]f "source target"

check availability of files to be processed:
SAPCAR -l [-A filename][-X filename] [file1 file2...]

other options:
-a : append files to an archive
-A FILE : get names to include from file FILE
-C DIR : change to directory DIR
-e : redirect output from stdout to file sapcar_output
-f FILE : use archive file FILE (default DEFAULT.SAR)
-g : ignore case of of archive names while extracting,
testing or listing archives
-h : do not change permissions of existing directories
during extraction
-i : ignore inaccessible files while creating an archive
-l : check availabilty of files to be processed
-lower : convert filenames to lowercase while extracting
-m : merge two archives
-n : print statistical information
-p octalvalue : set permissions of all files in archive to value
-P : use absolute path-names (use carefully)
-r : do not resolve symbolic links/shortcuts while creating
an archive
-R dir : use dir instead of current directory
-s : do free space check
-T FILE : rename files to be included in FILE
-v : verbosely list files processed
-V : compute or verify checksum (obsolete, always set,
for backward compatibility)
-X FILE : get names to exclude from FILE

examples:
create archive with all files and directories in the current directory
including point files:
SAPCAR -cvf MY.SAR .

create archive with all files and directories in the current directory
without point files:
SAPCAR -cvf MY.SAR *
Note that SAPCAR treats "*" and "?" as wildcard characters. The former
matches any character string, while the latter matches any single
character.

create archive with a complete directory and directory rights:
SAPCAR -cvf MY.SAR dir

create archive with all files of a directory without the directory
itself:
SAPCAR -cvf MY.SAR dir/*
if during extraction with SAPCAR -xvf MY.SAR the directory dir does not
exist it will be created with rights 755

create archive with only the files of a directory
SAPCAR -cvf MY.SAR -C dir .
or better
(cd dir; SAPCAR -cvf ../MY.SAR .)

merge two archives:
SAPCAR -mvf "a source-archive.sar target archive from 27.5.1999.sar"

append files to an archive:
SAPCAR -avf archive.sar file1 file2 file3

extracting/verifying files:
If you try to extract files from an archive that is not a valid SAPCAR
archive according to the version 2 specification SAPCAR assumes an archive
of the old format and automatically invokes the appropriate extraction
routine. If it still cannot handle the archive it will stop execution.
Notice that extracting out of old archives only works with the command
options known to the old CAR application.

using absolute pathnames:
If you create an archive with absolute pathnames the files will be
extracted with exactly these pathnames! SAPCAR does not cut the first
slash like the UNIX tool tar.

specifying a list of archives for extracting/verifying/listing:
You may call SAPCAR with the following command line:
SAPCAR -xvf "ARCHIVE1.SAR ARCHIVE2.SAR"
thereby specifying a list of archives you want to extract. Note
that you have to delimit archive names with "," if at least one
of the archive names you call SAPCAR with contains at least one
whitespace character; e.g.
SAPCAR -xvf "ARCHIVE WITH BLANK.SAR, ARCHIVE.SAR, ARCHIVE2.SAR"

using A, T and X option:
All entries in the specified files are treated relative to the current
working directory unless the entry is an absolute pathname (in this case
the relevant file will be archived with an absolute pathname).
If you want to specify a directory path in these files use the slash ("/")
as path delimiter.

Use the pipe sign ("|") to separate old and new names in a T file when
these names contain whitespaces. If neither the old file name nor the new
one contains any whitespaces you may use whitespaces as delimiter between
old and new name (that means a valid CAR rename file is also a valid SAPCAR
rename file and hence may be given with the -T option).
Note that pattern matching is not supported for entries in -A, -T and -X
files (i.e. "*.cpp" will not result in processing all cpp-files
in the current directory).

Lines starting with "#" as the first non whitespace character will be
ignored by SAPCAR (this also holds true of lines containing only
whitespaces).

If you insert a directory name in the specified file the complete
directory with the directory rights will be included in the archive.

If you specify dir/filename only this file will be included in
the archive. During extraction the directory dir will be created if
it does not exist.

using -C option:
All relative filenames in the command line are treated as relative
to the specified directory.

SAPCAR 2.0, build 410504

C:TEMPsp46c>

If you have a lot of .car files in the folder,which you want to upgrade the kernel, you can run the following command:

C:TEMPsp46c>sapcar.exe -xvf "*.car"

SPAM: QUEUE_NOT_EMPTY ... HELP URGENT

System: 46C/NT4/Ora817

I am trying to import the SPAM update KD40. The import aborts at CHECK_REQUIREMENTS with cause of error QUEUE_NOT_EMPTY. I seard OSS but nothing.

Solution:

delete or remove content of the buffer file in usrsaptransbuffer folder.

Upgrade Procedure / Support Packages

Upgrade Procedure / Support Packages

During an upgrade or the import of an Support Package, existing objects of the SAP standard are overwritten with the objects redelivered. To help the customer retain the objects modified in a previous release, SAP provides all modified objects which are redelivered (in an upgrade or Support Package) in the upgrade adjustment of transactions SPAU and SPDD. These transactions allow customers to enter their modifications into the corresponding new objects being delivered at upgrade. The Modification Assistant supports this process of adopting customer modifications.

In the past, all objects modified by a customer and delivered again by SAP, an IBU or an SAP partner, had to be manually re-modified during an upgrade. Now, modifications are either automatically adopted or the system provides you with an assistant for adjusting your modifications to the newly upgraded configuration.

In general, objects altered using the Modification Assistant can now be automatically accepted into the upgraded system if the modifications undertaken in the original version do not directly overlap those made in the customer version. If collisions occur between the two versions at upgrade (naming collisions, or if SAP has deleted an object modified by a customer), the system offers support during the upgrade, which means that a semi-automatic adjustment is made. In some cases, however, you may still have to manually adjust objects using ABAP Workbench tools.

Objects modified according to the old system used prior to the advent of the Modification Assistant must be manually maintained after an upgrade has been run.

Use transactions SPDD and SPAU during an upgrade to select these objects and modify them manually.

• Transaction SPDD allows you to adjust modifications to ABAP Dictionary objects during an upgrade.

• Transaction SPAU allows you to adjust programs, function modules, screens, interfaces, documentation, and text elements after an upgrade.

Additional information about the upgrade procedure can be found in:

Upgrading from Release 4.5A or Less

Modifications Made by Several Different People

Adjusting Other SAP Systems

Upgrading the Development System

Upgrading the Production System

Handling Change Requests During Modification Adjustment

Choosing a Change Request for Modifications

Local and Transportable Change Requests

Releasing Tasks at the End of Modification Adjustment

Choosing a Change Request to Transfer Modification Adjustments to Other SAP Systems

Notes (Troubleshooting)

Set color to system

1. Alt+F12 -> New Visual Design
Select the General tab. In the Active Theme (top left) window, make sure select System ENJOY. Click on Apply.

From sdn forum, maybe you can find a post said select system dependent, but i test should be select enjoy.

2. Click on the color setting tab or Alt+F12 -> Set Color to System
That will let you choose the color.

ITS WEBGUI in ECC6.0

Copy from: https://www.sdn.sap.com/irj/sdn/thread?threadID=303806

How to disable the User menu?

use sm30 tcode and change the table ssm_cust and change the parameter:

ALL_USER_MENUS_OFF

NO (default), YES or 'X' - Do not Display User Menu on Easy Access Screen (Note 380029)

CUSTOMER_MENU_OFF NO (default), YES or 'X' - Do Not Display Customer Menu on Easy Access Screen (Note 380029)

SAP_MENU_OFF NO (default), YES or 'X' - Do not Display the SAP Menu on the Easy Access Screen (Note 380029)

The other method is use sm30 tcode and change the table users_ssm to determine whether or notusers are allowed to switch between the SAP menu and their user menus.

Apply:

If a user ask you based on the role menus, you can not find any key.

If a user has several roles assigned, then some functions can be repeated in different parts of the role-based user menu.

Types of SAP Support Packages

Get from sap website.

Types of Support Packages

SAP delivers various types of program corrections with Support Packages as part of the software maintenance. Support Packages automatically correct a whole range of errors by downloading corrections into the SAP System. Two categories of Support Packages are available: ABAP Support Packages and Java Support Packages.

ABAP Support Packages

ABAP Support Packages contain corrections and updates for the ABAP components of the SAP system that were performed up to a certain point in time. Each Support Package is based on the previous one. If you want to import Support Package 10, for example, you must also import all previous Support Packages (1-9). To import ABAP Support Packages, you use the Support Package Manager.

All SAP R/3 Releases up to 4.5 are supported by corrections in the form of SAP R/3 Support Packages (formerly Hot Packages) or SAP R/3 HR Support Packages (formerly Legal Change Patches HR) until the end of their maintenance period.

SAP HR Support Packages contain corrections or adjustments due to legal changes for HR functions in SAP R/3. Up to SAP R/3 3.1I (and SAP R/3 4.0B up to LCP HR 53), SAP R/3 HR Support Packages contain corrections for SAP HR as well as the same set of corrections as SAP R/3 Support Packages. As of SAP R/3 4.5B (and SAP R/3 4.0B as of LCP HR 54), the content of the SAP R/3 Support Packages is no longer included in SAP HR Support Packages.

Component Support Packages

ABAP Support Packages are available for all components of mySAP.com, such as SAP Basis, SAP BW, or SAP Advanced Planner and Optimizer (SAP Basis, SAP BW, SAP APO Support Packages).

Add-On Support Packages

Corrections for add-ons, such as industry solutions, strategic development projects or SAP R/3 Plug-Ins, are provided in Add-On Support Packages. For more information on Add-On Support Packages, refer to SAP Note 160168 .

Conflict Resolution Transports (CRT)

CRTs adapt Component Support Packages to add-ons, such as industry solutions (IS components). If an add-on modifies objects in the SAP R/3 Core components, conflicts with SAP R/3 Core Support Packages may arise. A CRT resolves these conflicts. For more information on CRTs, refer to SAP Note 53902.

SPAM/SAINT Updates

SPAM/SAINT Updates extend the functions of the Support Package Manager (Transaction SPAM) and the SAP Add-On Installation Tool (Transaction SAINT).

Java Support Packages

Java Support Packages contain corrections and updates to Java components. They are delivered in the form of Software Component Archives (SCA). Unlike ABAP Support Packages, Java Support Packages always contain the complete version of the Development Components for the application. You therefore need to apply the latest Support Package only. If there are dependencies with other Java Support Packages, these are specified in an SAP Note.

As of SAP NetWeaver 2004s, you can apply Java Support Packages using the Java Support Package Manager (JSPM). For more information on JSPM, refer to the quick link /JSPM.

Java Support Packages are available as of SAP Web Application Server 6.20. For SAP Web Application Server 6.20 and 6.40, you apply Java Support Packages using the Software Deployment Manager (SDM). The SDM is contained in the SAP Web AS installation as of 6.20. For more information on SDM, refer to SAP Note 544244.

Support Package Stacks

A Support Package Stack is a set of Support Packages and patches for a specific product version that must be used in the specific combination.

For more information on Support Package Stacks, refer to the quick link /sp-stacks.

All corrective software packages, for SAP NetWeaver 2004s and SAP Business Suite 2005 and beyond that are delivered after April 2nd, 2007 will ONLY be available via SAP Solution Manager's Maintenance Optimizer.

login/password_expiration_time

4月份因为内部Audit的原因，加强了Security,新增（更改）了部份login parameter
login/password_expiration_time 60
login/no_automatic_user_sapstar 0
login/failed_user_auto_unlock 1

特别要指出没有login/password_expiration_time在profile时SAP取的defaul value是0，当添加后从0改成60然后重启生效，哪么所有Dialog用户被要求改密码；这个参数第一次的从0到60的更改的副作用有点象reset "almost" users'password;而这里为什么说almost user,是因为第一次是0到60，估计绝对大部分用户的password都不符合SAP password policy,所以这里他们都要更改密码，而更改过后，如果你再次改login/password_expiration_time，用户就不要再次更改了，直到password_expiration_time到期。所以有Admin异想天开用它来更新password policy（象密码长度、字符变动）,的确是好注意！我试过从profile再次删掉login/password_expiration_time,让SAP取默认值0，重启生效，同一用户不必更改密码；下一测试添加login/password_expiration_time＝60重启生效，同一用户同样不必更改密码；下一测试更改login/password_expiration_time＝120，同一用户同样不必更改密码；具体测试过程如下

Profile Active value Change password
N/A 0
login/password_expiration_time 60 YES
login/password_expiration_time 120 NO
delete the parameter from profile 0 NO
login/password_expiration_time 20 NO
login/password_expiration_time 60 NO
login/password_expiration_time 120 NO



但如果要避免更改密码，似乎没什么好办法，但也不没有方法，只是不是针对所有用户：
1，前面有提到更改密码只涉及Dialog用户，所以可以将有需要的用户（如大BOSS）变成Service用户；
2，in the table USR02, just set a date far in the future for the field BCDA1 (password last change). For example, if you want to set it so user SMITH does not have to change his password until 2010, you can use the following SQL script : update USR02 set BCDA1 = '20101231' where BNAME='SMITH' Just replace the values for BCDA1 and BNAME with your own values ! This script is for MS SQL Server + R/3 46B and 46C, but the syntax should not be very different for other database systems and R/3 versions.

但从国内的企业应用来看，60天似乎太短了，下一阶段要设成120天；在ECC6 IDES测试过，从60到120，用户不需要更改密码。

相关的表：USR02

另外要说明的是login/failed_user_auto_unlock，明显的是一鸡肋，用户一但发现因密码错误不能登录，他就会不停的试不确定的密码直至被锁，而被锁后，根本不会等第二天自动解锁，他们会直接找Admin.

金山词霸企业版VS谷歌版

不在企业做的朋友多不知道金山词霸居然还有企业版，公司现在一直在用，本着短小精干的精神，想试用一下才20MB大小的谷歌版，结果问题来了！

在PDF文档里居然无法取词，而企业版怎么试也没问题。是跟企业版有冲实呢？还是卖给谷歌一个半残品呢？这是一个謎啊！如果是后者，哪金山太雷人了

slove ‘Lock table overflow' process

出错情况：

用户报称修改QT时出错：‘Lock table overflow';

...

检查日志SM21,

Internal lock administration error
> EqSetCluster(); rtc=16 enxxmenq1905
Lock table overflow
Internal lock administration error
> EqSetCluster(); rtc=16 enxxmenq1905
Lock table overflow
Internal lock administration error
> EqSetCluster(); rtc=16 enxxmenq1905
Lock table overflow
Internal lock administration error

详细日志，

An overflow of the lock table occurred when you were setting the loc
The lock table consists of several individual tables each of which
can overflow individually. The subsequent line indicates which of th
tables has overflowed.
The lock table is contained in the memory of the lock server
(-> enqueue server). Only the total size can be set. This is set
with the profile parameter "enque/table_size" in the instance
profile of the central locking server. Its value is entered in KB.
The setting only becomes effective when the system is restarted.
The default size of the lock table is 4096 KB.
Please note that when increasing the size of the lock table, a disk
requirement of approx. 1.5 x the size of the lock table is necessary
in each case in the global directory for the reporting file and in
the log directory for the backup file.
Before you increase the lock table after an overflow, you should
always check whether the overflow resulted from a program error
or an operating error.

检查profile parameter "enque/table_size"　with RZ10,

Short description: Size of lock table

by this parameter:

Parameter description :

This parameter defines the size of the lock table that is held in
main memory by the enqueue server. The lock table contains all of
the information about which locks are currently held, and by whom.

The size of the lock table limits the maximum number of lock
entries, the maximum number of elementary lock names, and the
maximum number of lock owners.
In the case of an overflow of the lock table, you should check
whether the update server is working correctly, since the lock table
can grow in size very quickly if updates stop. If the cause is not
update problems, you can use this parameter to increase the size of
the lock table.
The Computing Center Management System (CCMS) constantly monitors
the status of the lock table, and issues warnings if the free space
runs short.

The Computing Center Management System (CCMS) constantly monitors
the status of the lock table, and issues warnings if the free space
runs short.
You can view the fill level of the lock tables using the statistics
functions of lock management (transaction SM12 -> Extras ->
Statistics).

实施时考虑过公司的运行情况，将实际大小设成10MB，

enque/table_size = 10000

check LOCK status with SM12,

发现total locks居然达到8K有余，Nr_of_Locks: 8701,有异于平时系统正常运行状态，而绝大部分是一个用户锁定的；

查看用户进程SM50,确认用户在运行CORUAFFW，询问用户运行Tcode：COGI,确认用户在做物料替换时中断了会话，从而导致系统锁定的大批物料而没有释放。

解决方案：end session in SM50.

How to search sofeware which not belong to u?

Sometimes, we want to download the other software which not My Company's Application Components

like as other database of IDES, old version support package.

SAP Software Distribution Center

Search in SAP Software Distribution Center

Advanced Search

Change Search Method to All terms, default Context is restriction, change to no restriction, Max Search Result to 1000, select all the search object object, You will find you want to search. Good luck!

SAP最新的“挤奶”行动

Tcode: USMM

背景资料：

1、业内人士称SAP北亚区高管曾辱骂中国客户

...

太多了，选一则贴上，这里要注意的是：

为了达成这一战略目标，纪秉盟将10亿元任务分解到四个季度，即第一季度的“绝对值指标”是12％、第二季度23％、第三季度是20％，第四季度是45％。

现在是第三季，也有会计说法是第二季，从朋友，顾问，自身得到的体验是，SAP开始大范围的“挤奶”了，而且重点之一是从老客户哪里挤奶，还不能是纸质包装奶，必须是新鲜奶，有得忙了！

SQL error 2812: Could not find stored procedure.doc

起因：是在一台测试服务器上，安装了多个测试Instance，一次在安装Solution Manager时，将其覆盖在ERP上；

现象：一是登录时显示SAP菜单出错，报错START_CALL_SICK，Database inconsistency: Start Transaction SICK.但运行SICK还是出错，注意到"Can't execute sap_check_if_sick".但运行一些模块Tcode似乎没问题；

二是在激活DDIC object时出错，报错SQL error 2812 occured: Could not find stored procedure 'sap_get_object_type'.

设想：可能是错误的安装删除了SQL procedure

在现象二的帮助里，有The stored procedure must be created in the database. To do this, follow the instructions in SAP Note 460268.

Note Language: English Version: 1 Validity: Valid from 14.12.2001
Summary
Symptom
The following error message is displayed in the status bar or written to a
log file when executing a DDIC function:
SQL error 2812: Could not find stored procedure ...
More Terms
MSSPROCS
Cause and Prerequisites
As of Release 6.20, the access to the database for the return of system
catalog data is executed with stored procedures. These are called in
function modules of the SFMSS_SYSCAT group.
If such a stored procedure is missing, the above SQL Server error message
is issued. It is then transferred to the status bar or the log via the
functions modules.
Solution
Solution
Proceed as follows:
o Execute the MSSPROCS report in SE38.
o Choose the version of your SQL Server as the Database Release value
and confirm with Enter.
o Select the missing stored procedure in the table control.
o Choose "Start". A log must be displayed notifying you that the
procedure was successfully executed.

解决:按照Note上的指引，执行MSSPROCS，选择SQL版本9.0(SQL2000是8.0,SQL2005是9.0),程序已自动选择应安装的组件，点开始运行，很快就运行完提示一系列的脚本已执行。

问题解决。

About SAP installation problem

看过很多同学在述说自己在安装IDES有多辛苦，过程有多复杂，时间之长，机器之慢，说起来臭婆娘的哪块布要长之

装过数十次，总结一下：

1，内存，要高；

　见过好多同学用1GB内存在哪折腾。没错，我还用过512MB装成功过，哪是4.6B的sql版本；但要知道必先利其器这话，SAP说到底就是个数据库的应用软件，没个大内存你好意思出手！SAP官方安装文档一出口就是标准配置2GB，这话跟微软说的没两样，看看就算了，千万别信！4GB吧，越多越好越快越没问题，还会帮你省点钱

2，硬盘，要大；

　光源文件就10几个GB，放在网络盘你还装不上，不在本地盘不行，ECC6装完就80GB了，你不搞个250GB都不好出去见人！有条件搞个RAID1，IDES容易坏硬盘，尤其是内存少的机器，我都坏三还是四块了

3，网卡，

　杨生哪写着虚拟网卡，哪是因为人家哪时候穷，买不起网卡，新来的就别照本全搬了

4，JAVA，

　千万别想着最新版本，SAP让你用哪个老不死的就是因为它就是传说中的稳定版

5，版本，

　个人感觉4.6D的ORACLE版好点，一来是ORACLE8,让你学点数据库的知识，不是贬低MSSQL，其实SQL2005比ORACLE10或11G性能上不差，可以说有过之而无不及，当然是Windows IA的平台上，Unix就不要比了，SQL没这版本啊，只是MSSQL都是图形界面，让你无从下手之余人变懒了；二是容量少，60GB拿下；三者，SAP什么版本其实根子还是R/3,你就是最新搞到ECC6R3对basis还是没什么新意，不就多JAVA，不就更容易安装，切，硬件需求之高，一点不利普及

About login/failed_user_auto_unlock work or not

记录在这里不是简单的说将login/failed_user_auto_unlock=1后，再reboot SAP这种问题，而是说到底这个para.生效了没有，有没有在midnight自动解锁用户？

整个persidure是：

1，用户因为输错密码太多（login/fails_to_user_lock）被封锁；

　　　这里算第一天，按SAP　OSS说明，这天的Midnight,这个用户应该被解锁

2，Midnight，用户解锁；

3，用户用正确的密码登录or错密码；

哪为什么会有这篇废话？而且网上还有哪么多人对这个wonder　and puzzle？

究根道底就是虽然用户解锁了，只要用户还没用正确的密码再次尝试登录前，作为管理员的你在SU01之类的程序看这个用户时，你会发现这个用户的状态居然是Password logon not allowed(too many failed logons),其实只需要用户的一次正确登录，这个状态就会清零（这就是cause of puzzle)；如果用户再次用了错密码，要么找你，要么等一天再试，你说用户会选什么？

How do you pronounce IT?

The following pronunciations are based on an approximation of U.S. English. An understanding of U.S. English may be needed to understand how to interpret a particular pronunciation rendering. If you know of a term in information technology that people often stumble over or mispronounce, please send us an e-mail and let us know!

Note: In writing, many style editors prefer that the spelled-out version of a term should be used in the first written occurrence of a term in an article (for example, "wireless local area network (WLAN)" instead of just "WLAN" or even "wireless LAN"). Thereafter, the abbreviated form can be used.

In pronouncing an abbreviation or reading it aloud, the pronouncer may want to convert the abbreviation into the long form for the understanding of a listener (for example, reading "wireless LAN" for "WLAN").

To update the SAP kernel

1. create a folder to store the kernel SAR file

2. copy the SAR file to the new folder

3. run sapcar -xvf SAPEXEDB* (database dependent)

4. run sapcar -xvf SAPEXE_* (database independent)

Step 3 and 4 are to extract the kernel

5. stop SAP console

6. stop SAP service

7. stop SAPoscol service

8. remove the SAPEXEDB___.SAR and SAPEXE__.SAR from the new kernel folder

9. copy everything from the new kernel folder to E:usrsap<SID>DVEBMGS00exe

10. copy everything from the new kernel folder to E:usrsapE05SYSexeucIA64

11. start SAPOSCOL and SAP SERvice

12. start SAP console

SAP server hung by "ERROR => New Process with the same PID".

I noticed the server was hung by unkown reason on 08:40AM today morning, so I decided to restart sap to solve this case ASAP. After that, I looked back the database log, system log and the other related files to find what happen, and found the clew in the dispatcher's trace files, "ERROR => New Process with the same PID". This error happened on almost dispatchers, so there was no dispatcher to handle user's session, then we got the server was hung at that time.

I Thu Jun 05 08:56:01 2008
I *** ERROR => New Process with the same PID (2732, Aktion: 1
[semnt.c 1920]
I *** ERROR => New Process with the same PID (7076, Aktion: 1
[semnt.c 1920]
I *** ERROR => New Process with the same PID (6056, Aktion: 1
[semnt.c 1920]
I *** ERROR => New Process with the same PID (7076, Aktion: 1
[semnt.c 1920]
I *** ERROR => New Process with the same PID (4112, Aktion: 1
[semnt.c 1920]
I
I Thu Jun 05 08:56:02 2008
I *** ERROR => New Process with the same PID (948, Aktion: 1
[semnt.c 1920]
I *** ERROR => New Process with the same PID (3900, Aktion: 1
[semnt.c 1920]
I *** ERROR => New Process with the same PID (6032, Aktion: 1
[semnt.c 1920]
I *** ERROR => New Process with the same PID (3900, Aktion: 1
[semnt.c 1920]
I *** ERROR => New Process with the same PID (3900, Aktion: 1
[semnt.c 1920]

I checked SAP's note with the key word, and found a note named "Note 920530 - Error Message in Trace: New Process with the same PID ", this note is valid since 07.08.2007, and maybe we should consider to apply the last kernel patch on the server.

Error 1053: The service did not respond to the start or control request in timely fashion

BW测试机在更新Symantec后重启，发现SAP<SID>_00和SAP<SID>_01出错不能启动，

Error 1053: The service did not respond to the start or control request in timely fashion

尝试手动在command命令行里启动相应的sapstartsrv.exe文件，报错Couldn't found mfc71u.dll，对这个文件有点眼熟，在SAP/note查找，发现一篇NOTE提到这个文件， Note 684106 - Microsoft runtime DLLs

打上DLL补丁，重启后，问题解决。

但这个CASE知其然，不知其所以然，这个DLL本应在安装时自成动打上去的，但为何丢失？查看symantec的LOG也找不到相应的DLL被删的记录。

Update on 2008/08/05

今天在一部测试机子装了数个IDES，由于有一个版本问题没装上，后来发现SAPOSCOL服务不能正常启动了，报错：

Error 1053: The service did not respond to the start or control request in timely fashion

初以为按以前的方面可解决，但不奏效。

尝试手动时，发现服务的命令行居然是：

G:usrsapC11sysexerunSAPSTARTSRV.EXE pf=G:usrsapC11sysprofileSAPOSCOL.EXE service

直接在注册表中regedit中改成：

G:usrsapC11sysexerunSAPOSCOL.EXE service

即可。

其实解决此类错误，手动运行，得知其出错原因就是踏上通往成功的大道。

TMS request queue restore

公司SAP架构以前是二层，DEV－＞PRD；现在增加了QAS，但有一个小小的困扰就是request queue在QAS和PRD之间是不一样的，QAS只保存了只建立后的request import list，实质上QAS是PRD的system copy版，所以有必要在QAS恢复完整的request import list，有利于版本比较。

实质上，request import list就是OS上的一个＜SID＞文件，保存在usrsapmnttransbuffer。

将PRD的request list文件拷贝过来QAS，即可。在QAS系统上STMS刷新QUEUE就会发现所有已导入的request都已列表出来了。

BTW，有朋友倾向于为美观计定期清除request queue,说是一打开就是成千request,SAP默认是按号码大小顺序排序，找最新的request要按PAGEDOWN都要好久，或者按反序排序，但无论如何，OS备份还是要做的！

备份，有备无患！

Finding SAP table names and descriptions

To get a list of SAP table names and descriptions, browse table DD02T in SE16 or run the following SQL in sqlplus:

Code

Select tabname, ddtext from sapr3.dd02t where ddlanguage = 'E'

SAPGUI for Java Connect setting

conn=/H/(hostname)/S/32(S.No.)

Daily Cleaning background Jobs

Login Client: 000

Login ID: DDIC

if you have a SAP release 4.7 or higher then use transaction sm36 ->

standard jobs button -> default scheduling.
This will create all the needed housekeeping jobs you need.

Or, with transaction ssaa, Overall vien, Execute,

Installation Follow-Up Work, Basis Settings, Scheduling Necessary Background Jobs

Most consultants just schedule the STANDARD jobs with SM37 (or SSAA), without checking any related SAPnotes.

See below latest overview.

Best regards,
Stefan

### R/3 JOB OVERVIEW

Job name : SAP_REORG_JOBS
Program : RSBTCDEL2
Variant : Yes
Parameters variant : 7 days (good value, but check in company)
Frequency : Daily
Description : Delete batch job logs
WARNING: Do not schedule job with program RSBTCDEL; much more jobs are deleted; see note 837691.

Job name : SAP_REORG_SPOOL
Program : RSPO1041
Variant : Yes
Parameters variant : 7 days (good value, but check in company)
Frequency : Daily
Description : Delete old spool requests.

Job name : SAP_SPOOL_CONSISTENCY_CHECK
Program : RSPO1043
Variant : Yes
Parameters variant : 7 days (good value, but check in company)
Frequency : Daily
Description : Spool data (TemSe) consistency check.
NOTE: Job must be scheduled an hour after SAP_REORG_SPOOL.

Job name : SAP_REORG_BATCHINPUT_<CLIENT>
Program : RSBDCREO
Variant : Yes
Parameters variant : 5 days (good value, but check in company)
Frequency : Daily
Description : Delete successfully processed BIM sessions and their logs from the TEMSE table.
WARNING: Job must be scheduled when no other jobs are running.
NOTE: Job must be scheduled for all customer clients (meaning each individual client).

Job name : SAP_REORG_ABAPDUMPS
Program : RSSNAPDL
Variant : Yes
Parameters variant : 30000 / 500
Frequency : Daily
Description : Delete short dumps from SNAP table.

Job name : SAP_REORG_JOBSTATISTIC
Program : RSBPSTDE
Variant : Yes
Parameters variant : 30 days
Frequency : Monthly
Description : Delete runtime statistics.

Job name : SAP_COLLECTOR_FOR JOBSTATISTIC
Program : RSBPCOLL
Variant : No
Parameters variant :
Frequency : Daily
Description : CCMS: Collector for Background Job Run-time Statistics

Job name : SAP_REORG_PRIPARAMS
Program : RSBTCPRIDEL
Variant : No
Parameters variant :
Frequency : Monthly
Description : Reorganization of Print Parameters for Background Jobs (see note 307970).

Job name : SAP_REORG_XMILOG
Program : RSXMILOGREORG
Variant : Yes
Parameters variant : 7 days
Frequency : Weekly
Description : Reorganization of XMI interface loggings.

Job name : SAP_CCMS_MONI_BATCH_DP
Program : RSAL_BATCH_TOOL_DISPATCHING
Variant : No
Parameters variant :
Frequency : Hourly
Description : Starts CCMS Method Dispatching in the background.

Job name : SAP_UPDATE_RECORDS
Program : RSM13002
Variant :
Parameters variant :
Frequency :
Description :
WARNING: Do not schedule this job !!!
Following parameter is set: rdisp/vb_delete_after_execution=1

Or Notes 16083

Generate SolutionManager key report

*&---------------------------------------------------------------------*
*& Report ZSLMKEY
*&
*&---------------------------------------------------------------------*
*&
*&
*&---------------------------------------------------------------------*

REPORT ZSLMKEY.

types: begin of dswpclientkey,
INSTNO type num10,
DBID(3),
BUNDLE_ID(8),
SERVICE_KEY(40),
end of dswpclientkey.
*data: dswpclientkey_w type standard table of dswpclientkey.
DATA: P_VALUE(10),
P_INSTNO(10).

PARAMETERS: P_SID(3),
P_SYSNO(2),
P_SERVER(15).

START-OF-SELECTION.
PERFORM GET_SP_VALUE USING P_SID
P_SYSNO
P_SERVER
P_INSTNO
CHANGING P_VALUE.

END-OF-SELECTION.
WRITE P_VALUE.
*&---------------------------------------------------------------------*
*& Form get_sp_value
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
* -->P_PF_SID text
* -->P_PF_SYSNO text
* -->P_PF_SERVER text
* <--P_PF_VALUE text
*----------------------------------------------------------------------*
FORM get_sp_value USING P_PF_SID
P_PF_SYSNO
P_PF_SERVER
P_PF_INSTNO
CHANGING P_PF_VALUE.

CONSTANTS: lc_part_len TYPE i VALUE 5,
lc_pw_len TYPE i VALUE 10,
lc_allowed_chars(38) TYPE c VALUE
'-0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ_'.

data: lf_string(20) type c,
lf_key type i,
ls_key type dswpclientkey,
lf_part(lc_part_len) type c,
lf_finalf(lc_pw_len) type c,
lf_finalx type xstring,
lf_xbuffer type xstring,
lf_opf(10) type c,
lf_langu like sy-langu,
lf_subrc like sy-subrc,
lf_len type i,
lo_conv_to_x TYPE REF TO cl_abap_conv_out_ce.

clear: lf_string, lf_finalx, lf_opf.

concatenate p_pf_sid p_pf_sysno p_pf_server into lf_string.

* Large letters only
translate lf_string to upper case.

lf_langu = sy-langu.
SET LOCALE LANGUAGE 'E'.
lo_conv_to_x = cl_abap_conv_out_ce=>create( encoding = '1100' ).
lf_len = STRLEN( lf_string ).

IF lf_string(lf_len) CN lc_allowed_chars.
else.

* Fold the input string to a lc_part_len long string
WHILE lf_len > 0.
lf_part = lf_string(lc_part_len).
SHIFT lf_string BY lc_part_len PLACES.
lf_len = STRLEN( lf_string ).
CALL METHOD lo_conv_to_x->reset.
CALL METHOD lo_conv_to_x->write( data = lf_part n = -1 ).
lf_xbuffer = lo_conv_to_x->get_buffer( ).
lf_finalx = lf_finalx BIT-XOR lf_xbuffer.
ENDWHILE.

lf_key = 12.

PERFORM scramble USING lf_finalx
lf_key
lc_part_len
CHANGING lf_finalf
lf_subrc.

if not lf_finalf is initial.
p_pf_value = lf_finalf.
ls_key-dbid = p_pf_sid.
ls_key-instno = p_pf_instno.
ls_key-bundle_id = 'SM_KEY'.
ls_key-service_key = lf_finalf.
if not p_pf_instno is initial.
* insert dswpclientkey_w from ls_key.
if sy-subrc <> 0.
* update dswpclientkey_w from ls_key.
endif.
endif.
else.
clear p_pf_value.
endif.
endif.
ENDFORM. " get_sp_value
*&---------------------------------------------------------------------*
*& Form scramble
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
* -->P_LF_FINALX text
* -->P_LF_KEY text
* -->P_LC_PART_LEN text
* <--P_LF_finalf text
* <--P_LF_SUBRC text
*----------------------------------------------------------------------*
FORM scramble USING iv_xstring TYPE xstring
iv_key TYPE i
iv_src_len TYPE i
CHANGING lf_finalf
lf_subrc LIKE sy-subrc.

CONSTANTS: lc_max_len TYPE i VALUE 20,
lc_mask(4) TYPE x VALUE '0000003F',
lc_random(64) TYPE x VALUE
'F0ED53B83244F1F876C67959FD4F13A2' &
'C15195EC5483C234774943A27DE26596' &
'5E5398789A17A33CD383A8B829FBDCA5' &
'55D702778413ACDDF9B83116610E6DFA'.

DATA: lv_key_index(4) TYPE x,
lv_rand_index(4) TYPE x,
lv_xkey(4) TYPE x,
lv_xkey_shl_1(4) TYPE x,
lv_xkey_shr_5(4) TYPE x,
lv_scramble_byte TYPE x,
lv_dest(lc_max_len) TYPE x,
lv_index TYPE i,
lv_len TYPE i.

CLEAR lf_subrc.

IF iv_src_len EQ 0. EXIT. ENDIF.
lv_len = XSTRLEN( iv_xstring ).
IF iv_src_len GT lc_max_len OR
iv_src_len GT lv_len.
lf_subrc = 2.
EXIT.
ENDIF.

lv_xkey = iv_key.
lv_xkey_shl_1 = iv_key * 2.
lv_xkey_shr_5 = iv_key DIV 32.
lv_rand_index = lv_xkey BIT-XOR lv_xkey_shr_5 BIT-XOR lv_xkey_shl_1.
lv_rand_index = lv_rand_index BIT-AND lc_mask.

lv_index = 0.
DO iv_src_len TIMES.
CATCH SYSTEM-EXCEPTIONS compute_int_times_overflow = 1.
lv_key_index = ( iv_key * lv_index * lv_index ) - lv_index.
ENDCATCH.
IF sy-subrc <> 0.
lf_subrc = 1.
EXIT.
ENDIF.
lv_scramble_byte = lc_random+lv_rand_index(1) BIT-XOR
lv_key_index+3(1).
lv_dest+lv_index(1) = iv_xstring+lv_index(1) BIT-XOR
lv_scramble_byte.
lv_index = lv_index + 1.
lv_rand_index = lv_rand_index + 1.
lv_rand_index = lv_rand_index BIT-AND lc_mask.
ENDDO.
IF lf_subrc <> 0.
EXIT.
ENDIF.

WRITE lv_dest(iv_src_len) TO lf_finalf.

ENDFORM. " scramble

The client is currently locked against logon.

During the remote client copy with profile SAP_USER, just saw the copy files was 90 of 90, so i considered the copy finished and tried to restart the instance caused by profile modified. But When I restarted and tried to logon, the system responding message with "The client is currently locked against logon" .

Logon client 000 with DDIC, run SCC4, the system remind the clinet 004 have lock due to copy failed.

Delete the lock and then logon client 004 and continue the remont client copy, wait the statistics said successful.

SAPOSS connection

Tcode: SM59

SAPOSS connecttion failled by conection password wrong.

give user ”OSS_RFC” password “CPIC“.

Install SAP patch and support package

SAP EarlyWatch Alert报告出来了，说是要打补丁云云。

Before we can deliver any services, the latest version of the SAP Service tools must be available in your system.
The last run of report RTCCTOOL was 11.04.2008. During the check, the tool detected SAP Notes that were rated RED or YELLOW.

Recommendation:
Run report RTCCTOOL (review SAP Note 69455) and implement the recommendations.

1. [Note 69455 ] Addon ST-A/PI 01K_ECC600
Description "Servicetools for Applications Plug-In" for ERP 2005 / ECC 6.00
Implementation From http://service.sap.com/supporttools download the addon file
ST-A/PI 01K_ECC600. Upload the file to transaction SAINT 'Installation
package > Load packages > From Frontend' and install as per note 69455 .
Then restart report RTCCTOOL and choose 'List->Refresh from SAPNet'.

2. Note 539977
Description Addon supportpackage level 6 for ST-PI 2005_1_700 for 7.00
[patches up to level 6 for Basis tools for services]
Implementation Open http://service.sap.com/supporttools-> ST-PI 2005_1_700 ->Supportpk.
Add patch SAPKITLQI6 (and predecessors if not yet implemented) to
download basket. Release basket via Maintenance optimizer. Upload from
frontend into transaction SPAM, define a queue and import the queue.

第一个patch可以在service.sap.com下载，但第二个supoort pachage就需要Solution manager下载了，只能靠朋友发过来了

要用的Tcode:

SE38-> RTCCTOOL

SAINST

SPAM

Migrate SAP to ne disk group

Moving the tempdb database(SQL server)

Moving the tempdb database

use tempdb
go
sp_helpfile
go

use master
go
Alter database tempdb modify file (name = tempdev, filename = 'E:Sqldatatempdb.mdf')
go
Alter database tempdb modify file (name = templog, filename = 'E:Sqldatatemplog.ldf')
go

Why the SAP* password is not PASS?

please check if the SAP parameter "login/no_automatic_user_sapstar"is set to 0

Parameter : login/no_automatic_user_sapstar



Short description: Control of the automatic login user SAP*



Parameter description :

If the user master record belonging to user SAP* is deleted,
it is possible to re-log on with SAP* and initial password PASS.
SAP* then has the following attributes:

- The user has all authorization, as authorization checks
cannot be executed.

- You cannot change the standard password PASS.

Using profile parameter login/no_automatic_user_sapstar,
you can deactivate the special attributes of SAP*.



Work area: Logon

Unit :



Default value: 1



Who is permitted to make changes: The customer



Limitations for operating systems: None



Limitations for database systems: None



Other Parameters Affected or Dependent:

The profile parameter login/no_automatic_user_sap* supported in
SAP Releases 3.0 and 3.1 no longer have any effect.

is still only supported in Release 3.1.

Valid entries, formats, areas : 0, 1

0: Automatic user SAP* is permitted
1: Automatic user SAP* is deactivated


1: Automatic user SAP* is deactivated

Who is the Last Change?

事情的由来，是同事要将传输Z*表，自然要将local object改成transport package,但在SE80中自己名下死活找不到这张表，但在SE11中Attributes中的Last changed on/by的确是同事的名字...

后来发现，在SE11的Technical Setting中Last Change另有其人...看来这里其实指的是Owener。

Copy client schedule

You want to use parallel processes for a client copy.

Summary

Header Data

Affected Releases

SAPOSCOL not running (Shared memory not available)

Run ST06,

SAPOSCOL not running (Shared memory not available)

Check what happen, because during I uninstall the other instance D01, but the SAPOSCOL service was deleted unguarded. So try to reinstall the service.

The “ntscmgr.exe” program located in the Exe -> Run directory can be used to reinstall the SAPOSCOL as a service.

Execute the following command:

ntscmgr.exe install SAPOsCol -b saposcol.exe –p

It is OK now.

The SQL Server (MSSQLSERVER) service terminated with service-specific error 1814 (0x716).

卸载SAP时将TEMPDB文件夹也给删除了，结果SQL server service启动失败，报错The SQL Server (MSSQLSERVER) service terminated with service-specific error 1814 (0x716).

SQL server每资重启都会重建TEMPDB，所以只要在原来的路径上重建TEMPDB文件夹即可。

修改SAP登录界面

T-code: se61,
data_element: ZLOGIN_SCREEN_INFO
document class: General Text
then choose "create", you can input whatever you want. 查看全文

Hotfix for IA64

性能方面的原因，要在RX3600/6600上打IA64 hotfix,　但是这两个hotfix是还没公开发行的版本，所以用了点笨方法来打；

1，系统config还是要保存的，用的是HP的DP，虽然这样就可以打hotfix了，但万一失败的话，还要重新安装系统和SAP，再加上恢复系统config才恢复到原来镜像，所以只能用下面的笨方法；

2，因为Windows 2003是装在RAID1的阵列中，打hotfix之前，将其中一个硬盘拔了出来，打完hotfix并测试没问题后，再插回去同步；这里原想着要是失败了，就用拔出来的硬盘启动也可以，结果用不着，一次成功！

下面还有两台服务器6600，先测试一周再进行

农村包围城市？

2008年2月19日，微软公司宣布将向全球大学 生免费赠送SQL Server 2005,Visual Studio 2005 and 2008, Windows Server Standard Edition, XNA Game Studio 2.0及其Expression的套装产品，此次赠送还将惠及到高中生 。

我有点好奇，DBA，尤其是中国的DBA，是在什么时候接触到数据库的？大学里学本数据库原理的哪种不算啊

象我就是半路出家，先做SA，再做DBA，在学校别说数据库，连电脑都。。。这说的有点过了，当年游戏还是玩过滴，五笔诗还是背过滴

但要说Microsoft这样做能在数据库市场上起到攻城略地，我有点怀疑，SQL server落后Oracle不是一两点啊，何况还有MySQL，DB2。。。这里特别是大一点点数据库，这一招不会是MySQL被收购的反应措施吧？Sun向来是免费惯了的

HP command view login "Insufficient privileges" problem

HP command view only login sucessfully on one manage server, the "Insufficient privileges" happened on the second server. 查看全文

数据库虚拟化——这样做值吗？

今天在INFOQ上看到一篇＜＜数据库虚拟化——这样做值吗？＞＞（英文版），想起二年前做过的类似测试...

当时公司被美国大头收购，总部测试Lab连接美国的服务器正是用一台IBM服务器虚拟了FS，DNS，DHCP，IA数台，整个IT部门兴起了虚拟化的测试浪潮，美国也派人过来详加介绍美国本土是如何在每个节点用两台IBM服务器(鬼佬真是有钱，在国内我们都是买DELL）建起cluster架构，测试到数据库时，卡壳了！买了台DELL　PE6800来测试，当时SAP还没升级，ORACLE7.3.4＋WINNT4+SAP31H，ESX对NT4的支持差的要命，磁带机认不到，每台服务器只能用一个CPU，问题一堆堆

后来SAP升级选型，顾问过来摸底，来前说也有些公司实施过数据库虚拟化，来后发现我们的数据库如此之大，足足600GB，强烈建议用实体机，现在用了两台HP　RIX6600做cluster，何故？还是性能问题。

结论，哪是一篇好文章，值得参考。

ICNV- Append old change log into LXP database(PRD)

1, Backup LXP;
2, ICNV;
3, During the append period, consultant found the G drive had no free space for log file to extend, because bulk insert data would cause the log file size increase quickly, you can see the log file size was 197GB on 2008/02/16, so I decided to add more space(100GB) from SAN to keep the append procedure to finished after discuss with consultant. That means the server use the SAN sapce is 1.4TB now, we should consider this status highly if we want to do some action on SAN environment on future like as snapclone, VOL extend, SAN schema change, etc.
4, The change document records have been transferred to the production system on 0:20AM 17-Feb-08;
5, Backup LXP,
6, Shrink log file.

BTW, User complained SAP can not save and update, lick QT update and Material create during the icnv period. That's OK.

Where is Telnet in Vista/Longhorn beta builds?

Where is Telnet in Vista/Longhorn beta builds?

Telnet is now made an optional component in Vista and Longhorn Servers. This means if you type telnet in command shell, you will be out of luck.

Why have we done it so?

As time has passed, fewer users use telnet. Thus, to decrease the foot print as well as the attack surface, we decided to make it an optional component.

Great, now how do I get telnet client/server working again?

Vista -

Use software explorer or Click Start, Control Panel, Programs, and then Turn Windows Features on or off. In the list, scroll down and select Telnet Client. Click OK to start the installation.

How to change the password for win2003 via remote desktop

Start

Setting

windows security

Maximum No. Of SAP Session Per User

Maximum No. Of SAP Session Per User

安装服务器准备SAP升级的小问之IE6安装

因为要AntiVirus需要IE6的环境，而在安装IE 6时，出现下面的错误提示：
“以前的安装有尚未完成的操作，需要重新启动。建议在运行 Internet Explorer 安装程序之前重新启动计算机。现在安装程序将关闭。”
重启计算机后，还是出现的问题。

解决方法：
运行ie6setup.exe /q

SAP Uninstall 之误删测试数据库

事情的起由，是昨晚要删掉另一台测试服务器上的SAP数据库，然后删除所占的SAN空间，腾出空间来给生产库迁移至SAN环境。

假设有A、B服务器，A机有a数据库，B机有b数据库，而b数据库是由a数据库的盘直接snapclone出来的，包含了数据库文件和SAP配置文件！！！帮凶啊！而B机上的SAP是用System copy方法做出来的，usr里面包含了a和b的配置文件，我这里就是LXD和LXT，一字之差啊！

现在要删掉B机上的b数据库。

出错过程：要知道SAP Uninstall是根据profiles来确认要删除SAP和数据库的机器和位置，事后检讨，当时应该是一不小心，点了B机上a数数据库配置文件。

结果，删LXT变成LXD严重啊，LXD正在恢复中...

Update,1.1TB size 的LXD数据库用了将近16个小时才恢复到前一小时的镜像，但不能startup disk+work.exe，还得用system copy的方法，才恢复正常。

经验教训：

1，用system copy的方法装SAP，尤其是用snap clone来做的盘，记得将原SAP的配置文件删除掉；断绝错误之源；

2，SAP Uninstall时，最好是不选择drop database,事后手动在SQL　EM下手动drop；就算点错了profiles，数据库文件还在，system copy就回来了

3, 安装SAP，最好采用不同的SID，如果使用相当的SID安装SAP，则采用Localhost的安装方式；其实最好全部用Localhost的安装;

PDB文件的用途

在SAP　FTP上下载GUI710的PATCH，发现有一个PDB的文件，查了一下用途：

The SAP Service Marketplace contains, in addition to the actual Support Package file for the SAP GUI (for example, GUI610.EXE), another file with a "pdb" extension (for example, 610_PDB.EXE).
The PDB file is ONLY required when requested by SAP Support (it contains important debugging information for SAP GUI "crashes"). The OSS message issued with each problem contains more information on how to handle the PDB file.

执行程序为什么老是显示Compiling...

经理问，为什么开发的同事反映执行报表时老是显示Comiling...

开发同事仔细检查，发现许多程序执行时都显示Comiling...

问题找到我Basis这边,原因是这是一个刚升级的系统，还没有transport all the requests,所以没有执行SGEN而已

至于SGEN是做什么的？因为SAP启动后，系统会将没有用过的程序和对象都做compile,这是正常的ABAP系统的行为，而SGEN可以强行generate　ABAP程序，详细看下面的帮助,当然我们可以先做一次SGEN，到所有的程序都传输过来了，再做一次

恢复数据库

今天尝试恢复一个大小为650GB的SQL　7数据库，到一台DELL　PE6400的服务器上，恢复速度慢的令我不敢相信，到现在花了22小时才完成了589GB;

因为上一个星期同样的恢复到台HP　DL380上，才用了8小时，不过哪次用硬盘是在SAN上面，而且是Gigabytes的网速，而今天用的PE6400的网卡是100MB的，本机上的RAID的；

一句话，没有可比性！列出来只是好奇的心理，似乎网速是瓶颈？

Update: 2007/12/26 17:19 恢复完成

651733 MB 1422 min (27512 Mb/h)

今晚加通宵，SAP迁移到SAN环境

各位SAP系统用户，SAP系统将于2007-12-26 0:00AM至2007-12-26 10:00AM期间进行迁移项目，届时IT部将会对此作出特别安排；

1. SAP生产系统将会在2007-12-26 0:00AM至2007-12-26 08:00AM停止服务用于迁移项目；

2．20007-12-25 23:00PM的MPS后台作业将会取消，IT将会提前安排在2007-12-25 18:00运行MPS；请销售部门的同事注意，2007-12-25的截单时间是18:00PM !!!

固定打印格式

因为是针打，RONIX打印机，要用到特别的打印格式，可以用function 'GET_PRINT_PARAMETERS'

CALL FUNCTION 'GET_PRINT_PARAMETERS'
EXPORTING
line_size = 200
line_count = 90
destination = 'LOCL'
layout = 'Z_90_200'
new_list_id = 'X'
immediately = 'X'
expiration = 0
IMPORTING
out_parameters = print_parameters
valid = valid_flag.

EVA4000 Controller down

我们这里的EVA4000的配置是2D2C，早上例行检查发现有一个Controller坏了，一点显示没有，查日志也没发现原因，只有找HP support了，通知换一个。

这已是二个月来第二次出现故障了

Trans backup hang

平时几分钟就可以做完的Trans backup，现在做了1个多小时了！只好cancel device，等下一次Trans backup

Update, i already aborted the backup, then i found the log is showed "write failure on backup device". now i run trans backup normal.

十一长假害人不浅

说来也真是搞笑，早上居然有2个用户报称不能进入生产系统，查了半天，居然没这个用户...最后查清楚，用户自己记错了登录名字＜＿＞

Ctrete new role

人家放假，我来加班，平均4下键盘/秒，一边按键盘，一边擦活络油，一天下来才建好了10个ROLE，累死人啊

Update,周一老大问进度，建完了Composit role,User speciol role正建到D字头。

神秘失踪的Trans Log Backup

前面说过目前的备份是用HP Data Protector,版本是6.0，每天凌晨5点在线全备，中午12：30和下午17：30各进行一次Trans Log Backup。

这样的备份策略才刚设好两天，今天进行查看Internal Database->Session，发现这两天中午12：30执行的Trans Log Backup不翼而飞，好象从来就没执行过...但药品这两天下午17：30的TLB就备份完成了，78GB的LOG一次用了23分钟备份，另一次用了25GB（因为没有truncate log)。

我明明将这三个session设置在一个Backup Job里面，早上一次Full backup,中午和下午各一次Trans Log Backup。难道一个Backup Job里只能有一个Trans Log Backup session,而且会只执行最后一个TLB session？

百思不得其解，只有打HP800了...

另外，自己也重设了Schedule,早上一次全备，中午和下午各一次Trans Log Backup,这次清楚看到下一次Schedule就是中午12：30的TLB...等着吧，中午见分晓...

R1,

中午的哪次TLB哪是莫名就失踪了

R2，

但在HP论坛上找到一点资料可能有帮助，http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=787159，有人反映“It seems DP only does a trans backup of a database full backup, only when in the same schedule (trans after full).”就是说一个schedule里只可含一个Full Backup和一个Trans Log Backup,而我这里一个F，两个T...这位Rocky仁兄在哪儿感叹“puzzled...and still puzzled i am.”，大家何尝不是同病相怜啊，

与HP800讨论以后，她也觉得我这例子有点莫明其妙，没别的法子，建议另建Schedule来执行T backup Session;

建了两个Schedule，里面分别是12：30和17：30的Trans Log Backup Session.先放在周六日跑...

希望星期一出好结果吧！

R3,

周六日的测试还是让人不知所以然，我设在中午12：30PM的SESSION（下图椭圆内）还是没有执行；而与之相反，设在下午5：30PM的没有任何问题；
我在星期六下午2点进行检查，发现后尝试右键点这个SCHEDULE运行，可以运行，但反而是FULL　BACKUP（第二张图）；

R4,

从新设置了一个每小时一次Trans Backup的Schedule,这回到是生效了，每小时备份一次；

上周末设置了Auto Shrink，回来注意到了LOG从120GB降到5GB了，看来以后不用手动shrink;

经历过的备份和恢复

旧时的SAP数据库是Oracle7.3.4，做了archive log，备份软件是ARCserve，每次是offline全备。

恢复就是将这些备份恢原到另一张机做测试；

年前将Oracle转成SQL server，迁移测试时发现前工程师设置的archive log恢复应用不生效，原来是设置archivelog的文件名太长了和大小写的问题，这情况的archivelog与noarchivelog一样，汗一个！这么多年都没出过大事，真佩服前任和Oracle。也怪自己从来没做过archivelog的恢复

转到SQL server后，用的备份软件是HP Data Protector（DP），这样可以选择在线备份和离线备份了；因为公司的业务要求还没哪么高（就是7*24啦），现在是每天凌晨在线全备，周一开工哪天凌晨来一个offline full backup；

当然在升级这些日子来回来恢复镜像做测试，这些备份还是得到充分验证的；

离线备份做恢复一点问题没有，在线备份做恢复的话，则要先建好恢复的文件夹，不然...当然在线备分来做恢复，恢复时间哪个长啊，毕竟咱的数据库有700GB啊，末后升到SQL2005，嘿嘿1.2TB！有搞头！

为了更高的业务要求，昨天又设了两个Transation Log Backup, 一个在中午12：30，另一个在下午17：30，都是下班，这样最少也可以保证最多只丢4小时数据了，昨天第一次做Trans log backup,78GB，用了25分钟；还算可以接受。

更换主机光纤接口卡的故事

故事的起源是订购的DL380G5主机供应商下单时漏掉了哪块双通道的光纤接口卡（当然还有光纤和SPF也一起漏掉了），事急从权，供应商将他们的存货（当然是旧的）拿来顶着用。

拿来的存货包括扩充卡、两张QLOGIC的同型号的单通道光纤接口卡，外加一张EMX的的单通道光纤接口卡（细心的朋友可能注意到了我没有写EMX的型号，正是这张EMX卡惹的祸）

供应商第一次将两张QLOGIC安装好后，装驱动时发现怎么也找不到另一张QLOGIC卡，设备管理器里只有一张卡；没法子只好将哪张EMX卡装上去，装驱动，再到HP Command View EVA里设置好WWN，分配VDISK，一切正常，供应商的工程师也走人了。

接着安装数据库SQL server 7，居然蓝屏死机，凭着经验一一解决，总算将数据库装起来了，通知SAP顾问进行下一步的升级测试......

第二天...

第三天...

...

SAP顾问报料说，升级测试不是很顺利，大量读写的升级时不时出错，死机...

检查系统日志说是DISK错误，怀疑是SAN有问题，观察SAN的LOG没发现什么特别有用的信息，前面状态灯都是绿的，正常；绕到后面终于看到光张交换机上两条光纤的状态灯不一致；打HP800终于搞清楚状态灯显示所代表的信息，原来我们哪两条光纤的状态是，一条的带宽是4GB，另一条是2GB（就是哪张EMX卡），通是通，但我们是自动分配带宽的...两张卡带宽都不匹配，问题就出在这里，解决的方法很简单，将哪条带宽2GB的光纤拔下来，让所有数据流量走一条通道。

后文，订的双通道的光纤卡终于到货了，供应商的工程师安装上去，重启，自动装驱动，分配VDISK，但在驱盘管理器怎么也发现不了刚分配的VDISK，原来是没在HP Command View EVA里设置新的WWN，删掉旧的WWN，重设WWN，一切正常！

SQL server 7安装错误一例

在一台DELL　PE6600上远程终端方式安装SQL　server　7，安装过程最后config阶段出现错误（Setup failed to config server.)

后面查了一下MICROSOFT，SQL7是不能用远程终端方式安装的，只能本地安装；

SQL　2K和2005倒是可以用远程终端方式安装

DL380 G5电源烧了

早起本来是要打SQL7SP4和迁移TEMPDB的，但一早上发现机子死了，原来是电源烧了。 没有冗余电源，只好将开发库机子上的电源拆过来顶替用，当然任务也取消了，因为昨晚没备份就死了 HP服务答应6小时送过来。 立马给经理电话要订三台机子的冗余电源

用上SAN了，真快！

计划用SAN来作IMPORT的介质，来达到加速IMPORT的目的，用的是VRAID0+1，果然，不用18个小时就做完了600GB数据的IMPORT，原来LOCALDISK的IMPORT可是要35个小时的！

有空再整理一下整个SAN的架构

XCOPY的妙用

因为测试的原因，开发的同事要将新服务器的目录建的与源服务器一模一样，小小算一下，几百个。。。。。 XCOPY /T /E 可以将源路径的大大小小所有目录全部拷贝过去，哈哈，但文件不会。。。

做DBA,未算赢先计输

很快就要转MS SQL了，贴份error list

Errors 1 - 999
Error Severity Description
1 10 Version date of last upgrade: 10/11/90.
21 10 Warning: Fatal error %d occurred at %S_DATE. Note the error and time, and contact your system administrator.
102 15 Incorrect syntax near '%.*ls'.
103 15 The %S_MSG that starts with '%.*ls' is too long. Maximum length is %d.
104 15 ORDER BY items must appear in the select list if the statement contains a UNION operator.
105 15 Unclosed quotation mark before the character string '%.*ls'.
106 16 Too many table names in the query. The maximum allowable is %d.
107 15 The column prefix '%.*ls' does not match with a table name or alias name used in the query.
108 15 The ORDER BY position number %ld is out of range of the number of items in the select list.
109 15 There are more columns in the INSERT statement than values specified in the VALUES clause. The number of values in the VALUES clause must match the number of columns specified in the INSERT statement.
110 15 There are fewer columns in the INSERT statement than values specified in the VALUES clause. The number of values in the VALUES clause must match the number of columns specified in the INSERT statement.
111 15 '%ls' must be the first statement in a query batch.
112 15 Variables are not allowed in the %ls statement.
113 15 Missing end comment mark '*/'.
114 15 Browse mode is invalid for a statement that assigns values to a variable.
116 15 Only one expression can be specified in the select list when the subquery is not introduced with EXISTS.
117 15 The %S_MSG name '%.*ls' contains more than the maximum number of prefixes. The maximum is %d.
118 15 Only members of the sysadmin role can specify the %ls option for the %ls statement.
119 15 Must pass parameter number %d and subsequent parameters as '@name = value'. After the form '@name = value' has been used, all subsequent parameters must be passed in the form '@name = value'.
120 15 The select list for the INSERT statement contains fewer items than the insert list. The number of SELECT values must match the number of INSERT columns.
121 15 The select list for the INSERT statement contains more items than the insert list. The number of SELECT values must match the number of INSERT columns.
123 15 Batch/procedure exceeds maximum length of %d characters.
124 15 CREATE PROCEDURE contains no statements.
125 15 Case expressions may only be nested to level %d.
128 15 The name '%.*ls' is not permitted in this context. Only constants, expressions, or variables allowed here. Column names are not permitted.
129 15 Fillfactor %d is not a valid percentage; fillfactor must be between 1 and 100.
130 16 Cannot perform an aggregate function on an expression containing an aggregate or a subquery.
131 15 The size (%d) given to the %S_MSG '%.*ls' exceeds the maximum. The largest size allowed is %d.
132 15 The label '%.*ls' has already been declared. Label names must be unique within a query batch or stored procedure.
133 15 A GOTO statement references the label '%.*ls' but the label has not been declared.
134 15 The variable name '%.*ls' has already been declared. Variable names must be unique within a query batch or stored procedure.
135 15 Cannot use a BREAK statement outside the scope of a WHILE statement.
136 15 Cannot use a CONTINUE statement outside the scope of a WHILE statement.
137 15 Must declare the variable '%.*ls'.
138 15 Correlation clause in a subquery not permitted.
139 15 Cannot assign a default value to a local variable.
140 15 Can only use IF UPDATE within a CREATE TRIGGER statement.
141 15 A SELECT statement that assigns a value to a variable must not be combined with data-retrieval operations.
142 15 Incorrect syntax for definition of the '%ls' constraint.
143 15 A COMPUTE BY item was not found in the order by list. All expressions in the compute by list must also be present in the order by list.
144 15 Cannot use an aggregate or a subquery in an expression used for the group by list of a GROUP BY clause.
145 15 ORDER BY items must appear in the select list if SELECT DISTINCT is specified.
146 15 Could not allocate ancillary table for a subquery. Maximum number of tables in a query (%d) exceeded.
147 15 An aggregate may not appear in the WHERE clause unless it is in a subquery contained in a HAVING clause or a select list, and the column being aggregated is an outer reference.
148 15 Incorrect time syntax in time string '%.*ls' used with WAITFOR.
149 15 Time value '%.*ls' used with WAITFOR is not a valid value. Check date/time syntax.
150 15 Both terms of an outer join must contain columns.
151 15 '%.*ls' is an invalid money value.
153 15 Invalid usage of the option %.*ls in the %ls statement.
154 15 %S_MSG is not allowed in %S_MSG.
155 15 '%.*ls' is not a recognized %ls option.
156 15 Incorrect syntax near the keyword '%.*ls'.
157 15 An aggregate may not appear in the set list of an UPDATE statement.
159 15 For DROP INDEX, you must give both the table and the index name, in the form tablename.indexname.
160 15 Rule does not contain a variable.
161 15 Rule contains more than one variable.
163 15 The compute by list does not match the order by list.
164 15 GROUP BY expressions must refer to column names that appear in the select list.
165 16 Privilege %ls may not be granted or revoked.
166 15 '%ls' does not allow specifying the database name as a prefix to the object name.
167 16 Cannot create a trigger on a temporary object.
168 15 The %S_MSG '%.*ls' is out of the range of computer representation (%d bytes).
169 15 A column has been specified more than once in the order by list. Columns in the order by list must be unique.
170 15 Line %d: Incorrect syntax near '%.*ls'.
171 15 Cannot use SELECT INTO in browse mode.
172 15 Cannot use HOLDLOCK in browse mode.
173 15 The definition for column '%.*ls' must include a data type.
174 15 The %ls function requires %d arguments.
177 15 The IDENTITY function can only be used when the SELECT statement has an INTO clause.
178 15 A RETURN statement with a return status can only be used in a stored procedure.
179 15 Cannot use the OUTPUT option when passing a constant to a stored procedure.
180 15 There are too many parameters in this %ls statement. The maximum number is %d.
181 15 Cannot use the OUTPUT option in a DECLARE statement.
182 15 Table and column names must be supplied for the READTEXT or WRITETEXT utility.
183 15 The scale (%d) for column '%.*ls' must be within the range %d to %d.
185 15 Data stream is invalid for WRITETEXT statement in bulk form.
186 15 Data stream missing from WRITETEXT statement.
188 15 Cannot specify a log device in a CREATE DATABASE statement without also specifying at least one non-log device.
189 15 The %ls function requires %d to %d arguments.
190 15 Cannot update the function '%.*ls'.
191 15 Some part of your SQL statement is nested too deeply. Rewrite the query or break it up into smaller queries.
192 16 The scale must be less than or equal to the precision.
193 15 The object or column name starting with '%.*ls' is too long. The maximum length is %d characters.
194 15 A SELECT INTO statement cannot contain a SELECT statement that assigns values to a variable.
195 15 '%.*ls' is not a recognized %S_MSG.
196 15 SELECT INTO must be the first query in a SQL statement containing a UNION operator.
198 15 Browse mode is invalid for statements containing a UNION operator.
199 15 An INSERT statement cannot contain a SELECT statement that assigns values to a variable.
201 16 Procedure '%.*ls' expects parameter '%.*ls', which was not supplied.
203 16 The name '%.*ls' is not a valid identifier.
204 20 Normalization error in node %ls.
205 16 All queries in a SQL statement containing a UNION operator must have an equal number of expressions in their target lists.
206 16 Operand type clash: %ls is incompatible with %ls
207 16 Invalid column name '%.*ls'.
208 16 Invalid object name '%.*ls'.
209 16 Ambiguous column name '%.*ls'.
210 16 Syntax error converting datetime from binary/varbinary string.
212 16 Expression result length exceeds the maximum. %d max, %d found.
213 16 Insert Error: Column name or number of supplied values does not match table definition.
214 16 Cannot convert parameter '%ls' to %ls data type expected by procedure.
217 16 Maximum stored procedure nesting level exceeded (limit %d).
220 16 Arithmetic overflow error for data type %ls, value = %ld.
221 10 FIPS Warning: Implicit conversion from %ls to %ls.
223 11 Object ID %ld specified as a default for table ID %ld, column ID %d is missing or not of type default.
224 11 Object ID %ld specified as a rule for table ID %ld, column ID %d is missing or not of type default.
226 16 %ls statement not allowed within multi-statement transaction.
229 14 %ls permission denied on object '%.*ls', database '%.*ls', owner '%.*ls'.
230 14 %ls permission denied on column '%.*ls' of object '%.*ls', database '%.*ls', owner '%.*ls'.
231 11 No such default. ID = %ld, database ID = %d.
232 16 Arithmetic overflow error for type %ls, value = %f.
233 16 The column '%.*ls' in table '%.*ls' cannot be null.
234 16 There is insufficient result space to convert a money value to %ls.
235 16 Cannot convert a char value to money. The char value has incorrect syntax.
236 16 The conversion from char data type to money resulted in a money overflow error.
237 16 There is insufficient result space to convert a money value to %ls.
238 16 There is insufficient result space to convert the %ls value (= %d) to the money data type.
241 16 Syntax error converting datetime from character string.
242 16 The conversion of a char data type to a datetime data type resulted in an out-of-range datetime value.
243 16 Type %.*ls is not a defined system type.
244 16 The conversion of the %ls value '%.*ls' overflowed an %hs column. Use a larger integer column.
245 16 Syntax error converting the %ls value '%.*ls' to a column of data type %ls.
248 16 The conversion of the %ls value '%.*ls' overflowed an int column. Maximum integer value exceeded.
251 16 Could not allocate ancillary table for query optimization. Maximum number of tables in a query (%d) exceeded.
252 16 Cannot group by a bit column.
256 16 The data type %ls is invalid for the %ls function. Allowed types are: char/varchar, nchar/nvarchar, and binary/varbinary.
257 16 Implicit conversion from data type %ls to %ls is not allowed. Use the CONVERT function to run this query.
259 16 Ad hoc updates to system catalogs are not enabled. The system administrator must reconfigure SQL Server to allow this.
260 16 Disallowed implicit conversion from data type %ls to data type %ls, table '%ls', column '%ls'. Use the CONVERT function to run this query.
261 16 '%.*ls' is not a recognized function.
262 16 %ls permission denied, database '%.*ls', owner '%.*ls'.
263 16 Must specify table to select from.
264 16 Column name '%.*ls' appears more than once in the result column list.
266 16 Transaction count after EXECUTE indicates that a COMMIT or ROLLBACK TRANSACTION statement is missing. Previous count = %ld, current count = %ld.
267 16 Object '%.*ls' cannot be found.
268 16 Cannot run SELECT INTO in this database. The database owner must run sp_dboption to enable this option.
270 16 Table '%.*ls' cannot be modified.
271 16 Column '%.*ls' cannot be modified because it is a computed column.
272 16 Cannot update a timestamp column.
273 16 Cannot insert a non-null value into a timestamp column. Use INSERT with a column list or with a default of NULL for the timestamp column.
278 16 The text, ntext, and image data types cannot be used in a GROUP BY clause.
279 16 The text, ntext, and image data types are invalid in this subquery or aggregate expression.
280 16 Only text, ntext, and image data types are valid with the TEXTPTR function.
281 16 %d is not a valid style number when converting from datetime to a character string.
282 10 The '%.*ls' procedure attempted to return a status of NULL, which is not allowed. A status of 0 will be returned instead.
284 16 Rules cannot be bound to text, ntext, or image data types.
285 16 The READTEXT and WRITETEXT statements cannot be used with views.
286 16 The logical tables INSERTED and DELETED cannot be updated.
287 16 The %ls statement is not allowed within a trigger.
288 16 The PATINDEX function operates on char, nchar, varchar, nvarchar, text, and ntext data types only.
292 16 There is insufficient result space to convert a smallmoney value to %ls.
293 16 Cannot convert char value to smallmoney. The char value has incorrect syntax.
294 16 The conversion from char data type to smallmoney data type resulted in a smallmoney overflow error.
295 16 Syntax error converting character string to smalldatetime data type.
296 16 The conversion of char data type to smalldatetime data type resulted in an out-of-range smalldatetime value.
298 16 The conversion from datetime data type to smalldatetime data type resulted in a smalldatetime overflow error.
299 16 The DATEADD function was called with bad type %ls.
301 16 Query contains an outer-join request that is not permitted.
303 16 The table '%.*ls' is an inner member of an outer-join clause. This is not allowed if the table also participates in a regular join clause.
306 16 The text, ntext, and image data types cannot be used in the WHERE, HAVING, or ON clause, except with the LIKE or IS NULL predicates.
307 16 Index ID %d on table '%.*ls' (specified in the FROM clause) does not exist.
308 16 Index '%.*ls' on table '%.*ls' (specified in the FROM clause) does not exist.
310 16 Invalid escape sequence. Valid characters after ESC are: an ESC pair, underscore, percent sign.
311 16 Cannot use text, ntext, or image columns in the 'inserted' and 'deleted' tables.
312 16 Cannot reference text, ntext, or image columns in a filter stored procedure.
401 16 Unimplemented statement or expression %ls.
403 16 Invalid operator for data type. Operator equals %ls, type equals %ls.
409 16 The %ls operation cannot take a %ls data type as an argument.
410 20 COMPUTE clause #%d 'BY' expression #%d is not in the order by list.
411 20 COMPUTE clause #%d, aggregate expression #%d is not in the select list.
420 16 The text, ntext, and image data types cannot be used in an ORDER BY clause.
425 16 Data type %ls of receiving variable is not equal to the data type %ls of column '%.*ls'.
426 16 The length %d of the receiving variable is less than the length %d of the column '%.*ls'.
427 20 Could not load sysprocedures entries for constraint ID %d in database ID %d.
428 20 Could not find row in sysconstraints for constraint ID %d in database ID %d.
429 20 Could not find new constraint ID %d in sysconstraints, database ID %d, at compile time.
430 20 Could not resolve table name for object ID %d, database ID %d, when compiling foreign key.
431 19 Could not bind foreign key constraint. Too many tables involved in the query.
433 20 Could not find CHECK constraint for '%.*ls', although the table is flagged as having one.
436 20 Could not open referenced table ID %d in database ID %d.
437 20 Could not resolve the referenced column name in table ID %d.
438 20 Could not resolve the referencing column name in table ID %d.
439 20 Could not find FOREIGN KEY constraints for table '%.*ls' in database ID %d although the table is flagged as having them.
441 16 Cannot use the '%ls' function on a remote data source.
505 16 Current user account was invoked with SETUSER. Changing databases is not allowed.
506 16 Invalid ESCAPE character '%.*hs' has been specified in a LIKE predicate.
507 16 Invalid argument %d specified for SET ROWCOUNT.
509 11 User name '%.*ls' not found.
510 16 Cannot create a work table row larger than allowable maximum. Resubmit your query with the ROBUST PLAN hint.
511 16 Cannot create a row of size %d which is greater than the allowable maximum of %d.
512 16 Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression.
513 16 A column insert or update conflicts with a rule imposed by a previous CREATE RULE statement. The statement was terminated. The conflict occurred in database '%.*ls', table '%.*ls', column '%.*ls'.
515 16 Cannot insert the value NULL into column '%.*ls', table '%.*ls'; column does not allow nulls. %ls fails.
516 18 Could not get system date/time.
517 16 Adding a value to a '%ls' column caused overflow.
518 16 Cannot convert data type %ls to %ls.
528 20 System error detected during attempt to use the 'upsleep' system function.
529 16 Explicit conversion from data type %ls to %ls is not allowed.
532 16 The timestamp (changed to %S_TS) shows that the row has been updated by another user.
535 16 Difference of two datetime columns caused overflow at runtime.
536 16 Invalid length parameter passed to the substring function.
538 16 Cannot find '%.*ls'. This language may have been dropped. Contact your system administrator.
542 16 An invalid datetime value was encountered. Value exceeds the year 9999.
544 16 Cannot insert explicit value for identity column in table '%.*ls' when IDENTITY_INSERT is set to OFF.
545 16 Explicit value must be specified for identity column in table '%.*ls' when IDENTITY_INSERT is set to ON.
547 16 %ls statement conflicted with %ls %ls constraint '%.*ls'. The conflict occurred in database '%.*ls', table '%.*ls'%ls%.*ls%ls.
548 16 Cannot perform direct %ls to range maintained by replication. The conflict occurred in database '%.*ls', table '%.*ls'%ls%.*ls%ls.
550 16 The attempted insert or update failed because the target view either specifies WITH CHECK OPTION or spans a view that specifies WITH CHECK OPTION and one or more rows resulting from the operation did not qualify under the CHECK OPTION constraint.
551 16 The checksum has changed to %d. This shows that the row has been updated by another user.
553 16 %hs over nullable side of outer join query on table '%ls'.
555 16 User-defined functions are not yet enabled.
556 16 INSERT EXEC failed because the stored procedure altered the schema of the target table.
601 12 Could not continue scan with NOLOCK due to data movement.
602 21 Could not find row in sysindexes for database ID %d, object ID %ld, index ID %d. Run DBCC CHECKTABLE on sysindexes.
604 21 Could not find row in sysobjects for object ID %ld in database '%.*ls'. Run DBCC CHECKTABLE on sysobjects.
605 21 Attempt to fetch logical page %S_PGID in database '%.*ls' belongs to object '%.*ls', not to object '%.*ls'.
607 21 Insufficient room was allocated for search arguments in the session descriptor for object '%.*ls'. Only %d search arguments were anticipated.
615 21 Could not find database table ID %d, name '%.*ls'.
617 20 Descriptor for object ID %ld in database ID %d not found in the hash table during attempt to unhash it.
618 21 A varno of %d was passed to the opentable system function. The largest valid value is %d.
623 21 Could not retrieve row from page by RID because logical page %S_PGID is not a data page. %S_RID. %S_PAGE.
624 21 Could not retrieve row from page by RID because the requested RID has a higher number than the last RID on the page. %S_RID.%S_PAGE, DBID %d.
625 21 Could not retrieve row from logical page %S_PGID by RID because the entry in the offset table (%d) for that RID (%d) is less than or equal to 0.
626 16 Cannot use ROLLBACK with a savepoint within a distributed transaction.
627 16 Cannot use SAVE TRANSACTION within a distributed transaction.
628 13 Cannot issue SAVE TRANSACTION when there is no active transaction.
635 20 Process %d tried to remove DES resource lock %S_DES, which it does not hold.
637 20 Index shrink program returned invalid status of 0.
639 21 Could not fetch logical page %S_PGID, database ID %d. The page is not currently allocated.
644 21 Could not find the index entry for RID '%.*hs' in index page %S_PGID, index ID %d, database '%.*ls'.
649 21 Could not find the clustered index entry for page %S_PGID, object ID %ld, status 0x%x. Index page %S_PGID, in database '%.*ls', was searched for this entry.
650 16 You can only specify the READPAST lock in the READ COMMITTED or REPEATABLE READ isolation levels.
651 16 Cannot use %hs granularity hint on table '%.*ls' because locking at the specified granularity is inhibited.
652 16 Index ID %d for table '%.*ls' resides on a read-only filegroup which cannot be modified.
653 20 Two buffers are conflicting for the same keep slot in table '%.*ls'.
654 20 No slots are free to keep buffers for table '%.*ls'.
655 20 Expected to find buffer in keep slot for table '%.*ls'.
666 16 Maximum system-generated unique value for a duplicate group exceeded for table ID %d, index ID %d. Dropping and re-creating the index may fix the problem; otherwise use another clustering key.
701 19 There is insufficient system memory to run this query.
708 10 Warning: Due to low virtual memory, special reserved memory used %d times since startup. Increase virtual memory on server.
802 17 No more buffers can be stolen.
804 20 Could not find buffer 0x%lx holding logical page %S_PGID in the SDES 0x%lx kept buffer pool for object '%.*ls'.
809 20 Buffer 0x%lx, allocation page %S_PGID, in database '%.*ls' is not in allocation buffer pool in PSS (process status structure). Contact Technical Support.
813 20 Logical page %S_PGID in database ID %d is already hashed.
816 20 Process ID %d tried to remove a buffer resource lock %S_BUF that it does not hold in SDES %S_SDES. Contact Technical Support.
818 19 There is no room to hold the buffer resource lock %S_BUF in SDES %S_SDES. Contact Technical Support.
821 20 Could not unhash buffer at 0x%lx with a buffer page number of %S_PGID and database ID %d with HASHED status set. The buffer was not found. %S_PAGE.
822 21 Could not start I/O for request %S_BLKIOPTR.
823 24 I/O error %ls detected during %S_MSG of %S_BUF.
834 21 The bufclean system function was called on dirty buffer (page %S_PGID, stat %#x/%#x, objid %#x, sstat%#x).
840 17 Device '%.*ls' (physical name '%.*ls', virtual device number %d) is not available. Contact the system administrator for assistance.
844 10 Time out occurred while waiting for buffer latch type %d, bp %#x, page %S_PGID, stat %#x, object ID %d:%d:%d, waittime %d. Continuing to wait.
845 17 Time out occurred while waiting for buffer latch type %d for page %S_PGID, database ID %d, object ID %d, index ID %d.
901 21 Could not find descriptor for database ID %d, object ID %ld in hash table after hashing it.
903 22 Could not find row in sysindexes for clustered index on system catalog %ld in database ID %d. This index should exist in all databases. Run DBCC CHECKTABLE on sysindexes in the database.
906 22 Could not locate row in sysobjects for system catalog '%.*ls' in database '%.*ls'. This system catalog should exist in all databases. Run DBCC CHECKTABLE on sysobjects in this database.
911 16 Could not locate entry in sysdatabases for database '%.*ls'. No entry found with that name. Make sure that the name is entered correctly.
913 22 Could not find database ID %d. Database may not be activated yet or may be in transition.
916 14 Server user '%.*ls' is not a valid user in database '%.*ls'.
921 14 Database '%.*ls' has not been recovered yet. Wait and try again.
922 14 Database '%.*ls' is being recovered. Waiting until recovery is finished.
923 14 User %d not allowed in database '%.*ls'. Only the owner can access this database.
924 14 Database '%.*ls' is already open and can only have one user at a time.
925 19 Maximum number of databases used for each query has been exceeded. The maximum allowed is %d.
926 14 Database '%.*ls' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.
927 14 Database '%.*ls' cannot be opened. It is in the middle of a restore.
929 20 Attempting to close a database that is not already open. Contact Technical Support.
941 14 Cannot open database '%.*ls'. It has not been upgraded to the latest format.
942 14 Database '%.*ls' cannot be opened because it is offline.
943 14 Database '%.*ls' cannot be opened because its version (%d) is later than the current server version (%d).
944 10 Converting database '%.*ls' from version %d to the current version %d.
945 16 Database '%.*ls' cannot be opened because some of the files could not be activated.
946 14 Cannot open database '%.*ls' version %d. Upgrade the database to the latest version.
947 16 Error while closing database '%.*ls' cleanly.

1nd round export and import error

1I have checked the log of the 1nd round import and found there is a stop in the end of the SAPVIEW.log,

(IMP) ERROR: CREATE statement failed for object "M_ZSNOI"
(CREATE VIEW "M_ZSNOI" ( "MANDT", "BUKRS", "ZCSRG", "ZCSNO" ) AS SELECT T0001.MANDT, T0001.BUKRS, T0001.ZCSRG, T0001.ZCSNO
FROM ZPICNTSH T0001)
DbSlExecute: rc = 107
(SQL error 208)
error message returned by DbSl:
MSGNO 208, MSGSTATE 1, SEVERITY 16 -- Invalid object name 'ZPICNTSH'.
srvname SAPSRV01 : procname M_ZSNOI : line 1
#STOP: 20070405101300

Maybe is this caused the TRDIR's lost, TRDIR is also a view, And I have checked the str file(SAPVIEW.STR) of 1nd round export, the TRDIR is exported,

vie: TRDIR
fld: NAME
fld: SQLX
fld: EDTX
fld: VARCL
fld: DBAPL
fld: DBNA
fld: CLAS
fld: TYPE
fld: OCCURS
fld: SUBC
fld: APPL
fld: SECU
fld: CNAM
fld: CDAT
fld: UNAM
fld: UDAT
fld: VERN
fld: LEVL
fld: RSTAT
fld: RMAND
fld: RLOAD
fld: FIXPT
fld: SSET
fld: SDATE
fld: STIME
fld: IDATE
fld: ITIME
qry: SELECT PROG, SQLX, EDTX, VARCL, DBAPL, DBNA, CLAS, TYPE, OCCURS, SUBC, APPL, SECU, CNAM, CDAT, UNAM, UDAT, VERN, LEVL, RSTAT, RMAND, RLOAD, FIXPT, SSET, SDATE, STIME, IDATE, ITIME
FROM D010SINF
WHERE R3STATE = 'A' AND R3MODE = 'M' AND R3VERSION = '0001'

I have search MS SQL help, found SQL error 208:

Error 208
Severity Level 16
Message Text
Invalid object name '%.*ls'.

Explanation
This error occurs when an object that does not exist is referenced. If the object exists, you might need to include the owner¡¯s name in the object name.

If the object is not owned by the user attempting to access it, and it is not owned by the database owner, all references to the object must include the owner¡¯s name. For example, if user1 creates a table called test, other users must use the name user1.test when they refer to the table.

The Microsoft? SQL Server? naming convention for database objects is:

[[[server_name.][database_name].][owner_name].]object_name

The default value for server_name is the current server and the default value for database_name is the current database. The default value for owner_name is the current user. Because owner_name is part of the object name, it is possible for two different users to have tables with the same name in the same database (for example, user1.test and user2.test). For additional information about naming conventions, see Transact-SQL Syntax Conventions.

This message can also occur when you reference a temporary table that was created with an EXECUTE statement.

Action
The procedure for handling this error depends on what you know about the object indicated in the error message text.

The appropriate permissions must also be set to allow access to an object. If these permissions are not set, error 229 or 230 occurs.

If you do not know who owns the object
Execute sp_help with no parameters to display the object owner.
Or

Query the Information Schema Views if the object is a table or view to determine the object owner and type. If the object is not a table or a view, query the sysobjects system table to determine the object owner and type.
For example, to determine the owner and type for the object named table_1, execute the following:

USE master

GO

SELECT TABLE_SCHEMA

FROM INFORMATION_SCHEMA.TABLES

WHERE TABLE_NAME = 'table_1'

GO



If no rows are returned from this query, the object either resides in a different database or does not exist.

If you do not own the object in question
Include the object owner in the object name. For example:
SELECT *

FROM user1.table_1



Although using fully qualified object names eliminates this problem, remember that including the fully qualified object name in an application might complicate the maintenance of the application. For example, if all references to a table include the database name, changing the database name could become difficult.

Or

Have the database owner create the object. If the owner creates the object, any user can find the object without specifying the owner. However, temporary tables reside in tempdb and are dropped automatically when the user process or server connection that created them is terminated. Users cannot share temporary tables, even if they are created by the database owner.
If the object does not reside in the database
Switch context to the correct database using the USE statement. For example:
USE database_1



Or

Qualify the object name with the database name. For example:
SELECT *

FROM database_1.user1.table_1



If you own the object or if the object is owned by the database owner, the owner name is not needed. For example:

SELECT *

FROM database_1..table_1



If a temporary table created with an EXECUTE statement is referenced
If you must use the EXECUTE statement to create a temporary table, create it as a global temporary table using the syntax ##tablename.
See Also
CREATE TABLE SELECT
Creating and Modifying a Table sp_help
Errors 1 - 999 sysobjects
EXECUTE Transact-SQL Syntax Conventions
Information Schema Views USE
Querying SQL Server System Catalogs

终于要升级了

最近在忙SAP升级，是将原来的Oracle 7.3.4转到MS　SQL数据库，你要问为什么要O转M？一言概之，人家便宜啊！

顾问设计的升级路线是：Oracle 7.3.4, MS SQL 7， MS SQL 2000, 2005

数据就是这样升法，SAP KERNEL是3.1I COM, 3.1I EXT, 4.6D ，最后是mySAP 2005，估计是明年的事啦,HAHA.

ORA-1652: unable to extend temp segment by 256 in tablespace PSAPTEMP

在测试倒出时发生ORA－1652　ERROR，是在SAPAPPL1.LOG中 #START: 20070327015019 (EXP) ERROR: DbSlExeRead: rc = 99, table "QCMZPCED" (SQL error 1652) error message returned by DbSl: ORA-01652: unable to extend temp segment by 256 in tablespace PSAPTEMP #STOP: 20070327025836 研究一下，重启RESET帮助不行，看来得加DATAFILE，一口气将DATAFILE加倍了 ALTER TABLESPACE "PSAPTEMP" DEFAULT STORAGE ( MAXEXTENTS UNLIMITED ) ALTER TABLESPACE "PSAPTEMP" ADD DATAFILE 'g:oracleLMXsapdata1temp_5temp.data5' size 2088960 K ALTER TABLESPACE "PSAPTEMP" ADD DATAFILE 'g:oracleLMXsapdata1temp_6temp.data6' size 2088960 K ALTER TABLESPACE "PSAPTEMP" ADD DATAFILE 'g:oracleLMXsapdata1temp_7temp.data7' size 2088960 K ALTER TABLESPACE "PSAPTEMP" ADD DATAFILE 'g:oracleLMXsapdata1temp_8temp.data8' size 2088960 K

最近三个月忙啊

先是办公区域装修，忙完了； 跟着是所有PC要跟着动，过年一起忙完了； 机房也要大搬迁，现在正忙着呢，新的设备，什么交换机，路由，PIX啊，KVM啊，都没来全，等吧！ 结果就是加班也没有，病了一场，现在还在咳，都咳两周了，算上今天，第三周了 忙啊！不是人干的！ 只有两台HP的DL580来了，建个域是作SAP升级测试环境 又要在旧机上测试完整数据库。。。

问SQL客户端连接不上服务器（转）

问SQL客户端连接不上服务器

Telnet 127.0.0.1 1433

正在连接到222.20.43.211...不能打开到主机的连接， 在端口 1433: 连接失败

处理及解决:

A. Telnet IP 1433,错误的话下一步.

B. 使用服务器配置工具-启动WINSOCK,

C. 不行的话,使用客户端配置工具-别名,服务器别名使用服务器的计算机名称,服务器名使用服务器所在的IP.

D. 再不行启动1344UDP端口.不知道怎么开启,不过一般在SQL服务器运行后也会运行的.

E. 其实这个问题在SQL SERVER 2000 +XP的系统中经常出现,(2003不是很清楚),按装好SQL SERVER 2000后,启动企业管理器查看 SQL SERVER 2000的系统日志,在日志中可以看到SQL SERVER 启动的是那些协议来等待远程连接的,象楼主说的情况,打开SQL SERVER 2000 看到日志里面.会发现日志记录为SQL SERVER 2000正在监听以NAMEPIPED或者SHARE MEMORY的方式来等待连接.象这中情况,打SP3的补丁是可以解决的.打完补丁,重新启动机器,或者重新启动服务,你会看到SQL SERVER 2000正在监听1433端口了.比NETSTAT- AN 要直观些.

F. 删除XP系统中的SP2补丁.

问SQL客户端连接不上服务器（转）

问SQL客户端连接不上服务器

Telnet 127.0.0.1 1433

正在连接到222.20.43.211...不能打开到主机的连接， 在端口 1433: 连接失败

处理及解决:

A. Telnet IP 1433,错误的话下一步.

B. 使用服务器配置工具-启动WINSOCK,

C. 不行的话,使用客户端配置工具-别名,服务器别名使用服务器的计算机名称,服务器名使用服务器所在的IP.

D. 再不行启动1344UDP端口.不知道怎么开启,不过一般在SQL服务器运行后也会运行的.

E. 其实这个问题在SQL SERVER 2000 +XP的系统中经常出现,(2003不是很清楚),按装好SQL SERVER 2000后,启动企业管理器查看 SQL SERVER 2000的系统日志,在日志中可以看到SQL SERVER 启动的是那些协议来等待远程连接的,象楼主说的情况,打开SQL SERVER 2000 看到日志里面.会发现日志记录为SQL SERVER 2000正在监听以NAMEPIPED或者SHARE MEMORY的方式来等待连接.象这中情况,打SP3的补丁是可以解决的.打完补丁,重新启动机器,或者重新启动服务,你会看到SQL SERVER 2000正在监听1433端口了.比NETSTAT- AN 要直观些.

F. 删除XP系统中的SP2补丁.

使用BRTOOLS的环境

ORACLE_SID

ORACLE_HOME

SAPDATA_HOME

OMS发现不到新加的DB

重启一下Agent服务即可

Business area missing

仓库和财务的用户打电话过来抱怨说，在过帐/转仓时出错了，提示说业务范围（Business area)没有定义。

联系FI模块的开发，原来被删掉了一个业务范围！

OV03，维护“业务部门”(Maitain Business area）中添加回去就解决问题。

从招聘SAP开发看中国人的诚信

5个面试人员

IT初试全过关

HR进行诚信测试时，刷下四个，分别是三个毕业证书或学习经历“出错”，一个是工作经历“出错”

在某公司工作二个月，写成工作二年！

大哥，会不会夸张了一点点。。。

Modified the sapstop.bat script for complete shutdown database for cold backup.

重看oracle管理文档，发现在自已一直用shutdown immediate来关闭数据库，推荐用法是再来一次startup和shutdown

立马修改自已的脚本！

Backup can not finished in one tape

狠狠心，这是台测试服务器，只备份数据文件吧

ORA-01652出现在ROLLBACK　TABLESPACE

终于亲身经历了一回ORA-00600

早上检查生产库和测试库时，发现有Miss index。而这条index是开发建的，而建立的时间！正好是前几天大批用户complaint系统太慢的哪天！这几天我搞不清楚原因，终找到源头！

而这条index建的也不怎么样，开发都忘了加一个主键（MANDT），只好从建。

先从测试库开始，由于是测试数据库，也没太在意！但点了重建后，没过几分钟，测试用户说不知怎的突然退出了！

检查才发现，ORACLE crashed！在ALERT.log中还看到了ORA-00600

Thu Dec 07 09:07:12 2006
Errors in file G:oracleLMXsaptracebackgroundlmxDBWR.TRC:
ORA-00600: internal error code, arguments: [3382], [1], [1161843650], [1161843969], [], [], [], []

Dump file G:oracleLMXsaptracebackgroundlmxALRT.LOG

检查了别的log，也没发现别的有用信息！判断是重建索引与测试用户冲突了，心里庆幸当日开发在生产库时建索引没出事。硬着头皮，关掉ORACLE的服务，再重启。发现还没“损伤”。大幸！

立马锁定所有用户，exclude when rebuilding the index。

次日，在生产库也依样葫芦！

ORA-01652出现在TEMP　TABLESPACE

ORA-01632

开发在导入数据时出现Ora-01632错误，研究一下，发现是Primary index出错，原因是SAP默认的Next设置的太小，而开发要导入数据太大，而Max Extents根本不够。

有两个方向解决这个问题，一是增大Next，一是增大Maxextents；向开发了解到，这次导入数据后，以后罕有数据update，据以此，选择增大Maxtents：

Alter index SAPR3.ZPIBOOKD__0 storage ( Maxextents 3000);

Database error 1632 requires intervention by the database administrator
DB error 1632 at SEL access to table ZPIBOOKD
> ORA-01632: max # extents
> (300) reached in index
> SAPR3.ZPIBOOKD__0#
Perform rollback
Run-time error ExecuteCall
> Program YMIN5A03, Include YMIN5A03, line 1006
Run-time error getwa_abswa
> Short dump 061206105623sa generated for error pdem CALVINFUNG

Alter table/index SAPR3.* storage ( Next 4096K);

前任管理员在做Reorganization时，设置了compress extent和Next为SAP预定义的大小，结果是优化存储，但同时带来一个负面效应：每个对象的Next Extent都设置的太大了！

而数据库最大的Freespace就是2GB，用着用着就说不够空间！

没别的办法，将所有Next大于4MB的对象全select出来，然后：

Alter table/index SAPR3.* storage ( Next 4096K);

Update deactived.

入单的用户打电话过来，说不能保存，提示Update deactived.
远程登录DB查看，发现是index tablespace不够空间了，赶紧又加了2GB data file.

重新activate Update.

Oracle 10g 测试数据库could not open

重建一条index，发现session hand;

以为语法问题，仔细看了一下，不象！刷新EM，发现DB已经不能打开了，出现说存储空间不空。。。

由于是测试数据库，存储空间是用ASM，是用DISKPART建两个硬盘分区组成的。

所有的数据文件，备份，FLASHBACK数据也放在里面，本想ASMCMD进去，但出错说instance现在的状态不能进去。。。

进不去就不能删除一些文件，加一个硬盘分区又不想这样做。

看到出错的信息，主要是：

Wed Nov 29 10:41:55 2006
Errors in file c:oracleproduct10.2.0adminken1020bbdumpken1020b_arc1_3464.trc:
ORA-16014: log 2 sequence# 36 not archived, no available destinations
ORA-00312: online log 2 thread 1: '+ASMTEST/ken1020b/onlinelog/group_2.264.606743763'
ORA-00312: online log 2 thread 1: '+ASMTEST/ken1020b/onlinelog/group_2.265.606743769'

Archive log文件没法建了！！！自然影响整个数据库的状态。

想恢复正常，除了增大空间外，只能将部分文件删除以省出一点空间来，这只是一个测试库：

1，进磁盘组。。。删除不重要的文件，如以前的Archive log；

2， alter database clear unarchived logfile group 2;

将当前的logfile group 2不要了，嘿嘿！

正常打开后，调整一个备份的策略！省的空间出来，这只是10GB的空间啊！