SAP Content Server 6.40 and MaxDB 7.7.04.28

In PAM (service marketplace) it says that CS 6.40 is not supported with MaxDB 7.7.
I talked with SAP about it. They say:
"SAP is planning to release 7.7 to all customers in Q1 / 2010"
So I decided to instal MaxDB 7.7.04.28 and do an upgrade / migration test.

The upgrade went fine, and so did the migration.
The OS is Windows Server 2003 64 bit.
After migrating I did some tests. I recomand to do all these tests when you are planning to use Content Server or if you want to be sure that the migration was a success:

1. Create a Content Repository in CSADMIN.
Information you type into CSADMIN about the Content Repository will be saved in contentserver.ini
2. Test connection to the new Content Repository from transaction oac0
3. Send certificat from the new Content Repository from transaction oac0
4. Be sure the status for the CR is running (not defined - ref earlier post)
5. Try to read from the Content Server through your ECC-system. In my case I called an invoice and viewed the image-file
6. Try to upload something to the Content Server from your ECC-system.
To do this you can use function module ARCHIVOBJECT_CREATE_FILE

Number 1-5 is working just fine, but I have problems uploading a new image-file to the Content Server.
When I do an upload-test I receive no ARCHIVE_DOC_ID. Just this error message:
"http error: 500 (Internal serverError) ;ODBC State 00000"
The ODBC is just fine so it have to be something else. SAP is working with this case. I'll update you as soon as I know anything more.

07.01.2010:
Now I know something more:)
Just remove the ODBC for MaxDB 7.7 and install ODBC-driver 7.6. This solves the problem:)

"Downgrade" MaxDB

I have a little problem.

Need to "downgrade" a MaxDB 7.7 to 7.6. Anybody who have experience with this kind of work?

This is what I've done:

-Removed MaxDB 7.7 and droped the database
-Installed new database version 7.6 and created the db-instance

I have a complete backup from MaxDB 7.7 (Content Server) that I want to recover into MaxDB 7.6.

-Why do you have to do this? you may ask.
Answer: I did not look into PAM before upgrading my Content Server and MaxDB. Content Server 6.40 supports only MaxDB 7.6 - not 7.7. The upgrade went fine, but I get problems when migrating to new hardware/installation.

UPDATE at 14. december 2009. Message from SAP:
SAP is planning to release 7.7 to all customers in Q1 / 2010therefore there you do not have to downgrade to 7.6.

Screen generation - Incorrect DYNP version

My co-worker (Thomas Lyshagen or John Bjerke) solved this issue.

This is about a popup-message in sapgui:

"Screen generation RSSHOWRABAX 0100: Incorrect DYNP version"

1. Go to se38 and type in programname "rsgenerate"
2. Execute
3. In field "modules" you enter the name from the popup. In my case: RSSHOWRABAX
4. Leave the field "DYNPRO" empty and execute
You will receive a message like this:

Delete a SAP Client

There is of course more than one way to delete a SAP Client.

Here is one of them:

1. Log into the client you want to delete
2. Enter transaction SCC5
3. Choose "Delete entry from T000". If you don't choose to delete entry from T000 you will have to enter transaction SCC4 from a different client and delete the entry.
Start immediate or schedule a background job.
4. Reorg database.

Start Content Repository for Content Server

You have to start the Content Repository if the repository status is "defined" in transaction CSADMIN.

To start it you have to push butten for start. On the start butten you have an image of a padlock that is unlocked. I find it funny:)

Here is what you have to do to start Content Repository:

1. Transaction CSADMIN

2. Choose Content Repository and press "enter"

3. In the Content Server Admin-window you have to select "Details" and then "Display <-> Change"

4. Then push the butten with image of the padlock that is in status unlocked:

Shordump DBIF_RSQL_INVALID_REQUEST

Here is some info from the shordump:

