PATCHING OES ???

Hi,
i have installed OES.10.1.4.3.0_admin_win32.exe on windows 2003 platform, using Tomcat 5.5.25. While creating web-service SSM instance, config tool was not working well. It showed 'creating an instance' message and hanged. Later i created the web-service SSM instance using wizard. Lot of settings need to be done in the admin console if the instance was created using wizard.
Then I created IIS web server SSM instance using wizard. While performing the steps for environmental binding of IIS with plug-in file - wles_isapi.dl, the ISAPI filters status showed red arrow instead of green arrow.
Is there any flaw in the configtool (config.bat file) ? Do i need to patch OES using cumulative patches 1 or 2 ?
Which patch do i need to download and what will be the sequence of steps to be followed ?
I have OES admin and SSM installed. Do i need to re-install the two and then install the patches?
Regards,
Chhavi Saluja

It sounds like you've had a run of bad luck.
The config wizard is the older way to create security module instances and, as you've noted, requires quite a few manual steps. The ConfigTool is the new and nifty way to create instances and it automatically creates the necessary configuration on the admin side of the house. Unless you have a good reason to use the wizard you should probably avoid it and just use the ConfigTool.
I always recommend using the latest Cumulative Patch, so I'd try with CP2. If you run into trouble you can always back out and move to CP1 or remove the patch and be back at the base version.
Remember to apply the admin patch before applying the security module patch.

Similar Messages

PROBLEM IN OES INSTALLATION

Hi,
I installed OES succesfully.
platform : Tomcat 5.5.25
while creating SSM instance and configuring using IIS server......config tool is not working.
by means of wizard process is circuitous.
Do i need to patch OES.If yes then which patch do i need to apply and from which link can i download the patch
Regards,
Chhavi

You should definitely apply the latest patch, currently CP3 to both the admin and security module.
The patch is available through Metalink.
Also when you create the Security Module instance it is recommended that you use the ConfigTool rather than the Config Wizard. The ConfigTool is newer and better and automates virtually all of the steps you would have to manually perform after using the Config Wizard.
Again, to be 100% clear, use ConfigTool instead of Config Wizard.

OES2 Update confusion

In the past I've been mirroring the OES2-Updates-bundle and SLES10-SP1-Updates-bundle then applying those updates via the rug up command. I recently opened a ticket with Novell Support and the issue of patching came up. The engineer suggested I update using Novell's update server (via suse_register) and the command rug up -t patch.
Is there a difference between applying the monolithic patches and the Update bundles?
When I created the monolithic patch bundles (via zlmmirror) and tried rug up -t patch, no updates were applied even though rug lu showed several updates.
So confused,
Dan

Dan,
I know in oes 1 there was a difference using the patches and the monolithic bundle long long ago. We had some issues with that when we patched the server, opened some service requests and the problem was fixed. Since that time we use monolithic bundles to patches oes 1 and oes 2 server.
You need to know that when you mirror all the bundles from the novell update server you will get a bunch of patch bundles which are from type you-patch, whereas the monolithic bundle is from type package. Therefor the "rug up -t patch" will just check for assigned patch bundles to this server and therefor will not check the monolithic bundle. YOu can try to run "rug up -t package" or as I do, just use "rug up". The last one will check for all available updates in any of the assigned bundles.
Here is a bundle list from a oes 1 server where you can see the patch/package types:
Code:
# rug bl
S | Catalog | Name | Version | Type
--+------------------------+---------------------------------------------+---------+----------
i | Mandatory Bundles | OES1-20070327 | 4 | package
i | Mandatory Bundles | Recommended update for Novell iPrint server | 1 | you-patch
i | Mandatory Bundles | Recommended update for Novell NCP | 1 | you-patch
The OES1-20070327 is a monolithic bundle, the other are the pacthes and are from type you-patch.
Rainer

Named daemon shows as Unused

After patching my OES 2 DSFW server with the current maintenance update
and re-booting, I ran a "xadcntrl validate"
This showed that nameserver BIND was "unused"
I checked "rcnovell-xregd status" and found that it was not running
After manually starting rcnovell-xregd, I was able to start
rcnovell-named. xadcntrl validate showed all running.
I re-booted the system to re-test and still have the problem of
rcnovell-xregd not loading.
Can someone point me in the right direction to find out how to get this
to load automatically
Thanks,
Steve

a) Patched OES 2 SP3 with the december maintenance patch
b) completed this process - no change
c) ulimit -a output
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
file size (blocks, -f) unlimited
pending signals (-i) 16073
max locked memory (kbytes, -l) 32
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 16073
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
d) No change in rc level
Looks like a change was made such that xregd is trying to start before
a dependent service is done
XADCNTRL start also fails with the xregd error
again, once xregd is loaded novell-named loads fine
Steve
akarthikeyan wrote:
>
> Hi Steve,
> We would like to get the clarification for the following
> questions.
>
> a) Which OES to OES did you upgrade ?
> Have you upgraded from OES2 SP1/SP2 to OES2 SP3?
>
> b) If you are upgraded from OES2 SP2 to SP3, then there might be a
> chance that xregd registry corruption.
> Please refer to the following documentation steps to restore the xregd
> registry.
>
> 'Novell Doc: OES 11 SP1: NetStorage Administration Guide for Linux -
> Losing Registry Information After an Upgrade From OES 2 SP2 to OES 2
> SP3'
>
(http://www.novell.com/documentation/...a/by7swl5.html)
>
> c) If the problem continues even after rebuild registry, Please
> provide us output of "ulimit -a" command.
>
> d) Did you change any rc level of the daemon ?
>
>
> Thanks & Regards,
> Karthikeyan.A

