This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
See this idea on ideas.ibm.com
Product: AIX 6.1 and 7.1
Java v6 and v7
Oracle 12
PROBLEM: Client Ricoh is using Oracles new "hot patching" feature via distributed NFS. This process runs 64 bit Java programs in the NFS mountpoint for the hot patching. The execution of java commands within the NFS mountpoint loads shared libraries. When subsequent attempts to remove the directories which were used as temporary working space during the install are run, the "rm" fails, because file are renamed as .nfs###. This is due to the fact that the shared libraries are still loaded, per design.
EXAMPLE OF ERROR Encountered by Oracle hot patching -
rm: 0653-611 Directory t2pjdk_old/jre/lib/ppc64/j9vm is not empty.
rm: 0653-611 Directory t2pjdk_old/jre/lib/ppc64 is not empty.
rm: 0653-611 Directory t2pjdk_old/jre/lib is not empty.
rm: 0653-611 Directory t2pjdk_old/jre is not empty.
rm: 0653-611 Directory t2pjdk_old is not empty.
Files with the following naming convention are found in the directories -.nfs### .nfs### etc
The .nfsXXXX files for the deleted shared library cannot be removed from the client side.
The .nfsXXXX files can be deleted on the server side.
WORK AROUND:
Run "slibclean" prior to removing the files. This is problematic, because Oracle installation does not run as root. Oracle install cannot call slibclean prior to every "rm" command.
ORACLES ONLY CURRENT SOLUTION: Use sudo to run "slibclean" in a loop for the duration of the hot patching activity -
++++++++++++++++
script_torun_slibclean.sh:
#!/bin/bash
while true
do
sudo /usr/sbin/slibclean
sleep 5
done
++++++++++++++++
REQUESTED SOLUTION:
From either AIX, or JAVA, provide an Env variable similar to that available for 32 bit Java, that will allow the loading of the segments privately, preventing them being loaded as shared libraries.
Similar to the following avail for 32 bit-
If using MAXDATA -
$ export LDR_CNTRL=PRIVSEG_LOADS@MAXDATA=0xB0000000@DSA
.
If not -
$ export LDR_CNTRL=PRIVSEG_LOADS
Idea priority | Urgent |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
The workaround implemented by the customer was to run slibclean
multiple times to force the shared library cache to be cleaned.
In many cases, a single slibclean may be adequate, but because NFS
introduces these .nfsXXX files that keeps references to the libraries
active longer than when not using NFS, there is the need to run
multiple slibclean.
Also, Oracle may be able to tweat the permissions and ownership
of their embedded Java installation shared library files that could
force the libraries in the private area and not loaded as shared libraries.
This is my understanding from your explanation. Please confirm the same.
As per your explanation, after loading shared library you have renamed it. Renaming is allowed.
Now you are trying to remove the directories, which are used as temporary working space,
Then the expected behavior is that "rm" SHOULD FAIL. Removing the files with a original name, which are already renamed, is bound to fail.
Am still not clear with the understanding of the above query so I have the following questions
This renaming is only done for 64-bit?
Is there any renaming for 32-bit ?
What is the necessity for renaming?
Creating a new RFE based on Community RFE #72138 in product IBM AIX.