Short text
Invalid request.
What happened?
The current ABAP/4 program terminated due to an internal error in the database interface.
What can you do?
Note which actions and input led to the error.
For further help in handling the problem, contact your SAP administrator
You can use the ABAP dump analysis transaction ST22 to view and manage termination messages, in particular for long term reference.
Error analysis
An invalid request was made to the SAP database interface in a statement in which the table "EDID4 " was accessed.

Keywords
"DBIF_RSQL_INVALID_REQUEST"
"SAPLEDI1" or "LEDI1F09"
"F09_IDOC_INSERT_WITH_NUMBER"

The Keywords did confuse me a bit. This shortdump recommend to check transaction SM21. Thats a very importen clue. Remember to check more than just the red lights in SM21.
Under a warning in SM21 I found this information:
ORA-01653: unable to extend table SAPR3.EDI40 by 46075 in tablespace PSAPCLUD
So the answer is to extend tablespace PSAPCLUD.






I had over 400MB of free space in the mentioned tablespace. It was 95% full.
I did not think it was a problem related to tablespace. Anyway.... a shortdump with the header "DBIF_RSQL_INVALID_REQUEST" can be a tablespace-problem even if the keywords indicate something else.
Please send me a message if you need help to extend tablespace (harald.v@epost.no).

Picture is from: http://img.pte.at/lowrespics/1096894834i23327.jpg
I love sap-commercial ;)

Shordump START_CALL_SICK - CPU timers not synchronized

After patching our Kernel for ECC 6.0 til patch 221 we receive shortdumps when logging in:

START_CALL_SICK
Short text

Database inconsistency: Start Transaction SICK.

What happened?
The current program had to be terminated because of an error when installing the R/3 System. The error occurred when initializing the R/3 System.

Remember to read whole text in this shordump beacuse you often find the answer in there:

Error analysis
The error probably occurred when installing the R/3 system. Error text of the first reported error: "CPU timers not synchronized. Check note 1036194.".

Follow what is written in this note and you will solve this issue.

You have to enter the text that have an underline in this image.


PS: This message is posted by my friend John Bjerke.

CSADMIN - Content Repository prompt you for user and password

After installing Content Server successfully and created Content Repository I still get prompt for user and password when entering transaction CSADMIN - Choosing Content Rep.
This is because I have not activated the certificate.


Solution:
1. Go to transaction CSADMIN and choose your Content Repository
2. When you are prompt for user and password you have to enter the OS-user on host for the Content Server - hit OK.
3. Choose folder "Certificates" in Content Server Administration (CSADMIN).
4. Change into "change mode":






5. Select the line where the certificate is and choose "Activate":







The next time you enter CSADMIN you will not be prompted for user and password:)

Remember that the DB must be up and running. Try with DB manager if you still have problems.

Delete background jobs older than 30 days

As default SAP delete background jobs that is older than 10 days. You'll find the standard jobs in SM36 - Standard Jobs.
You will see that the job SAP_REORG_JOBS delete old jobs. This job uses program RSBTCDEL with variant SAP&001. You are not able to change this variant. Even if your user have SAP_ALL- and SAP_NEW-authorization.
You have to make a new variant if you want to delete jobs that is older than 30 days.

This is how you can solve this issue after scheduling the standard job:

1. Go to SE38 and enter program RSBTCDEL
2. Select "Variants" and choose "Change"
3. In the "Variant"-field you have to select "SAP&001"
4. Then choose "Variants" in the menu top left corner and then "Copy". Copy the variant into a new name that you desire:)











5. Make the value-change for the new variant. "Older than days" = 30. Save and close.
6. In the end you have to change the released job SAP_REORG_JOBS. You can do this in SM37. Remember to set the job from released to scheduled before changing.

I guess it's more than one way to solve this issue. Maybe someone knows how to change the original variant?

R3TRFORMZZMEDRUCK original object cannot be replaced

Import of transport request ended with error.

