Hi,

I am trying to delete incorrect Index Categories using t-code SRMO after a system copy (restore db from backup) from our production system to our sandbox system.

When I select the Index Category  and click on the "Delete Category" button I get this message:

Error during deletion of language 'EN'. Search

engine result '3147'

When I click on the Help button I get this:

Error during deletion of language 'EN'. Search engine result '3147'

Message no. SRET148

Diagnosis

When the index category is deleted, all languages, and consequently all physical indices on the search server (RFC server) are deleted.

If a physical index could not be deleted, the index category is not deleted or set to inactive either. This is to prevent the index from staying on the search server without R/3 inforamtion.

Procedure

Firstly clean up all languages / indexes for which this information appears.

Use the function to delete an index without R/3 information (if such an index exists) and / or  the function to delete the language without an index from the R/3 System.

You can then call the function 'Delete index category' again.

Any ideas on what function they are talking about in the second to last paragraph: "function to delete an index without r/3 information"?

Thank you,

Neil

Today I am starting a new blog series, about some issues when incorrect configuration is made on the Security Audit Log (SAL).

If you are interested on reading the most comprehensive document on SAL that I ever found, then please read “Analysis and Recommended Settings of the Security Audit Log (SM19 / SM20)”.

Why no UNC and NFS mounts?

The story short: performance.

SAL needs a stable file system to write. UNC (Universal Naming Convention) and NFS (Network File System) mounts are not appropriate. There is a variety of known issues using any of both.

Note that the file handler for SAL file needs to keep opened, due to performance reasons. The file handler would point to an arbitrary location when the file system disappears.

What should I do then?

The SAL files I have are huge, and I do not have enough file system space to store them. What should I do, if I cannot use UNC and NFS mounts?

You should use the local file system. Of course, since you have limited file system space, then you should use OS-level tools to archive audit files. Archived files can be moved to NFS mount location or to a UNC path. If you want to read individual files, then you can use report RSAU_SELECT_EVENTS (a single file can be read at time).

Additional Information

• 539404 - FAQ: Answers to questions about the Security Audit Log
• 1810913 - Performance improvement when reading the Security Audit Log
• 2191612 - FAQ | Use of Security Audit Log as of NetWeaver 7.50

Stay tuned for my next blog on SAL.

Hello

After sap system rename via SWPM tool for setup Virtualhsotname to ABAP system, RFC ABAP to the virtual host name failed.

RFC ABAP hostname from OS level => OK

RFC ABAP virtualhsotname for SAP => NOK

Erreur connexion

Error when opening an RFC connection (CPIC-CALL: 'ThSAPOCMINIT' : cmRc=27 thRc=2

ERROR: timeout during allocate

LOCATION: SAP-Gateway on host xxlocal_systemxxx / sapgw00

DETAIL: no connect of TP sapdp00 from host xx_virtual_hostnamexx after 20 sec

COMPONENT: SAP-Gateway

COUNTER: 286053

MODULE: gwr3cpic.c

LINE: 2189

CODE RETOUR: 242

SUBRC: 0

RELEASE: 721

TIME: Wed Apr 13 11:09:42 2016

VERSION: 2

Support will be appreciate

Regards

Eric MOUREY

Dear Experts,

This is regarding below two errors in log viewer belonging to component BC-XI-IBD

1) No hostname and Http port defined in Exchange profile sld.<SID>.<hostname>

2) Creating CIM client failed. Parameter password is empty.

SAP Process Orchestration system 7.40 on Oracle 11

This system was recently upgraded to 7.40 and we saw the first error mentioned above "No hostname and http port defined...." in D, Q and P system.

Hence we applied note 2198240, in which it says to change property of usage_type setting from XPI to CE

After we applied the change throughout the landscape the error "No hostname and http port..." were NOT occurring in systems

But we found strange thing ONLY in production system, we started receiving  the second error "Creating CIM client failed. Parameter password is empty"
For the second error we found note 1638667, which says to change usage_type setting property from CE to XPI.

We want to get rid of this reoccurring errors everday.

Kindly let me know your expert views.

regards,

Trever

Hi Team,

I am trying to use SUM to deploye Identity management on AS Java

Steps performed are mentioned below

1. Server came up succesfull without arrors, i ran STARTUP.BAT with SIDADM and it ran succesfully.

2. Now i tried starting gui from /usr/sap/smd/sum/startgui