Update Bash Live Production System?

Hello All,
I have updated bash and redline on our three servers which I have the ability to reboot at anytime but need to do our two servers that are actively accessed at all times. One is an OES2 SP3 (SLES 10 SP4) file server and the other is a OES 11 SP2 (SLES 11 SP3) Groupwise server. My question is can I update just the bash and redline without restarting the server or interrupting services? Does it matter which method I use? Rug/zypper vs. direct download of RPMs
Thanks for the advise.
Daniel

deejay33 Wrote in message:
> I have updated bash and redline on our three servers which I have the
> ability to reboot at anytime but need to do our two servers that are
> actively accessed at all times. One is an OES2 SP3 (SLES 10 SP4) file
> server and the other is a OES 11 SP2 (SLES 11 SP3) Groupwise server. My
> question is can I update just the bash and redline without restarting
> the server or interrupting services? Does it matter which method I use?
> Rug/zypper vs. direct download of RPMs
To answer your rug vs. zypper question first - zypper was provided
as a Technology Preview only in SLES10 so when updating OES2 SP3
you should use rug.
Now to address source of patches - if patching OES servers always
use the patches provided by Novell, either through the update
channels or download from Novell's Patch Finder site. Only
download the Shellshock patches from SUSE if your version of OES
is no longer supported (General or Extended) which is not the
case here.
After updating the bash and readline packages there is no need to
restart the server but you should make sure you logout any
terminal/SSH sessions and kill any remaining active bash
processes.
HTH.
Simon Flood
Novell Knowledge Partner

SLES OES Patching using ZCM - Best Practice?

Have recently updated an underused ZLM 7.3 to ZCM 11 and have started to utilise it to perform patching of SLES 10 SP3 and OES 2.
At present I have a Novell subscription that downloads from novell NU as Patches with
Create Category based Bundle Groups on.
I hadn't at this point got my head around the sandbox but now want to utilise this as I don't want to implement it willy nilly and have patches deployed and installed without testing first.
So first question is whether there is a best practice document for using ZCM 11 for patching SLES 10 and Sles/oes boxes that describes how best to use the sandbox.
Next question is whether sandbox applies to the patches or only monolithic bundles
At the end of the day it would be great to have a best practice document on how to utilise ZCM with change control over keeping SLES10/OES boxes patched up to date

Hello,
updates via ZCM is also a problem for me.
At least i could give a little response from testing.
As stated in the oes2 documentation patches had to be used for updates. At that point i had the problem that the subscription only created a bundle group which included the patches.
The monolithic bundle seems to be an ordinary update (zcm docu states rpm -U ...) and so should not be used for oes2 servers.
I found out that its ok to rename the patch bundle group created by the subscription to fix the patchlist. I use bundle names which include the date to keep updates from sles and oes in sync.
So you should be able to do updates with these bundlegroups without problem but it is not very nice because each patch bundle had its on log report and entry in the bundle list.
So to keep a global view is not very easy.
The other problem is that there is no official documentation neither on the oes2 or the zcm site how to correct update/patch a sles or oes system with zcm (without patchlink).
Hope this will be included soon as all linux satellite server will have the problem that this is the only way to get updates without direkt connection to the internet - at least as far as i can see.

Can not login into GUI after OES 11 SP1 patches

I had patched the OES 11 SP1 via YAST in order to update to OES 11 SP2. Upon restart, I can no longer login into the GUI.
The log files shows this:
Oct 19 09:45:08 millies1a [XTCOM]: WARNING: gdm_session_settings_load: lang = (null)
Oct 19 09:45:12 millies1a pam_autoncl[22163]: Auto Login will not continue - disabled for root user
Oct 19 09:45:13 millies1a checkproc: checkproc: can not get session id for process 32355!
Oct 19 09:45:16 millies1a gdm-simple-greeter[6948]: GLib-GObject-CRITICAL: g_param_spec_flags: assertion `G_TYPE_IS_FLAGS (flags_type)' failed
Oct 19 09:45:16 millies1a gdm-simple-greeter[6948]: GLib-GObject-CRITICAL: g_object_class_install_property: assertion `G_IS_PARAM_SPEC (pspec)' failed
What happened and how do I correct it?
Thanks in advance,
Ken

Originally Posted by mrosen
Am 19.10.2014 16:56, schrieb RLMILLIES:
>
> I had patched the OES 11 SP1 via YAST in order to update to OES 11 SP2.
> Upon restart, I can no longer login into the GUI.
> The log files shows this:
> Oct 19 09:45:08 millies1a [XTCOM]: WARNING: gdm_session_settings_load:
> lang = (null)
> Oct 19 09:45:12 millies1a pam_autoncl[22163]: Auto Login will not
> continue - disabled for root user
> Oct 19 09:45:13 millies1a checkproc: checkproc: can not get session id
> for process 32355!
> Oct 19 09:45:16 millies1a gdm-simple-greeter[6948]:
> GLib-GObject-CRITICAL: g_param_spec_flags: assertion `G_TYPE_IS_FLAGS
> (flags_type)' failed
> Oct 19 09:45:16 millies1a gdm-simple-greeter[6948]:
> GLib-GObject-CRITICAL: g_object_class_install_property: assertion
> `G_IS_PARAM_SPEC (pspec)' failed
>
> What happened and how do I correct it?
Go ahead and patch the server to SLES11Sp3 and OES11SP2 (via CLI and
using yast wagon). I've seen the same recently, and after updating it it
went away.
CU,
Massimo Rosen
Novell Knowledge Partner
No emails please!
http://www.cfc-it.de
Will do - Thanks
Sincerely,
Ken