Log file will tell you that original object cannot be replaced.
SAP will also provide you with a procedure to solve this:
If you still want to import the object, repeat the import with Unconditional Mode 2.

"Unconditional modes" is that you can override the rules of the transport system.
Import your request with option "Overwrite originals" is one of the unconditional modes.

HW-certification for SAP - Windows

Here is a usefull link if you are going to bay new hardware for your sap-application:
http://www.saponwin.com/

VMware:

Up until recently, to run SAP on VMware ESX on a given server, the server vendor had to do an additional certification specifically for VMware ESX. These certifications were published as SAP Benchmarks on http://www.sap.com/benchmark. In January, SAP agreed to remove this additional certification. This change was announced in the Benchmark Council in February. From now on, any server is supported that is

a.) on the VMware Hardware Compatibility List (http://www.vmware.com/resources/guides.html) AND !
b.) on the SAP certified hardware list, maintained at http://www.saponwin.com/

This info is taken from:

http://communities.vmware.com/blogs/SAPsolutions/2008/04/30/sap-hardware-certification-for-vmware-esx

Installing SAProuter with SNC connection on Windows

Here is my guide to install SAProuter with SNC for connection to SAP.
Hopefully you'll find it helpful.

Secure Network Communications:

Figure is taken from service marketplace and the saprouter-guide.

1. Register SAProuter at service marketplace. Send an oss-message with component XX-SER-NET-NEW to SAP. You have to attach "Remote Connection Data Sheet" to this oss-message (note 28976).
2. Download SAPSECULIB and SAPCRYPTO from service marketplace.
You'll find SAPSECULIB under Download - SAP support Packages - Entry by application group - SAP Technology Components.
You'll find SAPCRYPTO here:
https://websmp203.sap-ag.de/~form/handler?_APP=00200682500000000917&_EVENT=I_AGREE&_SWFOLDER=
3. Download SAPROUTER from service marketplace.
You'll find it under Download - SAP support Packages - Entry by application group - SAP Technology Components.
In my case I had to download version 7.00 because I could not find 7.10 for 32-bit Windows.
4. Create directory "saprouter" at your saprouter-host. In this example I created \usr\sap\saprouter.
5. Uncar your saprouter-file and copy saprouter.exe and niping.exe into your saprouter-folder (\usr\sap\saprouter).
6. Check if you can find ntscmgr.exe in the windows\system32-folder. If it's not there - find it and copy.
7. Create saprouter as an service.
Example: ntscmgr install SAProuter -b E:\usr\sap\saprouter\saprouter.exe -p "service -r -R E:\usr\sap\saprouter\saprouttab -S 3299"
8. Set saprouter-service to "Automatic" and user "adm".
9. Create key "saprouter" under
HKEY_LOCAL_MACHINE → SYSTEM → CurrentControlSet → Services → Event Log → Application
Then this values:
EventMessageFile (REG_SZ): ....\saprouter\saprouter.exe
TypesSupported (REG_DWORD): 0x7
10. Check if you can find MSVCR71.DLL and MSVCP71.dll in your system32-folder.
11. Download MS Runtime DLL attached to note 684106 (r3dllinst.zip). Unzip and run R3DLLINS.EXE from \NTPATCH - restart if necessary.
12. Uncar SECULIB and copy files from nt-i386 (if 32-bit windows) into \usr\sap\saprouter folder.
Uncar SAPCRYPTOLIB and copy files from \ntintel into \usr\sap\saprouter. You also have to copy files directly from the uncared SAPCRYPTOLIB-folder (files as ticket) into \usr\sap\saprouter.
13. Create environment variables for user:
SECUDIR = E:\usr\sap\saprouter
PATH = E:\usr\sap\saprouter
SNC_LIB = E:\sap\saprouter\sapcrypto.dll
14. Go to service marketplace:
https://websmp201.sap-ag.de/SAPROUTER-SNCADD
Press Apply Now!
You'll receive some data. Save it and copy the Distinguished Name.
Press Continue.
15. Open dos-command at your saprouter-host and type:
sapgenpse get_pse -v -r certreq -p local.pse ""
Just press "Enter" twice if you have to enter PIN.
16. Files local.pse and certreq is now created in saprouter-folder.
Open file certreq in notepad and copy the content.
17. Go back to service marketplace (window from nr. 14) and paste the content from certreq there. Press Request Certificate.
You will then receive your certificate.
18. Copy your certificate into notepad at your saprouter-host. Save this notepad-file as srcert in your saprouter-folder.
19. Open dos-command and import the certificate:
sapgenpse import_own_cert -c srcert -p local.pse
20. Create credentials. Open dos-command and type:
sapgenpse seclogin -p local.pse
21. Verify the import of the certificate. Open dos-command and type:
sapgenpse get_my_name -v -n Issuer
Everything should be ok.
22. Create a file called saprouttab in your saprouter-folder and enter thise entries:
KT "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 194.39.131.34 *
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" *
P 194.39.131.34 3299
23. Go into registry at your saprouter-host.
HKEY_LOCAL_MACHINE - SYSTEM - ControlSet001 - Services - SAProuter
Modify string ImagePath.
It should look like this:
E:\usr\sap\saprouter\saprouter.exe service -r -R E:\usr\sap\saprouter\saprouttab -S 3299 -K "p:"
24. Start saprouter-service
25. Open port 3299, 3200 between SAP and your saprouter.
26. Create RFC in SM59. If you need some help with this let me know.