It pops up software delivery tool and when tried connecting it on 4239 it throwed below errior

I can see telnet results are passing on both the ports i.e 4239 and d241

.Version SUM: SUM10SP16_7

AS JAVA: SAP Netweaver 7.4

Database: MxDb.

please help us in resolving that issue.

Good day experts,

I tried running a report in background, I choose immediately so that it doesn't have to be scheduled. But when I checked it in my own jobs, It remains at scheduled status. When I tried it on my admin account, It works and with status finished. It seems to be an authorization problem. What object could I be missing with my user account? I tried S_TCODE SMX and SP02 but still not working.

Thanks in advance!

Hello,

I'm trying to create a JDBC datasource on a Netweaver 7.3 Java system.

I've created a JDBC-Driver with ojdbc6.jar to connect to an Oracle 11g database (external system).

After this I created a custom JDBC-DataSource using this driver, vendor SQL and JDBC-Version 2.0.

As Object-Factory i used oracle.jdbc.pool.OracleDataSourceFactory and XADS-Class ist oracle.jdbc.xa.client.OracleXADataSource.

Within the additional properties I specified the URL like this: jdbc:oracle:thin:@<FQDN of db-server>:<port>:ORCL

But when I try to ping this connection an error occures:

DataSourceManagerImpl.pingXADSConnection(), Database access related error occurred.
[EXCEPTION]
java.rmi.RemoteException: Database access related error occurred.; nested exception is:
java.sql.SQLException: Ungültiger Oracle-URL angegeben: OracleDataSource.makeURL

Any help would be greatly appreciated.

Best regards, Bernd

When I try to undeploy an EAR file from a SAP Java AS 7.3 with NWDS, I am getting the message "EAR is required and cannot be removed from the server".  The EAR contains a custom PI adapter modul (EJB).

Does anybody know, how I can get around this problem?

In this document you will find the latest information about the SAP kernel such as

• Announcements of SP stack kernel deliveries
• Other news related to the development, maintenance and usage of the SAP kernel versions 72X (720, 720_EXT, 721, 721_EXT, 722, 722_EXT) and 74X (741, 742, 745)

If you are interested in getting notifications when this document is updated, please activate the "Receive email notifications" feature. To unsubscribe from receiving notifications, click on "Stop email notifications".

News

14.04.2016: WebGUI issue with Google Chrome Version 50

After updating Google Chrome from Version 49 to Version 50 the Easy Access Menu (start screen) remains empty. We are working on a kernel patch to circumvent this. For details see SAP Note 2305778.

12.04.2016: potential issue with Kernel 742 PL 311 - 321 and Kernel 745 PL 25 - 35

In edge cases a select statement may return an unexpected result. For details see SAP Note 2273425.
It is recommended to upgrade to SP Stack Kernel 745 PL 100 or Kernel 742 PL 329 which is the last release candidate before the upcoming SP Stack Kernel 742 PL 400.

17.03.2016: Kernel 745 Released as DCK to Kernels 740, 741 and 742

After an extended validation phase kernel 745 PL#100 has been released as a downward compatible kernel (DCK) to kernels 742, 741 and 740 and can be used instead of these with SAP NetWeaver 7.4. Refer to SAP Note 2251972 for details on installation and usage of kernel 742 as DCK. The release roadmap for 74* kernels is presented in SAP Note 1969546.

17.03.2016: SP Stack Kernel 722 PL 101 released

SP stack kernel 722 PL #101 is now available on SAP Support Portal. It contains various improvements and enhancements that are outlined in detail in Note 2292019.

Information on known issues in the stack kernel 722 PL #101 can be found in Note 2292017. This note will be updated on a regular basis.

18.12.2015: SAP Kernel 721 PL 618 and SAP Kernel 722 PL 20 and PL 21 revoked

As a precaution the Kernel (dw.sar) for 721 PL 618 and 722 PL 20 and 21 have been revoked from the SAP Support Portal.

For further details see SAP Note 2259736. We are working a patch highest priority.

13.11.2015: Heads up on Kernel 745 for NetWeaver 7.4

During Q1/2016 SAP Kernel 745 will be made available as Downward Compatible Kernel for SAP NetWeaver 7.4.

SAP Kernel 745 will eventually succeed SAP Kernel 742 (and 741 and 740).

SAP Kernel 742 will be retired in Q1/2017, one year later than the availability of SAP Kernel 745 as DCK. No more patches will be provided for SAP Kernel 742 after that date.