Communication between the DNS/DHCP Manager and OES Server

No communication between the DNS/DHCP Manager Console and OES server (status,start,stop)
The screenshot shows the tab "DHCP (OES Linux)" in the DNS / DHCP Manager console
in the bottom of the image it shows the state of the DHCP servers.
allDHCP.JPG
The dhcp service is started on all these servers
You can see that the status is known only for four servers.
The button "start/stop DHCP service" works fine on this servers and
the dhcp service can be canceled and also restarted
But the status of the "dhcp service" is not recognized for all the other DHCP servers
and so we can not start or stop dhcp service on these servers.
All servers were installed at different times (last three years) with OES11 and
are upgraded to OES11SP2 with all patches.
The server keto (DHCP_keto) is a new installation OES11SP2 few days ago.
All OES servers were set up identically from me. LDAP, LUM, DMS, DHCP works fine.
Which service on the OES server is responsible for
communication (status indicator) between the DNS/DHCP Manager and the OES serve?
How the status query is performed by the DNS/DHCP Manager?
How can I test the communication to the server on the client (console)?
Which configurationfiles I should be compare on the server?
Thanks in advance
Gernot

gernot,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://www.novell.com/support and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Forums Team
http://forums.novell.com

Error while patching OIM with BP06

Hi ,
I am facing error while patching OIM 11.1.1.5.0 with BP 06.
Please see the logs below:-
patch:
[input] skipping input as property weblogic_password has already been set.
[echo] unzipping the archives.....
explode-archived-apps:
[delete] Deleting directory /apps/oracle/middleware/Oracle_IDM1/server/apps/oim.ear
[delete] Deleting directory /apps/oracle/middleware/Oracle_IDM1/server/apps/Nexaweb.ear
[mkdir] Created dir: /apps/oracle/middleware/Oracle_IDM1/server/apps/oim.ear
[mkdir] Created dir: /apps/oracle/middleware/Oracle_IDM1/server/apps/Nexaweb.ear
[unzip] Expanding: /apps/oracle/middleware/Oracle_IDM1/server/patching/oim.ear into /apps/oracle/middleware/Oracle_IDM1/server/apps/oim.ear
[unzip] Expanding: /apps/oracle/middleware/Oracle_IDM1/server/patching/Nexaweb.ear into /apps/oracle/middleware/Oracle_IDM1/server/apps/Nexaweb.ear
[echo] archives unzipped successfully.....
[echo]           seeding the out of the box jobs into db
seed-ootb-jobs:
seed-ootb-jobs:
[echo] ----> SEEDING OUT OF THE BOX SCHEDULE JOBS AND TRIGGERS
[java] Mar 25, 2013 7:32:31 PM org.quartz.core.QuartzScheduler <init>
[java] INFO: Quartz Scheduler v.1.6.0 created.
[java] Mar 25, 2013 7:32:31 PM org.quartz.impl.jdbcjobstore.JobStoreSupport initialize
[java] INFO: Using thread monitor-based data access locking (synchronization).
[java] Mar 25, 2013 7:32:31 PM org.quartz.impl.jdbcjobstore.JobStoreSupport cleanVolatileTriggerAndJobs
[java] INFO: Removed 0 Volatile Trigger(s).
[java] Mar 25, 2013 7:32:31 PM org.quartz.impl.jdbcjobstore.JobStoreSupport cleanVolatileTriggerAndJobs
[java] INFO: Removed 0 Volatile Job(s).
[java] Mar 25, 2013 7:32:31 PM org.quartz.impl.jdbcjobstore.JobStoreTX initialize
[java] INFO: JobStoreTX initialized.
[java] Mar 25, 2013 7:32:31 PM org.quartz.impl.StdSchedulerFactory instantiate
[java] INFO: Quartz scheduler 'OIMQuartzScheduler' initialized from an externally provided properties instance.
[java] Mar 25, 2013 7:32:31 PM org.quartz.impl.StdSchedulerFactory instantiate
[java] INFO: Quartz scheduler version: 1.6.0
[java] Mar 25, 2013 7:32:36 PM org.quartz.core.QuartzScheduler shutdown
[java] INFO: Scheduler OIMQuartzScheduler_$_NON_CLUSTERED shutting down.
[java] Mar 25, 2013 7:32:36 PM org.quartz.core.QuartzScheduler standby
[java] INFO: Scheduler OIMQuartzScheduler_$_NON_CLUSTERED paused.
[java] Mar 25, 2013 7:32:36 PM org.quartz.core.QuartzScheduler shutdown
[java] INFO: Scheduler OIMQuartzScheduler_$_NON_CLUSTERED shutdown complete.
[echo] ----> SEEDING COMPLETE LOG FILE
[echo] ----> LOG FILE : ${work.dir}
[echo] jobs seded succefully.....
[echo]           updating the oes out of the box policies in oim db
update-oes-ootb-policies:
update-oes-ootb-policies:
[echo] ----> UPDATING OUT OF THE BOX OES POLICIES
[java] [EL Info]: 2013-03-25 19:32:45.952--ServerSession(139722802)--EclipseLink, version: Eclipse Persistence Services - 1.1.0.r3634
[java] [EL Info]: 2013-03-25 19:32:48.824--ServerSession(139722802)--file:/apps/oracle/middleware/Oracle_IDM1/modules/oracle.oes_11.1.1/jps-internal.jar-JpsDBDataManager login successful
[echo] ----> SEEDING COMPLETE LOG FILE
[echo] ----> LOG FILE : /apps/oracle/middleware/Oracle_IDM1/server/seed_data/Seed/OESPolicies
[echo] oes policies updated successfully..
[echo]           upgrading the oes-ootb policies accordin g to the patched xml
upgrade-oes-ootb-policies:
upgrade-oes-ootb-policies:
[echo] ----> UPDATING OUT OF THE BOX OES POLICIES
[java] java.io.IOException: No such file or directory
[java]      at java.io.UnixFileSystem.createFileExclusively(Native Method)
[java]      at java.io.File.createNewFile(File.java:883)
[java]      at oracle.iam.authzpolicydefn.loader.PolicyLoadDataLogger.createLogFile(PolicyLoadDataLogger.java:68)
[java]      at oracle.iam.authzpolicydefn.loader.PolicyLoader.main(PolicyLoader.java:196)
[java] Exception in thread "Main Thread" java.lang.NullPointerException
[java]      at java.lang.Throwable.printStackTrace(Throwable.java:508)
[java]      at oracle.iam.authzpolicydefn.loader.PolicyLoadDataLogger.createLogFile(PolicyLoadDataLogger.java:73)
[java]      at oracle.iam.authzpolicydefn.loader.PolicyLoader.main(PolicyLoader.java:196)
BUILD FAILED
/apps/oracle/middleware/Oracle_IDM1/server/setup/deploy-files/setup.xml:94: The following error occurred while executing this line:
/apps/oracle/middleware/Oracle_IDM1/server/setup/deploy-files/setup.xml:215: The following error occurred while executing this line:
/apps/oracle/middleware/Oracle_IDM1/server/seed_data/seed-rcu-data.xml:136: Java returned: 1
Total time: 2 minutes 25 seconds
I have seen similar error on forum but it has not been answered.
I have set all variables correctly and the directory has all permissions as well.
Please let me know what I am missing here.
Thanks in advance.

