Is Oracle Identity Management 11g Patch Set 5 (11.1.1.6.0) reqd for Essbase

In the Media pack Readme for parts required to be downloaded for different EPM products, Essbase has Oracle Identity Management 11g Patch Set 5 (11.1.1.6.0) for Microsoft Windows x86 (64-bit) listed. Can someone please tell me if this is a must have. If not under what conditions does one need to have this?
Thanks,
Ted.

It is not a must have, if you don't know what OIM is then you probably dont need it :)
Cheers
John
http://john-goodwin.blogspot.com/

Similar Messages

  • Is OID available in Oracle identity management 11g R2

    Is OID available in Oracle identity management 11g R2

    OID is not yet available in 11gR2.
    As you can see in the list below, ODSEE and OUD are the only directories currently available in 11gR2.
    Here is the list of products in Oracle Identity Management 11g R2
    Oracle WebLogic Server 11gR1 (10.3.6) and Coherence
    Oracle Access Manager Access SDK 11.1.2.0.0
    Oracle Entitlements Server Security Module 11g (11.1.2.0.0)
    Oracle Access Manager WebGates 11.1.2.0.0
    Oracle Business Intelligence 11g (11.1.1.5.0)
    Oracle Fusion Middleware Repository Creation Utility 11g (11.1.2.0.0)
    Oracle Identity and Access Management 11g (11.1.2.0.0)
    Oracle Directory Server Enterprise Edition 11gR1 Patch Set 1 (11.1.1.5.0)
    Oracle Identity Management 11g Patch Set 5 (11.1.1.6.0)
    Oracle SOA Suite 11g Patch Set 5 (11.1.1.6.0)
    Oracle Fusion Middleware Repository Creation Utility 11g (11.1.1.6.0)
    Oracle Unified Directory 11g (11.1.2.0.0)
    Oracle Fusion Middleware Identity Management Documentation Library 11g Release 2 (11.1.2.0.0)
    Oracle Coherence for C++ Version 3.7.1
    Oracle Coherence Version 3.7.1
    Oracle OpenSSO Fedlet version 11.1.1.3.0

  • Skin Customization in Oracle Identity Manager 11g Release 2 (11.1.2)

    I was recently tasked with branding an OIM instance to match pretty stringent branding standards. To accomplish this task, I extended the fusion theme which is provided out of the box into a new custom skin. In the example below, I took the design as far as I could, which required decently advanced css knowledge; however, even a novice web designer could easily make simple updates to the backgrounds and fonts which would also greatly enhance the user experience.
    Utilizing FireBug for Firefox, I inspected elements of the OIM interface to see which div's I needed to modify in the css file. You can edit as little or as many elements as you'd like in your custom skin; however, I'd recommend preserving the primary elements original placements to avoid confusion for users that are already used to an out of the box version of OIM.
    This is the Oracle doc I used when creating the custom skin: http://docs.oracle.com/cd/E27559_01/dev.1112/e27150/uicust.htm#BABJIJIA
    Notes regarding the Oracle tutorial mentioned above:
    Be sure and remove the temp directory, shut down your OIM server, upload your files, then restart your OIM server with each css modification.
    30.3.1 - Configuring Skins: 1. After you create the skin in the trinidad-skins.xml file, make a copy of the trinidad-skins.xml from the /iam-consoles-faces.war/WEB-INF/ directory to the
    oracle.iam.console.identity.sysadmin.ear/WEB-INF/ directory AND the
    oracle.iam.console.identity.self-service.ear/WEB-INF directory.
    (The doc references admin.ear: the fully qualified name of the ear is: oracle.iam.console.identity.sysadmin.ear)
    30.3.1 - Configuring Skins: Make all of your changes in the /oracle.iam.console.identity.sysadmin.ear/WEB-INF/trinidad-skins.xml file, /oracle.iam.console.identity.self-service.ear/WEB-INF/trinidad-skins.xml file, and the /iam-consoles-faces.war/WEB-INF/trinidad-skins.xml file.
    (The doc doesn't mention making your css edits in the oracle.iam.console.identity.self-service.ear directory which is required)
    Here is a link to my blog post with screenshots: http://www.idmworks.com/blog/entry/skin-customization-in-oracle-identity-manager-11g-release-2-11-1-2

    I was recently tasked with branding an OIM instance to match pretty stringent branding standards. To accomplish this task, I extended the fusion theme which is provided out of the box into a new custom skin. In the example below, I took the design as far as I could, which required decently advanced css knowledge; however, even a novice web designer could easily make simple updates to the backgrounds and fonts which would also greatly enhance the user experience.
    Utilizing FireBug for Firefox, I inspected elements of the OIM interface to see which div's I needed to modify in the css file. You can edit as little or as many elements as you'd like in your custom skin; however, I'd recommend preserving the primary elements original placements to avoid confusion for users that are already used to an out of the box version of OIM.
    This is the Oracle doc I used when creating the custom skin: http://docs.oracle.com/cd/E27559_01/dev.1112/e27150/uicust.htm#BABJIJIA
    Notes regarding the Oracle tutorial mentioned above:
    Be sure and remove the temp directory, shut down your OIM server, upload your files, then restart your OIM server with each css modification.
    30.3.1 - Configuring Skins: 1. After you create the skin in the trinidad-skins.xml file, make a copy of the trinidad-skins.xml from the /iam-consoles-faces.war/WEB-INF/ directory to the
    oracle.iam.console.identity.sysadmin.ear/WEB-INF/ directory AND the
    oracle.iam.console.identity.self-service.ear/WEB-INF directory.
    (The doc references admin.ear: the fully qualified name of the ear is: oracle.iam.console.identity.sysadmin.ear)
    30.3.1 - Configuring Skins: Make all of your changes in the /oracle.iam.console.identity.sysadmin.ear/WEB-INF/trinidad-skins.xml file, /oracle.iam.console.identity.self-service.ear/WEB-INF/trinidad-skins.xml file, and the /iam-consoles-faces.war/WEB-INF/trinidad-skins.xml file.
    (The doc doesn't mention making your css edits in the oracle.iam.console.identity.self-service.ear directory which is required)
    Here is a link to my blog post with screenshots: http://www.idmworks.com/blog/entry/skin-customization-in-oracle-identity-manager-11g-release-2-11-1-2

  • Tables using  Oracle Identity Manager 11g

    Good evening friends,
    I have a query about the tables used by Identity Manager 11g.
    There is some document that tells me the tables used by Oracle Identity Manager 11g, and how they are linked.
    Very grateful for your help

    This does not exist for 11g. Only 9.x has a database diagram. Most the tables are the same, it's just the request side that is new due to the SOA integration.
    -Kevin

  • How to repair the database used by Oracle Identity Manager 11g

    Hi friends,
    I have a question about Oracle Identity Manager 11g.
    As I can repair the database used by Oracle Identity Manager 11g
    Thanks

    I think you can do if the repaired database is replica of old one.
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/repair.htm

  • Enterprise Deployment Guide for Oracle Identity Management 11g

    Hi,
    I am looking for Enterprise Deployment Guide for Oracle Identity Management 11g for latest verion 11.1.1.5
    Please help
    Thanks

    Thanks for the reply.
    Actually I am looking for Enterprise Deployment Guide for Oracle Identity Management for 11.1.15(similar like E12035-06).I am not able to find same in the link provided.
    Thanks

  • Unable to send Email Notification for Oracle Identity Manager 11g for users

    Hi All,
    Can anyone please share a workaround to send email notifications when user is created through trusted recon in OIM 11G.Please Help Me out.
    \oim_user

    Hi
    Do you just create the user in OIM and not anywhere else?
    I have cofigured notification on the the target resources that i automatically assign to users as soon as they are created via trusted recon. Let say a user gets AD rersource. Ill notify whoever i want from there.
    Another way i did it was using the post eventHandler code. I call an email service to notify admins on the status of the recon and post recon eventhandlers. snippet below..
    tcEmailNotificationUtil emailNotificationUtil = new tcEmailNotificationUtil(dbReference);
    emailNotificationUtil.constructEmail(emailTemp);
    emailNotificationUtil.setBody(buildMailBody(message));
    emailNotificationUtil.sendEmail(toAddress);
    Let me know if this gives you an idea.

  • Oracle Identity Manger 11g

    Hi Experts !
    As we all know that Oracle Identity Management 11g has been released. My question is that what version of Oracle Identity Manager has been included in Oracle Identity Management 11g? Is it still Oracle Identity Manger 9.1.0.2? or is there anything like Oracle Identity Manager 11g? I am unable to find the download link for the identity manager.
    please help me here.
    Regards

    Thank you for you reply sir !
    OIM 9.1 was in struts framework. but since oracle fusion middle ware is based on ADF so OIM 11g will also be in ADF??
    Is support available for migration from OIM 9.1 to OIM 11g?
    Best Regards

  • Mail notifications Identity Manager 11g.

    Friends,
    I have configured the resource database.
    - As I can notify the user by email when you request a resource, and when the reconciliation process the information correctly and incorrectly.
    - As I can send email notifications when a user is provisioned to a resource set Oracle Identity Manager 11g.
    Thanks.

    I am facing the same issue. However my platform is Windows 7 Ultimate x64. I guess all Vista compitable editions should be working on Windows 7 as well.

  • Oracle Identity Manager Customization

    Hi to all. Working with Oracle Identity Manager 11g, I have a simple need. Please let me describe my scenario. I have one user, say Joseph who has 2 or many accounts of a resource, namely "BADGE". In my application, one user may have one or more badges. When Joseph tries to submit a ModifyProvisionedResource request for the BADGE resource type, the system shows a table for the selection of one among the BADGE resources. This table has 3 columns: Resource, UserID, Description.
    I simply need to add one column to this table to show a custom attribute of the BADGE resource.
    Which are the steps to follow to do this?
    Thank you in advance,
    Giuseppe.

    Hi,
    As martin said its a custom interface.You will have to extend ManageAttestationTask class. You need to override few method particularly populateTableData and populateTableDataForRequestDetails methods.
    I would recommend this approach until you are every much familier with struts development because if you messed up attestation won't work and more over oracle dosn't support any action class customizations.
    Regards
    Nitesh

  • Error while installing oracle identity manager

    Im using windows installer. I get error below when installing Oracle Identity Manager, any idea to solve this?
    Following Error occured during schema creation connected
    ERROR loading database script C:\oracle identity manager\OIM9.0.1.1\installServer\Xellerate/db/oracle/xell.sql!
    Please contact your DBA! ORA-06550: line 1,
    column 7: PLS-00905: object KOD.PIN_OBJ is invalid ORA-06550: line 1,
    column 7: PL/SQL: Statement ignored [12/13/06 11:36 AM]
    ------------------------------------------------------------------------------

    Hi,
    I got the same error:
    Following Error occurred during schema creation connectedError loading database scriptD:\appl\OIM_902_RC\OIM_902_RC\installServer\Xellerate/db/oracle/xell.sqlPlease contact your DBA!ORA-06550: line 1, column 7: PLS-00905: object VIM_ADMIN.PIN_OBJ is invalid ORA-06550: line 1, column 7: PL/SQL: Statement ignored [12/8/06 5:57 PM]      
    But I could fix it by dropping the schema and recreate it by only executing the prepare_xl_db.sh script as dba user on database server:
    1.     Copy the scripts prepare_xl_db.sh and xell_db_prepare.sql from the distribution CD/Directory to a directory on the machine hosting the database where there is (as the account user performing this task) write permission.
    2.     Run the prepare_xl_db.sh script by entering the following command:
    ./prepare_xl_db.sh
    3.     Provide information appropriate for the database and host machine when the script prompts for the following items:
    •     The location of the Oracle home (ORACLE_HOME)
    •     The name of the database (ORACLE_SID)
    •     The name of the Oracle Identity Manager database user to be created
    •     The password for the Oracle Identity Manager database user
    •     The name of the tablespace to be created for storing Oracle Identity Manager data
    •     The directory in which to store the data file for the Oracle Identity Manager tablespace
    •     The name of the data file ( no need to append the .dbf extension)
    •     The name of the temporary tablespace
    4.     Check the prepare_xell_db.lst log file located in the directory where the xell_db_prepare script was run from to see execution status and additional information.

  • Error while installing OFM 11g - Oracle Identity management suite 11g

    Hi,
    I am getting following error while installing Oracle Identity management suite 11g (Oracle Internet Directory & Oracle Virtual Directory) on Red Hat Linux 5.0.
    "Error in invoking target 'client_sharedlib' of makefile '/apps/idm/Oracle/OracleHome/Oracle_Home/rdbms/lib/ins_rdbms.mk"
    the same error is repeating for others also i.e. 'all', 'install" etc.
    Can you advice me how to overcome this?
    Regards
    Chinta

    Hi Chinta,
    Pl. check for all gcc and glibc OS packages compatibility with your your OS. This will solve your problem.
    Also check that you are not installing a 32 bit IM software on a 64 bit machine or viceversa.
    regards,
    Sailesh

  • Error on installing Oracle Identity Manager 9.1.0.1 in WebLogic Server 11g

    Hello friends.
    Can you help solve this case:
    I installed Oracle 9.1.0.1 on Oracle Identity Manager Weblogic Server 11g, completing the installation with the following errors: attach the log so I can guide the solution.
    link of the complete log
    http://textbin.com/1c824
    Part of the log**************************************
    With the Partitioning, OLAP, Data Mining and Real Application Testing options".>
    ####<Sep 30, 2011 4:23:04 PM PET> <Info> <JDBC> <idm9> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1317417784538> <BEA-001517> <Connection Pool "xlXADS" using Driver: "Oracle JDBC driver", Version: "11.2.0.2.0".>
    ####<Sep 30, 2011 4:23:18 PM PET> <Info> <Common> <idm9> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1317417798143> <BEA-000628> <Created "30" resources for pool "xlXADS", out of which "30" are available and "0" are unavailable.>
    ####<Sep 30, 2011 4:23:18 PM PET> <Info> <JDBC> <idm9> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1317417798147> <BEA-001124> <Created Connection Pool named xlXADS.>
    ####<Sep 30, 2011 4:23:24 PM PET> <Error> <Store> <idm9> <AdminServer> <[ACTIVE] ExecuteThread: '23' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1317417804279> <BEA-280061> <The persistent store "AdminServer_OIM_JDBCSTORE" could not be deployed: weblogic.store.PersistentStoreException: Can't find JDBC DataSource jdbc/xlDS: javax.naming.NameNotFoundException: While trying to lookup 'jdbc.xlDS' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/xlDS'
    weblogic.store.PersistentStoreException: Can't find JDBC DataSource jdbc/xlDS: javax.naming.NameNotFoundException: While trying to lookup 'jdbc.xlDS' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/xlDS'
         at weblogic.store.admin.JDBCAdminHandler.createDataSource(JDBCAdminHandler.java:107)
         at weblogic.store.admin.JDBCAdminHandler.makeStoreIO(JDBCAdminHandler.java:186)
         at weblogic.store.admin.JDBCAdminHandler.makeStore(JDBCAdminHandler.java:164)
         at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:59)
         at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:240)
         at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
         at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
         at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
         at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:188)
         at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:492)
         at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
         at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:139)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused By: javax.naming.NameNotFoundException: While trying to lookup 'jdbc.xlDS' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/xlDS'
         at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
         at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:247)
         at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
         at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at weblogic.store.admin.JDBCAdminHandler.createDataSource(JDBCAdminHandler.java:102)
         at weblogic.store.admin.JDBCAdminHandler.makeStoreIO(JDBCAdminHandler.java:186)
         at weblogic.store.admin.JDBCAdminHandler.makeStore(JDBCAdminHandler.java:164)
         at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:59)
         at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
         at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
         at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
         at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
         at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:187)
         at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:491)
         at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
         at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:137)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    ####<Sep 30, 2011 4:23:24 PM PET> <Warning> <Management> <idm9> <AdminServer> <[ACTIVE] ExecuteThread: '23' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1317417804321> <BEA-141197> <The deployment of AdminServer_OIM_JDBCSTORE failed.
    weblogic.management.DeploymentException:
         at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:62)
         at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
         at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
         at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
         at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
         at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:188)
         at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:492)
         at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
         at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:139)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused By: javax.naming.NameNotFoundException: While trying to lookup 'jdbc.xlDS' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/xlDS'
         at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
         at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:247)
         at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
         at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at weblogic.store.admin.JDBCAdminHandler.createDataSource(JDBCAdminHandler.java:102)
         at weblogic.store.admin.JDBCAdminHandler.makeStoreIO(JDBCAdminHandler.java:186)
         at weblogic.store.admin.JDBCAdminHandler.makeStore(JDBCAdminHandler.java:164)
         at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:59)
         at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
         at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
         at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
         at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
         at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:187)
         at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:491)
         at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
         at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:137)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    ####<Sep 30, 2011 4:23:24 PM PET> <Error> <JMS> <idm9> <AdminServer> <[ACTIVE] ExecuteThread: '23' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1317417804381> <BEA-040123> <Failed to start JMS Server "AdminServer_OIM_JMSSERVER" due to weblogic.management.DeploymentException: The persistent store "AdminServer_OIM_JDBCSTORE" does not exist.
    weblogic.management.DeploymentException: The persistent store "AdminServer_OIM_JDBCSTORE" does not exist
         at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:313)
         at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:200)
         at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:240)
         at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
         at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
         at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
         at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:188)
         at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:492)
         at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
         at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:139)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    ####<Sep 30, 2011 4:23:24 PM PET> <Warning> <Management> <idm9> <AdminServer> <[ACTIVE] ExecuteThread: '23' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1317417804385> <BEA-141197> <The deployment of AdminServer_OIM_JMSSERVER failed.
    weblogic.management.DeploymentException: Internalrror activating the JMS Server AdminServer_OIM_JMSSERVER: weblogic.management.DeploymentException: The persistent store "AdminServer_OIM_JDBCSTORE" does not exist
         at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:215)
         at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
         at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
         at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
         at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
         at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:188)
         at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:492)
         at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
         at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:139)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused By: weblogic.management.DeploymentException: The persistent store "AdminServer_OIM_JDBCSTORE" does not exist
         at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:313)
         at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:200)
         at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:240)
         at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
         at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
         at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
         at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:188)
         at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:492)
         at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
         at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:139)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    Thanks

    Hi Kevin,
    Make your suggestion, delete the domain and reinstall Oracle Identity Manager, the result was the same error, this happens when I start the xlStartServer.sh
    Exception in thread "QuartzWorkerThread-2" java.lang.OutOfMemoryError: PermGen space
    at java.lang.reflect.Proxy.defineClass0(Native Method)
    at java.lang.reflect.Proxy.getProxyClass(Proxy.java:504)
    at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:581)
    at com.thortech.xl.dataaccess.tcDataBaseClient.bindToInstance(Unknown Source)
    at com.thortech.xl.dataaccess.tcDataBaseClient.<init>(Unknown Source)
    at com.thortech.xl.server.tcDataBaseClient.<init>(Unknown Source)
    at com.thortech.xl.client.dataobj.tcDataBaseClient.<init>(Unknown Source)
    at com.thortech.xl.scheduler.core.quartz.QuartzWrapper$TaskExecutionAction.run(Unknown Source)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    at weblogic.security.Security.runAs(Security.java:41)
    at Thor.API.Security.LoginHandler.weblogicLoginSession.runAs(Unknown Source)
    at com.thortech.xl.scheduler.core.quartz.QuartzWrapper.execute(Unknown Source)
    at org.quartz.core.JobRunShell.run(JobRunShell.java:178)
    at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:477)
    CJava HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
    ^CJava HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
    Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
    Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
    Exception in thread "QuartzScheduler_NON_CLUSTERED_MisfireHandler" java.lang.OutOfMemoryError: PermGen space
    Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
    java.lang.OutOfMemoryError: PermGen space
    ^CJava HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
    Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
    Exception in thread "[ACTIVE] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
    java.lang.OutOfMemoryError: PermGen space
    Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
    Thanks
    Edited by: JLK on Oct 2, 2011 11:35 PM
    Edited by: JLK on Oct 2, 2011 11:37 PM

  • Calling From Oracle Forms 11g patch set 2(11.1.1.3.0) to  Oracle Reports 1

    Hi
    While calling From Oracle Forms 11g patch set 2(11.1.1.3.0) to Oracle Reports 11g patch set 2(11.1.1.3.0) I found unable to run report error
    But its finely working in 10g. The Place of error is in find_report_object
    Is any solution to resolve this problem like any registry setting or patches to solve this problem
    Please guide me
    Regards
    Murali N S

    I was able to download it from this link:
    [http://download-llnw.oracle.com/otn/java/jdeveloper/11.1.1.3.0/jdevstudio11113install.exe]
    on the general 11g Fusion download page at:
    [http://www.oracle.com/technology/software/products/middleware/index.html]
    Although the site does appear to be having problems. I got intermittent errors of the page/server not being available.

  • Oracle Identity Manager 9.1.0.2 and Oracle Weblogic server 11g R1 b(10.3.1)

    Hi,
    can we Install Oracle Identity Manager 9.1.0.2 version on Oracle Weblogic server 11h R1 b(10.3.1)?
    Is it OIM 9.1.0.2 compatible to install on Oracle Weblogic server 11h R1 b(10.3.1).
    Early response is appreciated

    Check this
    http://www.oracle.com/technology/software/products/ias/files/idm_certification_101401.html#BABGBGHI
    And Oracle has mentioned that
    *2.1 Certified Application Servers*
    Note: There is no change in application server certification from
    release 9.1.0.1 to release 9.1.0.2.
    Oracle WebLogic Server 10.3
    But you can try with new version of Weblogic. It shouldn't create any problem.

Maybe you are looking for