See also Understanding Kernel Releases for the SAP NetWeaver AS ABAP and SAP Note 1969546 - Release Roadmap Kernel 740

09.11.2015: SP Stack Kernel 742 PL#300 Released

SP stack kernel 742 PL #300 is now available on SAP Support Portal. It contains various improvements and enhancements that are outlined in detail in SAP Note 2237353.

Information on known issues in the stack kernel 742 PL #300 can be found in SAP Note 2231749. This note will be updated on a regular basis.

16.10.2015: Kernel 722 PL14, PL15 and enserver PL 14 revoked

As a precaution Enqueue Server 722 PL 14 (enserver.sar) and Kernel (dw.sar) 722 PL 14 and PL 15 have been revoked from the SAP Support Portal.
The new patch of the Enqueue Server might not be 100% compatible to older clients (e.g. disp+work PL 13) and the newer disp+work starting PL 14 might not be 100% compatible with old Enqueue Servers (prior patch 14). Standard operations Enque, Dequeue and DequeueAll are NOT affected. Details can be found in SAP Note 2239931

13.10.2015: SP Stack Kernel 721 PL#600 Released

SP stack kernel 721 PL #600 is now available on SAP Support Portal. It contains various improvements and enhancements that are outlined in detail in SAP Note 2214191.

Information on known issues in the stack kernel 721 PL #600 can be found in SAP Note 2214680. This note will be updated on a regular basis.

02.10.2015: issue with Oracle lib_DBSL 722 PL 13

Please do not use patch 13 for the 722 Oracle lib_DBSL

Further details can be found in note 2220724. A fix is expected early next week.

14.09.2015: SP Stack Kernel 741 PL#300 Released

The last SP stack kernel for the 741 kernel version has been released today. Kernel 741 PL #300 can be downloaded from the archive area of SAP Support Portal. Refer to release note 2207362 for information on fixes included in this stack kernel.

As announced previously, kernel 741 has reached its end of maintenance, see note 1969546 for more detail. Future 74* kernel corrections will be delivered through 742 kernel patches.

08.07.2015: SP Stack Kernel 742 PL#200 Released

SP stack kernel 742 PL #200 is now available on SAP Support Portal. It contains various improvements and enhancements that are outlined in detail in Note 2178917.

Information on known issues in the stack kernel 742 PL #200 can be found in Note 2176515. This note will be updated on a regular basis.

07.07.2015 SAP Kernel 741 maintenance

The SAP Kernel 741 reached its end of maintenance, see note 1969546. We will continue to deliver regression fixes during July and a final stack kernel 741 PL#300 in August. After that corrections will be delivered through kernel 742 patches.

12.06.2015 SAP Kernel Archive

SAP Kernels which are out of maintenance like SAP Kernel 720 can be found in the archive https://support.sap.com/software/patches/archive.html

For SAP Kernel 720 the last version is patch level 800. Please read the release note 2158874  - SAP Support Package Stack Kernel 7.20 (EXT) Patch Level 800. Corresponding note for regression found in the future is 2138737.

20.05.2015 SAP Kernel 722 Released