Hi,
Thanks for your help.
The directory was already created during patch execution.
My error was related to MDS password.
The password for mds was different from OIM password so the patch errored out.
Once the mds password was updated correctly in the profile file, the patch executed successfully.

Having issue with OEG (11.1.1.6.1) and OES (11.1.1.5) integration

Hi,
I have installed latest OEG release (11.1.1.6) and OES 11.1.1.5, followed the instructions in the OEG and OES integration guide to create a policy that delegates authorization to OES through OES 11g Authorization filter.
Before testing the OEG policy, I created a OES11g authorization policy on OES Admin Server, and used a simple Java application to invoke authorization decisions successfully. But when testing the OEG policy from Service Explorer, I got the an error, and below is the trace stack:
DATA     3/19/12 17:49:15.186     trace transaction
DEBUG     3/19/12 17:49:15.186     add header Host:localhost:8080
DEBUG     3/19/12 17:49:15.186     add header Authorization:Basic d2VibG9naWM6d2VsY29tZTE=
DEBUG     3/19/12 17:49:15.186     add header SOAPAction:"http://startvbdotnet.com/web/Add"
DEBUG     3/19/12 17:49:15.186     add header User-Agent:Gateway
DEBUG     3/19/12 17:49:15.186     incoming content-length: 344
DEBUG     3/19/12 17:49:15.186     add header Connection:close
DEBUG     3/19/12 17:49:15.186     add header X-CorrelationID:Id-854f5ea44f67a9db01190000 1
DEBUG     3/19/12 17:49:15.186     add header Content-Type:text/xml; charset="utf-8"
DEBUG     3/19/12 17:49:15.186     Incoming HTTP request: method=POST, host=(unset), port=(unset), path=/, query=(unset), version=1.1
DATA     3/19/12 17:49:15.186     Firewall resolved uri '/' against '/'
DATA     3/19/12 17:49:15.186     Firewall failed to resolve uri '/' against '/healthcheck'
DEBUG     3/19/12 17:49:15.186     using handler at /
DEBUG     3/19/12 17:49:15.186     Adding MessageListener: com.vordel.circuit.FilterPathTracker@f0f11b8
DEBUG     3/19/12 17:49:15.186     Adding MessageListener: com.vordel.reporting.rtm.RealtimeMonitoring$1$1@70c7c57c
DEBUG     3/19/12 17:49:15.187     handle type text/xml with factory class com.vordel.mime.XMLBody$Factory
DEBUG     3/19/12 17:49:15.187     Adding MessageListener: com.vordel.dwe.http.HTTPMessageListener@5200089
DEBUG     3/19/12 17:49:15.187     Circuit reference [Global Request Policy] is not enabled - ignoring
DEBUG     3/19/12 17:49:15.187     Circuit reference [Custom Request Policy] is not enabled - ignoring
DEBUG     3/19/12 17:49:15.187     Circuit reference [Path Specific Policy] valid and enabled - calling
DEBUG     3/19/12 17:49:15.188     run circuit "OES11g Authorization "...
DEBUG     3/19/12 17:49:15.188     run filter [HTTP Basic] {
DEBUG     3/19/12 17:49:15.188     VordelRepository.checkCredentials: username=weblogic
DEBUG     3/19/12 17:49:15.188     } = 1, filter [HTTP Basic]
DEBUG     3/19/12 17:49:15.188     Filter [HTTP Basic] completes in 0 milliseconds.
DEBUG     3/19/12 17:49:15.188     run filter [11g Authorization] {
DEBUG     3/19/12 17:49:15.188     creating subject from 'weblogic'
DEBUG     3/19/12 17:49:15.197     checking 'write' to resource: HelloOESworld/MyResourceType/MyResource
DEBUG     3/19/12 17:49:15.262     parsing XML body from input stream of type sun.net.www.protocol.jar.JarURLConnection$JarURLInputStream. ContentSource is of type java InputStream
DATA     3/19/12 17:49:15.263     getting class javax.xml.xpath.XPath with classLoader.loadClass()
DATA     3/19/12 17:49:15.263     loaded class javax.xml.xpath.XPath
DATA     3/19/12 17:49:15.263     getting class javax.xml.xpath.XPathConstants with classLoader.loadClass()
DATA     3/19/12 17:49:15.263     loaded class javax.xml.xpath.XPathConstants
DATA     3/19/12 17:49:15.263     getting class javax.xml.namespace.QName with classLoader.loadClass()
DATA     3/19/12 17:49:15.263     loaded class javax.xml.namespace.QName
DEBUG     3/19/12 17:49:15.277     parsing XML body from input stream of type java.io.FileInputStream. ContentSource is of type java InputStream
DATA     3/19/12 17:49:15.278     getting class javax.xml.namespace.NamespaceContext with classLoader.loadClass()
DATA     3/19/12 17:49:15.279     loaded class javax.xml.namespace.NamespaceContext
DEBUG     3/19/12 17:49:15.744     parsing XML body from input stream of type sun.net.www.protocol.jar.JarURLConnection$JarURLInputStream. ContentSource is of type java InputStream
DEBUG     3/19/12 17:49:15.774     parsing XML body from input stream of type sun.net.www.protocol.jar.JarURLConnection$JarURLInputStream. ContentSource is of type java InputStream
DEBUG     3/19/12 17:49:15.845     } = 2, filter [11g Authorization]
DEBUG     3/19/12 17:49:15.845     Filter [11g Authorization] completes in 657 milliseconds.
DEBUG     3/19/12 17:49:15.845     ..."OES11g Authorization " complete.
DATA     3/19/12 17:49:15.846     getting class com.vordel.reporting.rtm.api.MetricTypeRangeCount with classLoader.loadClass()
DATA     3/19/12 17:49:15.846     loaded class com.vordel.reporting.rtm.api.MetricTypeRangeCount
DATA     3/19/12 17:49:15.847     getting class java.lang.Throwable with classLoader.loadClass()
DATA     3/19/12 17:49:15.847     loaded class java.lang.Throwable
DATA     3/19/12 17:49:15.848     getting class com.vordel.system.NativeOutputStream with classLoader.loadClass()
DATA     3/19/12 17:49:15.849     loaded class com.vordel.system.NativeOutputStream
DATA     3/19/12 17:49:15.849     getting class com.vordel.system.NativeOutputStream with classLoader.loadClass()
DATA     3/19/12 17:49:15.849     loaded class com.vordel.system.NativeOutputStream
DATA     3/19/12 17:49:15.849     getting class java.io.PrintStream with classLoader.loadClass()
DATA     3/19/12 17:49:15.849     loaded class java.io.PrintStream
ERROR     3/19/12 17:49:15.850     java exception running circuit: java.lang.RuntimeException: oracle.security.jps.service.policystore.PolicyStoreException: JPS-10619: Failed to initialize cipher for local cache encryption/decryption. at oracle.security.jps.az.internal.runtime.encryption.CipherServiceFactory.getService(CipherServiceFactory.java:61) at oracle.security.jps.az.internal.runtime.pd.receiver.UpdatePolicySet.initCipherService(UpdatePolicySet.java:211) at oracle.security.jps.az.internal.runtime.pd.receiver.UpdatePolicySet.<init>(UpdatePolicySet.java:139) at oracle.security.jps.az.internal.runtime.service.PDPServiceImpl.initializeControlledPD(PDPServiceImpl.java:296) at oracle.security.jps.az.internal.runtime.service.PDPServiceImpl.initial(PDPServiceImpl.java:368) at oracle.security.jps.az.internal.runtime.service.PDPServiceImpl.<init>(PDPServiceImpl.java:268) at oracle.security.jps.az.internal.runtime.provider.PDPServiceProvider.getInstance(PDPServiceProvider.java:89) at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.findServiceInstance(ContextFactoryImpl.java:139) at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.getContext(ContextFactoryImpl.java:170) at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.getContext(ContextFactoryImpl.java:191) at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.getContext(JpsContextFactoryImpl.java:132) at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.getContext(JpsContextFactoryImpl.java:159) at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.getContext(JpsContextFactoryImpl.java:165) at oracle.security.jps.openaz.pep.PepRequestFactoryImpl.<init>(PepRequestFactoryImpl.java:123) at oracle.security.jps.openaz.pep.PepRequestFactoryImpl.getPepRequestFactory(PepRequestFactoryImpl.java:113) at com.vordel.circuit.oracle.oeseleveng.OES11GAuthZProcessor.invoke(OES11GAuthZProcessor.java:76) at com.vordel.circuit.InvocationEngine.invokeFilter(InvocationEngine.java:154) at com.vordel.circuit.InvocationEngine.invokeCircuit(InvocationEngine.java:43) at com.vordel.circuit.InvocationEngine.processMessage(InvocationEngine.java:229) at com.vordel.circuit.SyntheticCircuitChainProcessor.invoke(SyntheticCircuitChainProcessor.java:36) at com.vordel.dwe.http.HTTPPlugin.invokeDispose(HTTPPlugin.java:290) at com.vordel.dwe.http.HTTPPlugin.invoke(HTTPPlugin.java:131) Caused by: oracle.security.jps.service.policystore.PolicyStoreException: JPS-10619: Failed to initialize cipher for local cache encryption/decryption. at oracle.security.jps.az.internal.runtime.encryption.AESCipherImpl.retrieveRawKey(AESCipherImpl.java:140) at oracle.security.jps.az.internal.runtime.encryption.AESCipherImpl.getKey(AESCipherImpl.java:184) at oracle.security.jps.az.internal.runtime.encryption.AESCipherImpl.<init>(AESCipherImpl.java:87) at oracle.security.jps.az.internal.runtime.encryption.CipherServiceFactory.getService(CipherServiceFactory.java:59) ... 21 more
DEBUG     3/19/12 17:49:15.850     add header Content-Type:text/plain
DEBUG     3/19/12 17:49:15.850     add header Server:
DEBUG     3/19/12 17:49:15.850     send prologue: content length -1
DEBUG     3/19/12 17:49:15.850     peer can do chunking
DEBUG     3/19/12 17:49:15.850     add header Transfer-Encoding:chunked
DEBUG     3/19/12 17:49:15.850     reused connection 0x2b72480 1 times
Am I missing something? Please help.