Upgrade and migrate ContentServer with MAXDB - v2

It seems that I have been worrying too much.


Created a snapshot of my ContentServer and successfully upgraded to maxdb 7.7.00.28.

I had no experience with CS or MAXDB, but with Database Manager it's pretty easy to handle:)

Upgrade and migrate ContentServer with MAXDB

I have tried to figure out how to solve this issue, but I find it hard.
The problem is that we do not have any dev- or qa-system to practice on.

I had to migrate the system anyway because of the hardware. I moved it to a vmware-client to by me some time . It's easier to do a roll back on vmware.
Now I want to migrate it to a new server (not vmware).

Source System:
SAPDB 7.3.0.35 - 32bit windows
Target System:
MAXDB 7.7 - 64bit windows

Note 962019 is very important!
Here is some prerequisites with my answers:
- In your source system, you use SAPDB Kernel Version 7.3.00 Build 57 (PTS 1143300) or higher, or MaxDB Kernel Version 7.5.00 Build 40 (PTS 1143301) or 7.6.00 Build 31 or higher.
My answer: NO, I use 7.3.0.35
-If the minimum required version 7.3.00 Build 57 is not yet available on the SAP Service Marketplace, you must first upgrade the Content Server Version 7.3. to Version 7.5.00 Build 40 before you can execute a heterogeneous system copy.
My answer: 7.3.00 Build 57 is NOT available and have never been. The same for version 7.5.00 Build 40.

So what can I do?
In point 4 (note 962019) it says:
- In your source system, you use SAPDB Kernel Version 7.3.00 Build 57 (PTS 1143300) or higher, or MaxDB Kernel Version 7.5.00 Build 40 (PTS 1143301) or 7.6.00 Build 31 or higher.

The conclusion is that I have to upgrade my source system to 7.6.00 Build 31 or higher....

Now I'm going to make som pancakes for my family. Continue in a few days!

SQL error in the database when accessing a table

I received this message when I tried to logon to my ECC 6.0 system (IDES):
"SQL error in the database when accessing a table"

It's a mssql 2005 database and windows 2003 server.
Usually you have to focus on the table causes the problem, but in this scenario the db-disk was full.
Increase the db-disk or move db-files to an empty partition.
Do you need help with moving db-files please let me know.