SAP kernel 722 has been released for customers today. The first shipment (Kernel 722 PL#4) can now be downloaded from SAP Support Portal. With this a new release cycle has been established for 72X kernel versions that can be used with all SAP NetWeaver releases 7.00-7.31:

• Kernel 720 reached its end of maintenance, no further corrections will be provided for this kernel version
• Kernel 721 becomes the standard kernel containing only corrections/bug fixes
• Kernel 722 replaces Kernel 721 in its role as Innovation Kernel. Besides regular corrections, new features/enhancements/improvements will be delivered with Kernel 722.

Refer to SAP Note 2133909 for general information on Kernel 722 including new features and current limitations. This note will be updated on regular basis.

Kernel 722 can be applied manually as a kernel patch, see Note 2115344 - Installation of Kernel 722 (EXT) for detailed instructions. Options to apply Kernel 722 during upgrade/update are outlined in Note 2133909.

04.05.2015: SP Stack Kernel 721 PL#500 Released

A new SP stack kernel 721 PL #500 is now available on SAP Support Portal.

SAP Note 2158856 contains the list of changes and enhancements introduced in this stack kernel compared to the previous stack kernel PL #402.

All regressions known in the PL #402 have been fixed.

Review SAP Note 2155366 for known issues in the stack kernel 721 PL #500. This note will be continuously updated.

14.04.2015: Kernel 742 Released as DCK to Kernels 740 and 741

After an extended validation phase kernel 742 PL#101 has been released as a downward compatible kernel (DCK) to kernels 741 and 740 and can be used instead of these with SAP NetWeaver 7.4. Refer to Note 2128122 for details on installation and usage of kernel 742 as DCK. The release roadmap for 74* kernels is presented in Note 1969546.

31.03.2015: SP Stack Kernels 741 PL#201 and 742 PL#101 are delivered

As announced previously, SP Stack kernels for 741 and 742 kernel versions have been updated. 741 PL#201 replaces 741 PL#200 and 742 PL#101 replaces 742 PL#100. New SP stack kernels can be now downloaded from SAP Support Portal, following fixes are included:

• Regression in the Oracle DBSL Library (Note 2118448, Point 2 - Termination during secondary database connection; LRAW length error) is removed.
• CommonCryptoLib has been updated to the version 8.4.35 (see Note 2134460.)

For more details on 741 PL#201 refer to Notes 2150081 - SAP Support Package Stack Kernel 7.41 Patch Level 201 and 2100429 - Known regressions in kernel 7.41 patch level 201.

Fixes and enhancements in the SP stack kernel 742 PL#101 are listed in the note 2145156. Information on known issues with this stack kernel can be found in the Note 2134238.

19.03.2015: Update on SP Stack Kernels 741 PL#200 and 742 PL#100

The latest SP stack kernels 741 (PL#200) and 742 (PL#100) contain a regression in the Oracle DBSL Library, see Note 2118448 -Termination during secondary database connection; LRAW length error, Point 2.

As a solution you may use the latest ORA lib_dbsl available on SAP Support portal. For kernel 741 on Windows, please be aware of the issue 2142073 - Application server in Windows NT with Oracle does not start.

Updated stack kernels will be provided as soon as possible.

11.03.2015: SP Stack Kernel 721 PL#402 Released

SP Stack kernel 721 PL #402 has been released and can be downloaded from SAP Support Portal. The issues from PL#400 (Note 2118382) and PL#401 (Note 2138260) are fixed.

Refer to Note 2138680 - SAP Support Package Stack Kernel 7.21 (EXT) Patch Level 402 for overview of new features, enhancements and improvements added since PL#300. Known regressions are documented in Note 2138678.

09.03.2015: SP Stack Kernel 742 PL#100 Released

SP stack kernel 742 PL #100 is now available on SAP Support Portal. It contains various improvements and enhancements that are outlined in detail in Note 2136550.

Information on known issues in the stack kernel 742 PL #100 can be found in Note 2129327. This note will be updated on regular basis.

04.03.2015: SP Stack Kernel 721 PL#401 Revoked

SP Stack kernel 721 PL #401 has been revoked from SAP Support Portal for all platforms except for MS Windows because the kernel archives contained some files with wrong versions.

In most cases it is not necessary to replace the kernel in a system running with PL#401 because the issue has a limited impact and does not affect the kernel itself. Details are outlined in Note 2138260.

SP stack kernel PL#402 will be released as soon as possible; this document will be updated accordingly.

06.02.2015: SP Stack Kernel 741 PL#200 Released

A new SP stack kernel 741 PL #200 has been released today and can be downloaded from SAP Support Portal.

For a summary of enhancements and improvements included into this stack kernel, see SAP Note 2101802 - SAP Support Package Stack Kernel 7.41 Patch Level 200.

30.01.2015: SP Stack Kernel 721 PL#401 Replaces PL#400

Current SP stack kernel 721 PL#400 has been replaced with PL#401, see Note 2121693 - SAP Support Package Stack Kernel 7.21 (EXT) Patch Level 401.

It fixes a file permission issue that has a very limited impact:

• It occurs with 721_EXT kernel on Windows platforms only
• It has no effect at runtime, only for future system maintenance
• Workaround is easy.

This means: even if above criteria apply, it is not always necessary to replace already installed 721 kernel PL#400. Refer to Note 2118382 for more information.

Note 2084437 contains the list of known regressions in the stack kernel 721 PL #401. This note will be continuously updated.

16.12.2014: SP Stack Kernel 721 PL#400 Released

A new SP stack kernel 721 PL #400 is now available on SAP Service Marketplace.

SAP Note 2101779 contains the list of changes and enhancements introduced in this stack kernel compared to the previous stack kernel PL #300.

All regressions known in the PL #300 have been fixed.

Review SAP Note 2084436 for known issues in the stack kernel 721 PL #400. This note will be continuously updated.

Dear Experts,

We keep getting this warning on SM21 in all our systems : Could not send SLD data.

We are running SAP Netweaver 7.40 and Solution Manager 7.10.

The successful checks we have done this far are :

SLDCHECK

SLDAPICUST

RZ70

SLD_NUC & SLD_UC RFCs

We even updated the SAP HOST AGENT to the latest version and patch level (SAP HOST AGENT 7.21 SP13), but the warning persists. On LMDB is updating regularly.

Could you please give us pointers on other things we can check and try.

Thanks in advance,

Tebello Taole

Today I will present a scenario about SAL: use one directory to store all SAL files from all application servers in a SAP system.

As I mentioned in my previous blog, the most comprehensive document on SAL that I ever found, is available here: “Analysis and Recommended Settings of the Security Audit Log (SM19 / SM20)”.

My system landscape

For testing purposes, I will use a SAP Netweaver 7.31 system. It have the following hosts and instances:

Host A: ASCS01 and DVEBMGS00

Host B: D00 and D01

SAL configuration

I will set DIR_AUDIT to \\Host B\usr\sap\SID\Audit\ in all dialog instances from the system.

Additional parameters:

FN_AUDIT = audit_++++++++_######.AUD

rsau/max_diskspace/per_day = 1000M

rsau/max_diskspace/per_file = 100M

Thus, all SAL files will be recorded in a single directory, using the pattern above (given by FN_AUDIT). I expect multiple files per day, having each file 100 MB. The maximum disk space that can be used every day is 1000 MB.

In SM19 I decided to record all Audit classes in all clients for all user IDs.

Where are the entries?

Well, all the entries are recorded in the same file, for all application servers. You will find incorrect information in SM20:

As you can see, 1, 2 and 3 show the exact same entries, for the same User and same Terminal name (even though I omitted this information from the screenshot). The entries from 1 and 2 are from Host B, instances D00 and D01. The entries from 3 are from Host A, instance DVEBMGS00.

Solution

Set individual directories for SAL files. Each application server should write its own files in an exclusive directory.

So, in my landscape, fixing things means setting DIR_AUDIT in the instance profile, using:

SID_DVEBMGS00_HOSTA:

DIR_AUDIT = X:\usr\sap\SID\DVEBMGS00\log

SID_D00_HOSTB:

DIR_AUDIT = X:\usr\sap\SID\D00\log

SID_D01_HOSTB:

DIR_AUDIT = X:\usr\sap\SID\D01\log

Then I executed one transaction code in each app server, resulting in the following SM20 report:

Additional Information

539404 - FAQ: Answers to questions about the Security Audit Log

Stay tuned for my next blog on SAL.

Another scenario involving SAL: do you want to have a single SAL file created per day? Alternatively, do you want to have more than one file, limiting the file size and the total amount of space occupied per day?

Making myself tireless on spreading a good advice, the most comprehensive document on SAL that I ever found, is available here: “Analysis and Recommended Settings of the Security Audit Log (SM19 / SM20)”.

a) SAL configuration: a single file per day

The configuration is simple: just set:

FN_AUDIT = ++++++++.AUD

and:

rsau/max_diskspace/local = xxxxx

The unit used for the disk space is Bytes (if the number does not present a suffix), or k (or K) for Kilobytes, or m (or M) for Megabytes.

b) SAL configuration: multiple files per day