Hello,
I too am facing the same error. The environment details are as follows:
OS: Win2k8 64 bit
OEG: 11.1.1.6.1
OES: 11.1.1.5
OES Client: 11.1.1.5
I have also applied the patch 12917515 to OES (both server and client). This patch contains 2 sub-folders [APM and OES]. I have installed the OES sub-folder patch only.
Steps: I followed the steps as mentioned in OEG-OES 11g integration guide: http://www.oracle.com/technetwork/middleware/id-mgmt/oes11g-integration-guide-1520074.pdf
Note: Instead of using a HTTP Basic filter, I set the "authentication.subject.id" attribute manually and then call "OES 11g Authorization" filter.
Issue,
The following exception is thrown when the authorization filter runs,
java exception running circuit: java.lang.RuntimeException: oracle.security.jps.service.policystore.PolicyStoreException: JPS-10619: Failed to initialize cipher for local cache encryption/decryption. at oracle.security.jps.az.internal.runtime.encryption.CipherServiceFactory.getService(CipherServiceFactory.java:61) at oracle.security.jps.az.internal.runtime.pd.receiver.UpdatePolicySet.initCipherService(UpdatePolicySet.java:211) at oracle.security.jps.az.internal.runtime.pd.receiver.UpdatePolicySet.<init>(UpdatePolicySet.java:139) at oracle.security.jps.az.internal.runtime.service.PDPServiceImpl.initializeControlledPD(PDPServiceImpl.java:296) at oracle.security.jps.az.internal.runtime.service.PDPServiceImpl.initial(PDPServiceImpl.java:368) at oracle.security.jps.az.internal.runtime.service.PDPServiceImpl.<init>(PDPServiceImpl.java:268) at oracle.security.jps.az.internal.runtime.provider.PDPServiceProvider.getInstance(PDPServiceProvider.java:89) at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.findServiceInstance(ContextFactoryImpl.java:139) at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.getContext(ContextFactoryImpl.java:170) at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.getContext(ContextFactoryImpl.java:191) at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.getContext(JpsContextFactoryImpl.java:132) at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.getContext(JpsContextFactoryImpl.java:159) at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.getContext(JpsContextFactoryImpl.java:165) at oracle.security.jps.openaz.pep.PepRequestFactoryImpl.<init>(PepRequestFactoryImpl.java:123) at oracle.security.jps.openaz.pep.PepRequestFactoryImpl.getPepRequestFactory(PepRequestFactoryImpl.java:113) at com.vordel.circuit.oracle.oeseleveng.OES11GAuthZProcessor.invoke(OES11GAuthZProcessor.java:76) at com.vordel.circuit.InvocationEngine.invokeFilter(InvocationEngine.java:154) at com.vordel.circuit.InvocationEngine.invokeCircuit(InvocationEngine.java:43) at com.vordel.circuit.InvocationEngine.processMessage(InvocationEngine.java:229) at com.vordel.circuit.SyntheticCircuitChainProcessor.invoke(SyntheticCircuitChainProcessor.java:36) at com.vordel.dwe.http.HTTPPlugin.invokeDispose(HTTPPlugin.java:290) at com.vordel.dwe.http.HTTPPlugin.invoke(HTTPPlugin.java:131) Caused by: oracle.security.jps.service.policystore.PolicyStoreException: JPS-10619: Failed to initialize cipher for local cache encryption/decryption. at oracle.security.jps.az.internal.runtime.encryption.AESCipherImpl.retrieveRawKey(AESCipherImpl.java:140) at oracle.security.jps.az.internal.runtime.encryption.AESCipherImpl.getKey(AESCipherImpl.java:184) at oracle.security.jps.az.internal.runtime.encryption.AESCipherImpl.<init>(AESCipherImpl.java:87) at oracle.security.jps.az.internal.runtime.encryption.CipherServiceFactory.getService(CipherServiceFactory.java:59) ... 21 more
Is there any other patch required to make OEG work with OES 11g ? How to resolve this error ?
Any help will be greatly appreciated.
Regards.