PS! Did you know that SAP loves Formula 1?
This picture is from http://www.flickr.com/photos/mosokul/194054577/
and shows a McLaren formula 1 car.

Shortdump DYNPRO_ITAB_ERROR after systemcopy

I receive this shortdump when I try to logon after a homogeneous system copy (DB-independent, using sapinst).
This is an ECC 6.0 system and the solution for me was to upgrade Kernel.
Fortunately I made a copy of \usr\sap\SID\sys\exe\run-folder before I imported the system copy at my target system. I could use this copy as my new kernel after finishing the import.
Kernel Patchno 144 is installed during system copy import (db-independent - SR3).

Here is some more details from my shortdump:
Runtime Errors DYNPRO_ITAB_ERROR
Date and Time 2009-07-16 08:18:21

Short text
Error in internal table in screen

What happened?
The current screen processing action was terminated since a situation
occurred where the application could not continue.
This is probably due to an error in the ABAP program or in the current
screen.

Error analysis
The program "SAPMSYST" has terminated.

The following error occurred (short text of cause of error):
"FX099: Wrong fieldtype for CURSOR. Has to be binary/hex type."

The following elements are affected:
Screen name.............. "SAPMSYST"
Screen number............ 0020

This error is connected to the processing of an internal table with the
field or variable "TC_IUSRACL-CURRENT_LINE", and was triggered within in the program.

Trigger Location of Runtime Error
Program SAPMSYST
Include SAPMSYST
Row 1,076
Module type (MODULE PBO)
Module Name D020_LOGON_WITH_SNC

Name or password is incorrect (repeat logon)

You get this message "Name or password is incorrect (repeat logon)" when doing an authorization test for RFC on to ERP2005 or higher. You are using a SAPgui controls that cannot handle case-sensitive passwords. The SAPgui controls convert the password into upper_case.
I experienced this problem for my RFC from BW (BIWREMOTE) into ERP2005.
Solution: Change the password for this user in the target system (the system you try to reach) to only upper-case. Another solution is to install the absolut latest of SAPGui. I have 7.10, but still got this problem....

OB52 - Not modifiable in QA system

You have the possibility to do changes when you access OB52 in Production system.
But when you access transaction OB52 in the QA system you receive this message:
Client 100 has status 'not modifiable'

Reason: In SCC4 the Client Role for this client in QA system is set to "Test". If you change it into "Production" you will have possibility to do changes in OB52 (S_ALR_87003642). Remember to change it back when you are finished.

Another solution is described in note 214132. But this solution was no good for me.

Instance shuts down - paging file too small

Our hosting-partner had some trouble with some SCSI-drivers who lead to disconnection from some of the harddrives.
Our db-disk and sap-disk was harmed.

When the problem was fixed we got problems starting one of our two SAP-instances.

At first both instances went green with the text:
"Running, Message Server connection ok"
But this status changed after some minutes:
"Running but not connected to Message Server"
And then the status changed into:
"Stopped"

I did not find any answers in the log-files (\usr\sap\sid\DVEBM0000\work).
The answer was in the event-viewer.





















[CreateOsShm] CreateFileMapping(6,450000 KB) failed with Err=1455 ERROR_COMMITMENT_LIMIT: The paging file is too small for this operation to complete.

Solution was to set the paging file again.

Shortdump DBIF_REPO_SQL_ERROR

Text in shortdump ST22:
Short text: SQL error 1654 occurred when accessing program
How to correct the error: Database error text........: "ORA-01654: unable to extend index SAPR3.D010TAB~0 by 128 in tablespace PSAPES700I"

This is basic understanding of an oracle-database. Tablespace is full. In this case it's PSAPES700I. Extend with brtools:
http://help.sap.com/saphelp_nw70/helpdata/en/1b/d20f6fe45a9e43b1856ea1b52c9612/content.htm
If you are using the old sap-tool "sapdba" insted of BRTOOLS you can email me (harald.v@epost.no) and I'll help you with the tablespace-extention.