Similar to the configuration to have a single file per day, you have to set:

FN_AUDIT = audit_++++++++_######.AUD

and two additional parameters:

rsau/max_diskspace/per_file = xxxxx

rsau/max_diskspace/per_day = yyyyy

Where xxxxx < yyyyy. The unit used for the disk space is the same as above.

Note that the mask in FN_AUDIT now contains ######, which will be replaced by a sequential number, i.e. a new number as soon as the file have reached the permitted file size. The new number is used to create the new SAL file.

c) SAL configuration: mixing things with odd results

I already saw cases where a configuration like this was used:

FN_AUDIT = audit_++++++++_######.AUD

rsau/max_diskspace/local = zzzzz

rsau/max_diskspace/per_file = xxxxx

rsau/max_diskspace/per_day = yyyyy

In such case, the configuration is not correct. It is not possible have a single file and multiple files, using a specific FN_AUDIT value.

Using SM20 in such case can bring a result like:

Even though there are SAL entries recorded in the files.

The solution is simple: use a) or b). Option c) is not valid - and can give you headaches.

Additional Information

539404 - FAQ: Answers to questions about the Security Audit Log

875835 - SecAudit: Analysis finds no audit events

909738 - SecAudit: Files are created with other names

Stay tuned for my last blog on SAL.