Odd file access issues OES 11 SP1

Hello,
We're running a VMWare ESXi 5.1 cluster. On that we have an OES 11 cluster managing groupwise/iprint/nss/dhcp/dns services. Over the summer we updated to SP1 on the OES side.
This school year we have seen some odd issues, particularly with our NSS volumes. Occasionally, some users will report that they can't see their home directory or other shared folders. I actually had one user opening up a shared folder for our high school and was seeing a shared folder for a completely different school. If you created a new folder, it put it in the proper share. So, very weird behavior. Generally a client reboot fixes the issues, but it's becoming common enough that I feel there is some underlying issue.
Any thoughts about what could be causing this? I'm not even sure where to look as far as logs go when we see the problem.
-Ian

You've patched up SLES and OES to the current patch level? What client OS and protocol is in use? What Novell client version, if any?

Yast2 channel-upgrade-oes command looking for wrong ldap server

a little background info
Today I upgraded our first OES-Linux server from OES11 to OES11sp1.This
was the first OES-L server that we installed for our migration from
NetWare. Everything has been working fine and today I upgraded it so it
would be at the same patch level as the other servers before we moved to
OES11sp2.
The upgrade went fine until the final step
I was following the "Novell Doc: OES 11 SP1: Installation Guide -
Channel Upgrade from OES 11 to OES 11 SP1"
The final step says:
"After the reboot, log on to the server and run the yast2
channel-upgrade-oes command to complete the OES services
reconfiguration. This will prompt for eDirectory" password...
When I put in the eDirectory password it fails with a message that it
cannot contact the LDAP server on the NetWare server that used to be our
main LDAP server. That server has been gone for almost 2yrs.
I'm assuming there is a conf file I can change the address in and move
forward. I poked around and could not find a file that had the old LDAP
servers IP address in it. Does anyone know where this configuration file
would be?