(Photo: http://www.made-in-china.com/)

Shortdump CALL_FUNCTION_NOT_FOUND

The short text in this shortdump is:
Function module "ANLBZW_CREATE_TRANSFER" not found.

The solution for this was in my case note 1276128.
You have to maintain view TRWPR and delete an entry containing function module ANLBZW_CREATE_TRANSFER.
Attached to note 1095424 you will find a script for this action.

CANNOT_CREATE_COFILE during SPAM queue

This is usually solved by:
1. Check authorization for cofiles-folder (sidadm and servicesidadm)
2. Download the affected support package again. It can be corrupted
3. Any full tablespaces?

If you look into SLOG and find this error message:
WARNING: \\\sapmnt\trans\tmp\SAPKKB70014.ARP is already in use (10), I'm waiting 4 sec (20090515192357). My name: pid 7280 on (APServiceARP)

In my case the problem was corrupt support package. I downloaded the package, deleted the cofile and the datafile. Remember to also delete the pending transport request that you will find int the trans\tmp-folder.

Maybe my father is a war-hero;)

I promised you to not only write about SAP, but try to combine that with family. Here is something about my life..... or my fathers life.
I have written an article about him (John Vedvik). I focus on one special incident in 1943 where my father went against the Germans. He was only 9 years old at the time. It's in Norwegian and on my norwegian blog-site: http://rusle.blogg.no/1242204244_min_egen_max_manus.html

Photo is taken by Kjetil Simonsen pixelphoto.no.

What is BI Business Process Management?

My good friend and colleague in CIBER, Pål Risberg, just wrote an interesting article with the subject: "What is BI Business Process Management?".
It's in Norwegian, but if you want it in english or have other questions you can just ask him at pal.risberg@ciber.com.

Change your life and become a SAP Consultant

I found this link at Daniel Toba's blogspot:

http://www.sapforall.net
This is a community for people wanting to pursue a career as SAP consultant.

Migration of SAP Content Server

Migration of SAP Content Server 6.40 from 32 bit to AMD64 for Norwegian Air Shuttle AS (http://www.norwegian.com/).
At first I installed MAXDB 7.6.04.16 as my target database.
Source database is 7.3.0.35.
I recommend to read note 649814 and 962019 first.
There you will see that you have to install MAXDB 7.6.05 build 11 or higher at your target-system.
Note 962019:
Note that the target system must be installed at least with 7.6.05 build 11. An upgrade to this version does not help.

Uninstall the old target-system:
1. Uninstall Content Server with Add/Remove Programs
2. Stop MAXDB-instance:
dbmcli -d -u , db_offline
3. Delete MAXDB-instance:
dbmcli -d -u , db_drop
4. Uninstall MAXDB with Add/Remove Programs

Install SAP Content Server 6.40 with MAXDB 7.7.* for x64
CDLABEL.ASC=MAXDB7.7.04 Build 28RDBMSNumber 51035704.
Remember to configure the IIS
Create Repository in CSADMIN

The Migration is a Heterogeneouse system copy.
Actions at source-system:
1. Check Data ->
Database Manager - Instance - Check - Database Structure
2. Create Index (ony for Kernel version 7.3 and 7.5) ->
Database Manager - Tools - SQL Studio
----more will follow------

THIS DOES NOT WORK!!!! I'll try again later.

My first blogging-day

Hello dear friends and enemies!

This is me and my oldest son. He was 1 year old at the time this picture was taken. He is now 2,5 years old. In desember 2008 my wife and me had twins. A boy and a girl. They are 5 months old now.
So you can imagine that it's a hectic time in our home

This is my first day as a blogger. Mainly I'll write about my profession as an SAP Basis Consultent at CIBER in Norway, but this is something that also affects my private life. So - I will write about both subjects;)

I also want to use this opertunity to improve my english. So you have to excuse me if you find some bad spelling or grammar.