Hi Experts,

We (Our Infrastructure team) recently changed our SAP router public IP,

By this time the status of SAP Router at SMP is not stable.

for 20min it is saying "Host did not respond 1,2,.. times" for some time status is "cancelled".

Even though SAP AG can access our SAP systems.

Could you please check and help do we need to change any setting anywhere.

thanks,

Sreenivas.

Dear All,

     We are facing problem in printing in the WEP HQ 2650 Printer (Heavy Duty Dot Matrix). The problem is mainly with SWIN Output Device type & Page Format. The printing is coming in X_65_80 &  X_90_120 correctly but not in higher formats like X_120_150 which are desired.

Is there any better way to print in the model mentioned.

In anticipation of your reply.

Hi

I am trying to implement best practices pharmaceutical within the latest ERP 6.0 system with Enhancement Package 8.

Can anybody suggest simple steps instead of reading lengthy documents?

I mean, How to import the best practice technical settings within the ERP system. is it same way as installing add-ons using SAINT t-code?

Reply with simple steps would be great help.

Best regards

Raj

Hello!

I have installed SAP NetWeaver Composition Environment 7.1 SR5 Evalution SDN Version on a windows xp machine.

Included is the J2EE Application Server and the MaxDB.

I have done a standard installation (no adjustments)

When I try to start the Application Server with the management console it does not work.

The DB is running and I can log on via management console. I can connect to the database with the config tool.

Tha app server starts but in status it says "Some processes running [Safe Mode]" (yellow symbol)

With in the management console I see under "AS Java Process Table" that the process server0 has not started.

The trace file states:

J Wed Jul 22 15:21:50 2009

J  [GC [ParNew: 9808K->2872K(10944K), 0.0070266 secs] 12456K->5521K(127488K), 0.0071551 secs]

F 

F [Thr 4016] Wed Jul 22 15:21:51 2009

F  [Thr 4016] *** LOG => SfCJavaVm: exit hook is called. (rc = -1501)

F  [Thr 4016] *** LOG => exiting (exitcode -1501, retcode 2).

M  [Thr 4016] CCMS: CCMS Monitoring Cleanup finished successfully.

Afterwards the server stops.

Does anyone have an idea what exitcode -1501 means?? I haven't found anything in these forums.

I checked the other logs but there were no errors.

Thanks in advance,

Jens

Imagine the scenario where your system was migrated from one server to another. The OS used was changed. In order to keep SAL data, you have moved SAL files from the original system to the new system. However, you have no results in your SM20 reports. What happened? How to resolve this issue?

Big versus Little?

Usually the code page from the server changed. You may also have changed from a big endian system to a little endian one, from your favorite Unix flavor to your favorite Linux flavor (or vice-versa). You can read more about what “endian” means in SAP note 552464.

You can use transaction code I18N to view the current internationalization system configuration:

Then you can find the code page of your system. In my test system, it is 4103 (Windows Server).

My source system have code page 4102 (AIX). Yes, you need to check the I18N system configuration in both systems, so you have the correct code pages.

The issue: moving one SAL file from the source system to the new system, and reading the file via report RSAU_SELECT_EVENTS shows:

The file size is more than 20 Megabytes and no entry found? Who would think that a simple code page change would cause such effect!

How to resolve the issue?

The short version: file conversion.

The long version: use report RSCP_CONVERT_FILE. It allows you to specify source and target code pages, specify the location of the files.

Note that you need to specify one file that contains the list of files that should be converted.

My file “list.txt” holds the list of files that I want to convert. For test purposes, I just put a single row in the list.

The input screen is this one:

The result of the file conversion:

Now, the result of RSAU_SELECT_EVENTS:

Additional Information

539404 - FAQ: Answers to questions about the Security Audit Log

747615 - Tool for converting files from one code page to another

752859 - sapiconv - a tool for converting the encoding of files

Do not miss the most comprehensive document on SAL that I ever found, available here: “Analysis and Recommended Settings of the Security Audit Log (SM19 / SM20)”.