Nevermind - I spoke too soon (and apparently forgot how to use grep to
search for strings in files...)
it was reading the old NetWare server IP address in a file named
/etc/sysconfig/novell/edir2_oes11
I put the correct address into the /etc/sysconfig/novell/edir_oes11 and
it worked
On 4/12/14, 5:26 PM, Steve B wrote:
> a little background info
> Today I upgraded our first OES-Linux server from OES11 to OES11sp1.This
> was the first OES-L server that we installed for our migration from
> NetWare. Everything has been working fine and today I upgraded it so it
> would be at the same patch level as the other servers before we moved to
> OES11sp2.
>
> The upgrade went fine until the final step
> I was following the "Novell Doc: OES 11 SP1: Installation Guide -
> Channel Upgrade from OES 11 to OES 11 SP1"
>
> The final step says:
> "After the reboot, log on to the server and run the yast2
> channel-upgrade-oes command to complete the OES services
> reconfiguration. This will prompt for eDirectory" password...
>
> When I put in the eDirectory password it fails with a message that it
> cannot contact the LDAP server on the NetWare server that used to be our
> main LDAP server. That server has been gone for almost 2yrs.
>
> I'm assuming there is a conf file I can change the address in and move
> forward. I poked around and could not find a file that had the old LDAP
> servers IP address in it. Does anyone know where this configuration file
> would be?

Patching OIM 11.1.1.5.3 to 11.1.1.5.6 Question

I would like to only patch my OIM 11.1.1.5.3 to OIM 11.1.1.5.6.
Patch Number: 14760839
Bundle Name: Oracle Identity Management Suite BP patch of 11.1.1.5.2
Looking into the downloaded zip, I see patches for the following:
- OIM 11.1.1.5.6
- OAM 11.1.1.5.5
- OES 11.1.1.5.4
- OAAM 11.1.5.2
In my environment I have OIM and OAM. Is it a requirement to patch OAM if I patch OIM to 11.1.1.5.6?

Hi,
If you are applying patch set for OIM ie from OIM 11.1.1.5.3 to OIM 11.1.1.5.6, it is not required to apply patch to OAM. OIAm products are certified in release level not in patch set level.
Please see the certification matrix.
http://www.oracle.com/technetwork/middleware/id-mgmt/identity-accessmgmt-11gr1certmatrix-161244.xls
Mark if this helps you.
Regards,
Kishore

CIFS Issues following May 2014 Maintenance Patch

