Skip to Content
author's profile photo Former Member
Former Member

Strange error with libicudata26.so during Kernel upgrade on AIX

Dears,

during an Sap kernel upgrade for sap ERP 2004, based on was 640, I foud this error unpaching the file SAPEXE_347-10004775.SAR:

"..

..

SAPCAR: could not open for writing libicudata26.so (error 28). Text file busy

..

"

I renamed the file libicudata26.so (it's a kind of error often occurs on Unix) and rerun the unpacking of the SAP file but this time I have this error :

"

Could not open the ICU common library.

The following files must be in the path described by

the environment variable "LIBPATH":

libicuuc26.so, libicudata26.so, libicui18n26.so [nlsui0.c 1457] pid = 6815972

Terminating.

You may set the environment variable NLSUI_7BIT_FALLBACK to run the program

without the ICU libraries in an emergency mode. [nlsui0.c 1205] pid = 6815972

"

Then if I move back the file libicudata26.so I get again the error :

"SAPCAR: could not open for writing libicudata26.so (error 28). Text file busy"

Any advise ?

The environment of the sidadm user used to unpack the SAR file is correct. The LIBPATH is in place.

AT the time the unpacking was running the Sap system was closed and the saposcol stopped and deleted as for Sap procedure.

Usually it's enought to rename the file busy and then it works; why this time the system complains about "........missing ICU common library " ?

best regards

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Best Answer
    Posted on Apr 19, 2011 at 04:57 PM

    > during an Sap kernel upgrade for sap ERP 2004, based on was 640, I foud this error unpaching the file SAPEXE_347-10004775.SAR:

    >

    > "..

    > ..

    > SAPCAR: could not open for writing libicudata26.so (error 28). Text file busy

    Make sure all the files are unpacked.

    Starting with 6.40 there is a service running (sapstartsrv), in case of a Unicode system this process will also keep the file busy.

    Markus

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.