If you have missed my previous blogs on SAL:

• Security Audit Log (SAL): No UNC, No NFS mounts
• Security Audit Log (SAL): One directory for all SAL files
• Security Audit Log (SAL): Single file or Multiple Files?

Stay tuned for my next blog series on… surprise, surprise!

Hi, all

I am trying to upgrade the BW server from 7.3.1 to 7.5 on windows 2008R2. DB is oracle.

According to the some links I found, I upgraded the hostagent to the latest level and from user sidadm, I ran d:\SUM\STARTUP.BAT confighostagent SB7. SB7 is the BW SID and d:\SUM is where I extracted the SUM package into. All working.

When I connect, with url http://hostname:1128/lmsl/.... I get HTTP 500.

Looking at the dev_saphostexec, I see error:

Looking at sapstartsrv.log :

Sorry, cut and paste doesn't work for me on SDN so I have to paste the picture. I still hate this SDN web layout even though they put it in 5 years ago. Anyhow, the services saphostcontrol and saphostexec are run under "SYSTEM".

Any of your help is much appreciated.

Thanks,

Jonathan.

Imagine the scenario where your system was migrated from one server to another. The OS used was changed. In order to keep SAL data, you have moved SAL files from the original system to the new system. However, you have no results in your SM20 reports. What happened? How to resolve this issue?

Big versus Little?

Usually the code page from the server changed. You may also have changed from a big endian system to a little endian one, from your favorite Unix flavor to your favorite Linux flavor (or vice-versa). You can read more about what “endian” means in SAP note 552464.

You can use transaction code I18N to view the current internationalization system configuration:

Then you can find the code page of your system. In my test system, it is 4103 (Windows Server).

My source system have code page 4102 (AIX). Yes, you need to check the I18N system configuration in both systems, so you have the correct code pages.

The issue: moving one SAL file from the source system to the new system, and reading the file via report RSAU_SELECT_EVENTS shows:

The file size is more than 20 Megabytes and no entry found? Who would think that a simple code page change would cause such effect!

How to resolve the issue?

The short version: file conversion.

The long version: use report RSCP_CONVERT_FILE. It allows you to specify source and target code pages, specify the location of the files.

Note that you need to specify one file that contains the list of files that should be converted.

My file “list.txt” holds the list of files that I want to convert. For test purposes, I just put a single row in the list.

The input screen is this one:

The result of the file conversion:

Now, the result of RSAU_SELECT_EVENTS:

Additional Information

539404 - FAQ: Answers to questions about the Security Audit Log

747615 - Tool for converting files from one code page to another

752859 - sapiconv - a tool for converting the encoding of files

Do not miss the most comprehensive document on SAL that I ever found, available here: “Analysis and Recommended Settings of the Security Audit Log (SM19 / SM20)”.

If you have missed my previous blogs on SAL:

• Security Audit Log (SAL): No UNC, No NFS mounts
• Security Audit Log (SAL): One directory for all SAL files
• Security Audit Log (SAL): Single file or Multiple Files?

Stay tuned for my next blog series on… surprise, surprise!

Dear SAP Basis Gurus and SAP Abap Gurus,

I am executing a sap report to create business partner in SAP CRM system. Now i have used parallel processing methodology in this report for business partner creation.

This report works fine with 80% of total dialogue processors in the system(quality/development/testing sap servers) used with multiple batch jobs in parallel (example if total dialogue processes in system is 100 then i schedule this report with 10 batch jobs and 8 dialogue processor per batch job).

But in production system we have 12 application servers with (150 dialogue processors, 20 update 1, 10 update 2 and 30 batch processes) per application server. So total resource is

dialogue processor : 1800

update 1: 240

update 2 : 120

batch jobs available: 360

Now i am scheduling the business partner creation report with 84 batch jobs and assigned 17 dialogue processor per batch job.

But only 7-8 jobs are remaining active after scheduling and updating the database creating customer and rest of the jobs are finished in 1 second without updating anything (note: there is nothing wrong with data creation as we write application log for error while data creation and nothing has come up in application log). Now i reprocesses the rest of the batch jobs which completed in 1 second earlier and didn't update, again 7-8 jobs are remaining active and creating business partner and rest of them are finished in 1 second and so on.

This report is working fine in other sap systems like quality/development/testing, and this problem is only happening in production.

I am not at all familiar with basis configurations, So kindly help me out with this issue.

Thanks for your help

Sudipto