Hi All,
Just wondering if anyone else has noticed issues with novell-cifs on OES 11 SP1 or SP2 following the May 2014 Updates?
We installed the most recent patches via YAST and noticed issues saving to our File Servers via CIFS from Autodesk Inventor. Inventor could see the mapped drives and open files however when saving a new file, it would give an error 'Failed to Create Folder, "H:".'
The offending RPM versions are:
OES11 SP2: novell-cifs-1.3.2-0.90.9
OES11 SP1: novell-cifs-1.3.1-35.52.73.19
Rolling back to the following versions resolved the issue:
OES11 SP2: novell-cifs-1.3.2-0.88.2
OES11 SP1: novell-cifs-1.3.1-35.52.69.1
I'm interested in knowing if anyone has experienced the same or similar issues. Most of our File Server traffic comes from Mac OS X or Citrix XenDesktop connections using CIFS. Unfortunately this means our reasons to continue running OES11 file servers with NSS are diminishing as we can't make full use of the features via CIFS. :(
Thanks,
John

Hi Wilfried,
Originally Posted by gerstner
Hi Jens & John
all Volumes of our OES11 Server are mounted with long namespace.
Meanwile we switched back from the buggy version to rpm novell-cifs-1.3.2-0.86.1 and every thing works fine again.
To open a SR at Novell (this would be the best way) ist just a question of time. Our OES Servers are just a view among hundreds of others. From the past i know it consumes a lot of time (tons of logs etc.).
To switch back to a previous version, is a workarround we could live with.
if you let me know the SR number (via private message), I'll try to help streamline things. When you open the SR, it ought to be sufficient to upload the supportconfig file, quote the descriptions from this thread and add a reference to this thread - so not *that much* time involved...
Regards,
Jens

Unable to start OES Admins Server (i.e asiAdminServer)

Hi All,
My goal is to install OES 10.1.4.3 . Below is my environment:
- RHEL 5.5 64 bit.
- SQL Server 2005.
- Weblogic 10.3.3 (wls1033_generic.jar)
-Java version is 64 bit JDK as shown below:
*"1.6.0_21" Java(TM) SE Runtime Environment (build 1.6.0_21-b06) Java HotSpot(TM) 64-Bit Server VM (build 17.0-b16, mixed mode)*
Steps:
1. Installed JDK 6update21.
2. Ran dbconfig tool on top of SQL Server.
3. Installed Weblogic.
4. Installed OES 10.1.4.3. (*While installing , I selected "Install Schema"*)
After installation , it has created "asiDomain" under /home/oracle/Middleware/ales32-admin. I tried starting OES admin server from /home/oracle/Middleware/ales32-admin/asiDomain/bin. But it throws below error and server is not coming up.
<Aug 23, 2010 6:19:43 AM PDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.3.0 Fri Apr 9 00:05:28 PDT 2010 1321401 >
<Aug 23, 2010 6:19:45 AM PDT> <Error> <Management> <BEA-141244> <Schema validation errors while parsing /home/oracle/Middleware/ales32-admin/asiDomain/config/config.xml - Invalid xsi:type qname: 'ext:log4j-auditorType' in element realm@http://xmlns.oracle.com/weblogic/domain>
<Aug 23, 2010 6:19:45 AM PDT> <Error> <Management> <BEA-141244> <Schema validation errors while parsing /home/oracle/Middleware/ales32-admin/asiDomain/config/config.xml - /home/oracle/Middleware/ales32-admin/asiDomain/<unknown>:7:9: error: failed to load java type corresponding to t=log4j-auditorType@http://www.bea.com/ns/weblogic/90/security/extension>
<Aug 23, 2010 6:19:45 AM PDT> *<Error>* <Management> <BEA-141244> <Schema validation errors while parsing /home/oracle/Middleware/ales32-admin/asiDomain/config/config.xml - Invalid xsi:type qname: 'ext:database-authenticatorType' in element realm@http://xmlns.oracle.com/weblogic/domain>
<Aug 23, 2010 6:19:45 AM PDT> *<Error>* <Management> <BEA-141244> <Schema validation errors while parsing /home/oracle/Middleware/ales32-admin/asiDomain/config/config.xml - /home/oracle/Middleware/ales32-admin/asiDomain/<unknown>:13:9: error: failed to load java type corresponding to t=database-authenticatorType@http://www.bea.com/ns/weblogic/90/security/extension>
<Aug 23, 2010 6:19:45 AM PDT> *<Error>* <Management> <BEA-141244> <Schema validation errors while parsing /home/oracle/Middleware/ales32-admin/asiDomain/config/config.xml - Invalid xsi:type qname: 'ext:asi-role-mapper-providerType' in element realm@http://xmlns.oracle.com/weblogic/domain>
<Aug 23, 2010 6:19:45 AM PDT> *<Error>* <Management> <BEA-141244> <Schema validation errors while parsing /home/oracle/Middleware/ales32-admin/asiDomain/config/config.xml - /home/oracle/Middleware/ales32-admin/asiDomain/<unknown>:26:9: error: failed to load java type corresponding to t=asi-role-mapper-providerType@http://www.bea.com/ns/weblogic/90/security/extension>
<Aug 23, 2010 6:19:45 AM PDT> *<Error>* <Management> <BEA-141244> <Schema validation errors while parsing /home/oracle/Middleware/ales32-admin/asiDomain/config/config.xml - Invalid xsi:type qname: 'ext:asi-authorization-providerType' in element realm@http://xmlns.oracle.com/weblogic/domain>
<Aug 23, 2010 6:19:45 AM PDT> <Error> <Management> <BEA-141244> <Schema validation errors while parsing /home/oracle/Middleware/ales32-admin/asiDomain/config/config.xml - /home/oracle/Middleware/ales32-admin/asiDomain/<unknown>:32:9: error: failed to load java type corresponding to t=asi-authorization-providerType@http://www.bea.com/ns/weblogic/90/security/extension>
<Aug 23, 2010 6:19:45 AM PDT> *<Error>* <Management> <BEA-141244> <Schema validation errors while parsing /home/oracle/Middleware/ales32-admin/asiDomain/config/config.xml - Invalid xsi:type qname: 'ext:asi-adjudicatorType' in element realm@http://xmlns.oracle.com/weblogic/domain>
<Aug 23, 2010 6:19:45 AM PDT> *<Error>* <Management> <BEA-141244> <Schema validation errors while parsing /home/oracle/Middleware/ales32-admin/asiDomain/config/config.xml - /home/oracle/Middleware/ales32-admin/asiDomain/<unknown>:38:9: error: failed to load java type corresponding to t=asi-adjudicatorType@http://www.bea.com/ns/weblogic/90/security/extension>
<Aug 23, 2010 6:19:45 AM PDT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: [Management:141245]Schema Validation Error in /home/oracle/Middleware/ales32-admin/asiDomain/config/config.xml see log for details. Schema validation can be disabled by starting the server with the command line option: -Dweblogic.configuration.schemaValidationEnabled=false>
<Aug 23, 2010 6:19:45 AM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Aug 23, 2010 6:19:45 AM PDT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Aug 23, 2010 6:19:45 AM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
I applied CP4 patch also but no luck :(
1. Am I missing something ?
2. Is my environment supported ?
Please provide your inputs.
Thanks
GK Goalla

Any inputs, please ?
Thanks
GK Goalla

PATCHING OES ???

Similar Messages

Maybe you are looking for