Install Oracle Access Manager in existing Access Manager domain

Hi
I am operator of a windows system with Oracle Access Manager installed.
We use OAM for SSO against Webpages in OIM running on Jboss, and now we are going to implement against a WebLogic webapplication too.
The userbase is standard Active Directory
I did not set up OAM myself so I'm not completely sure how it works.
To be able to test the SSO solution given by an external provider, I need to have a proper stage environment.
My idea is to set up another OAM on another server, wich points towards the same AD domaincontroller as the existing OAM
Is this possible? In the installation guide I find that the new AccessManager system should be added into the existing OAM configuration , before we turn of the existing OAM and then install the complete OAM on the new server. Then we can turn on the existing OAM again, and implement them as clusters. I would like them to be two indipendent instances not affecting one another, but in the same AD domain to be able to test features in one of them and use the other as the production server.
My fear is that I "mess up" the form in AD created from the old OAM, and that way mess the upp production environment.
Edited by: user631873 on 11.sep.2009 06:22

Hi,
Technically, you can certainly set up a new OAM infrastructure which points to the existing AD instance. You could do this in a number of ways, for example:
- set up the new instance so that it points to the same users and configuration branch as the existing instance, so that the new instance is effectively just an extension of the existing instance (with extra Identity and Access Servers, etc) ;
- set up the new instance so that it points to the same AD instance, but uses different User searchbase and Config branch. In this case the new instance is more or less completely separate, but it happens to use the same directory ;
- set up the new instance so that it points to the same Users, but a different Config branch, in which case the new instance has independed OAM configuration (policies, authentication schemes etc) but operates on the same user base.
(In OAM you can define separate ldap locations for the Users, Identity Config and Access Config.)
It depends on exactly what you want, but if the idea is to have a proper stage environment, then it is usually better for them to be completely independent, including the directory. OAM can update users as well as policies, and additionally different major versions of OAM have different schemas, so there are risks when using the same directory instance. Load testing is also an issue, since the directory is accessed extensivley by OAM.
Regards,
Colin

Similar Messages

  • Installing oracle ops center with a Customer-Managed Database.

    Hi Everyone,
    I am trying to install oracle ops center with a Customer-Managed Database.
    I followed this document http://docs.oracle.com/cd/E27363_01/doc.121/e25139.pdf
    but I fail.
    this is the error I get
    Executing job: jobs/40installOracle.pl --install  --remoteDBprops=/var/tmp/RemoteDBProps.txt
    40installOracle.pl Job Start = Wed Aug  6 11:16:25 2014
    looking for props file: /mnt/xvmoc_full_bundle/./Linux_i686/Product/installer/scripts/localOracleConfig.propertieslooking for alter storage file: /mnt/xvmoc_full_bundle/./Linux_i686/Product/installer/scripts/alterStorage.sqlRestarting install at state=done_install_ic
    Skipping Step:PrepOraDB because currentState=done_install_ic
    Skipping Step:Install IC because currentState=done_install_ic
    Error: Failed to get a database connection: Connection refused
    satadm: ERROR:    --- Failed to verify database
    Cannot verify remote database
    Please fix the problem and then try this step again.
    For a full log of the failed install see the file: /var/tmp/installer.log.28153.
    t. Try this step again (correct the failure before proceeding)
    x. Exit
    this is my RemoteDBProps.txt
    mgmtdb_appuser=OPSCENTER
    mgmtdb_password=xxxxxxxx
    mgmtdb_roappuser=OPSCENTER_RO
    mgmtdb_ropassword=xxxxxxx
    mgmtdb_dburl=jdbc:oracle:thin:@192.168.1.100:1521/oem
    I tested the connection to the sql using OPSCENTER and is working fine.
    What am I doing wrong?
    kind regards
    Albert Boqo

    Hi Albert,
    which Version of remote DB do have installed ?
    As the error indicates that the error say sqlpplus can't connect to it.
    Is the Oracle listener running for port 1521 ?
    Error: Failed to get a database connection: Connection refused
    satadm: ERROR:    --- Failed to verify database
    example to verify the status:
    /export/home/oracle/u01/app/oracle/product/11.2.0/db_1/bin/lsnrctl status
    and what is ../oracle/product/11.2.0/db_1/network/admin/tnsnames.ora
    configured is these same port/hostname as in RemoteDBProps.txt
    Regards
    Klaus M

  • Possible to install Oracle EBS R12 on existing (shell) Oracle 11.1.0.7 DB?

    Is it possible to install Oracle EBS R12 on existing (shell) Oracle 11.1.0.7 DB?

    user4434301 wrote:
    OK...I could be crazy, but I didn't see doing an installation of EBS R12 on a pre-existing 11.1.0.7 DB in there anywhere. It looked like the regular install directions. Are you sure?If you mean to say if you can install R12 with an existing EBS/standalone database then the answer is No.
    If you mean to say if you can lay down R12 software (to upgrade from 11i) with an existing EBS database then the answer is Yes.
    I hope it is clean now.
    Thanks,
    Hussein

  • Installing Oracle XE when ORACLE_HOME exists

    I have a Windows 2003 Server box that has Oracle Client 10g already installed. This client is needed to connect to a production database. Can I install Oracle XE without destroying the original client installation?

    Yes.

  • Issue with Installing Oracle 10g R2 on a Windows 2008 Domain Controller

    I'm assigned a evaluation task for my company. The task invoke to install oracle in my Domain Controller Server.
    I got "ORA-12560: TNS:protocol adapter error" when I installed ORACLE 10g R2 for Win2K8 on my Windows 2008 (a Domain Controller Server). It happened in the create predefined database period.
    I tried to google and noted that there are some RUMOS say "We cannot deploy ORACLE on a Domain Controller, It's impossible"
    Is this true? Please, Please advise!
    Thansk,

    This is a link to a same issue
    Creating instance oracle 10.2.0.4 on Windows 2008 32bit

  • Installing Oracle BPM suite, when SOA and BAM domain are already installed

    Hi Gurus
    I have installed already Oracle SOA domain now I have to install Oracle BPM suite, How to install it with no effect on already installaton.
    Please guide,
    Aamir

    Hi Aamir,
    Shutdown the database all the servers. Start the configuration wizard again(SOAORACLE_HOME/common/bin/config.sh) and select BPM and finish it. (SOA and BPM share the same schemas)
    Start the servers. Now you can see that BPM is configured with your soa server.
    To check whether everything is fine, login to AdminConsole , goto Deployments and check whether oracle.bpm.runtime(11.1.1,11.1.1) is shown as "Active"
    thanks,
    Murugesh

  • Problems Installing Oracle Metadata Repository into Existing Database

    Folks,
    I'm slowly going through the process of installing the Metadata Repository into a 10g database, using RepCA I've managed to determine all the DB parameters required for setting etc. The only thing RepCA now reports is missing is the Ultrasearch schema & packages.
    I've copied the ultrasearch dirs from the RepCA distribution and placed them in my $ORACLE home dir, I've also attempted to run the admin install script 'wk0setup.sql' which throws out several errors listed below. If anyone has successfully gone through this process on Solaris I would love to hear your about your experience & advice.
    Error 1. =================================================
    User is WKSYS
    ... loading ultrasearch_db.jar
    call sys.dbms_java.loadjava('-v -f -r -s -g PUBLIC $ORACLE_HOME/ultrasearch/lib/ultrasearch_db.jar', '((* wksys) (* public))')
    ERROR at line 1:
    ORA-29532: Java call terminated by uncaught Java exception:
    oracle.aurora.server.tools.loadjava.ToolsError: Error during loadjava: Failures
    occurred during processing. Check trace file for details
    Error 2 (File Doesn't exist at all) ==============================
    SP2-0310: unable to open file "/oracle/1020a/ultrasearch/admin/wk0launchq.pkh"
    Error 3 (Again the file doesn't exist at all) ========================
    SP2-0310: unable to open file "/oracle/1020a/ultrasearch/admin/wk0launchq.plb"
    ===========================================================
    Regards
    Austin

    Hi guys,
    I have used copy of that package from Oracle Identity Management installation, version 10.1.4.0.1 and have been able to complete manual Ultra Search installation. It's valid in dba_registry. After that I did run RepCA and metadata schemas have been created successfully in existing database, version 10.2.0.2. Be careful about database version, only 10.2.0.2 is certified with Oracle Identity management, so you need to run patch for upgrade to 10.2.0.2.
    Hope this helps.
    Dali
    Message was edited by:
    dallyz7

  • Installing Oracle for SAP on existing non-SAP RDBMS

    The title says it all -
    I haven't been able to find any real docs supporting or not supporting the practice of using an existing Oracle 10.2 RDBMS to add an SAP DB.  I know it's technically possible, but since the SAP Oracle installer is configured to build a new RDBMS for each SAP instance/DB installation, I'm wondering if it can be altered and piggy back on an existing one.
    The reason is I have a customer who would like to do this so they can continue to use an existing DEV Oracle server without adding the stress of an indepedent set of oracle binaries running, and consuming resources.

    > But aside from that - let's assume the release and patch levels from their own DBs are equal to the requirements from SAP.  What other considerations/issues/supportabilty problems might be encountered?
    If it's not a production system you could certainly go for it.
    I think though, that it's MUCH LESS maintenance work using a second ORACLE_HOME than to try to fiddle with the huge amount of single/interim patches SAP requires. If you just check
    Note 871096 - Oracle 10.2.0: Patches/patch collections for Oracle 10.2.0.2 (59 interim patches)
    Note 1137346 - Oracle 10.2.0: Patches/patch collections for Oracle 10.2.0.4 (39 interim patches)
    I can imagine you having a pretty hard time aligning that with the other non-SAP databases. On top may come incompatibilities with OPatch (SAP uses a "special OPatch") where you may need to switch between the official one and the "SAP-one" depending on which patch you install.
    The only additional resources the new ORACLE_HOME uses is harddisk space (some GB) - which shouldn't be more expensive than the work you'll need to invest to keep the system and working for both.
    Technically it can be done - certainly.
    Markus

  • 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

  • Problem installing Oracle Identity Manager Server  9.1

    Hello,
    I try to install oracle identity Manager Server 9.1, but I'm having a problem.
    Oracle identity manager 9.03 is already installed with jboss-4.0.3SP1 and j2sdk1.4.2_15
    and oracle 10.2.0
    So I follow these steps to clean out the db:
    1. Drop tablespace: drop tablespace oimtbs including contents;
    2. Drop user: drop user oimuser cascade;
    and ran prepare_xl_db.bat as instructed. No errors in the log.
    I ran the DiagonasticDashboard : the db setup was fine.
    When I ran the installer "setup_server.exe", i haved this message :
    Folowing Error occured during schema creation
    Error encountered while loading database script
    E:\OIM_Install\OIM9100\installServer\Xellerate/db/oracle/xell.sql
    Please contact your DBA!
    maximum key length (1478) exceeded
    Does anybody have any idea what this error is about ?
    Thanks.

    Index IDX_LKV_LKV_ENCODED on Table LKV (Column :- LKV_ENCODED - VARCHAR2(3000)) is failing on 2k block size. Though all the Indexes are working fine with the 4k block size.
    But OIM Dev team recommends to create the 8k block size for the Index storage.
    Because the blocksize affects the number of keys within each index node, it follows that the blocksize will have an effect on the structure of the index tree. All else being equal, large blocksizes will have more keys, resulting in a flatter index than the same index created in a 2k tablespace. A large blocksize will also reduce the number of consistent gets during index access, improving performance for scattered reads access.
    HOW TO CREATE THE INDEXES IN LARGER BLOCKSIZE TABLESPACE
    In the existing database:-
    Create a tablespace with the 8k blocksize, For Example
    First,
    Set the system cache size for that particular db block size
    sql> alter system set db_8k_cache_size=100M;
    sql> CREATE TABLESPACE db_8k_tablespace DATAFILE 'C:/oracle/product/10.2.0/oradata/8k_file.dbf' SIZE 100M BLOCKSIZE 8192;
    Then
    Reorganize the Index using command:-
    sql> Alter Index <Index_Name> Rebuild tablespace <Tablespace_Name>
    Regards,
    Neeraj Goel

  • Can't install Oracle Test Manager

    Hi,
    I’m trying to install Oracle Test Manager and I have got an error message on XE installation step: “installation of OracleXE failed.”
    The first line of log file says : “OXE_Detect: No OATS installed version found. Detecting external OXE version.
    However there is no trace of XE, neigther in Program Files nor in Services. Only the following Oracle services exist:
    •     Oracle Application Testing Suite Helper Service (Open Scipt) =>Running
    •     OracleMTSRecoveryService
    •     Oracleora9i_homeClientCache
    Is there anything to remove in Registry or somewhere else?
    Thanks by advance for your help
    Edited by: user8891760 on 4 juin 2010 00:21

    Hi,
    You can validate OID installation through 'opmnctl' and/or 'ldapbind'. You can access 'Oracle Directory Services Manager' through a browser using the url -
    'http://<host>:<port>/odsm/faces/odsm.jspx'.
    Here is a link which shows screenshots of the overview of 'Oracle Directory Services Manager'.
    -- Pramod Aravind

  • Error when installing Oracle Identity Manager 9.1.0.1

    Hello friends,
    I installed Oracle Identity Manager 9.1.0.2 Oracle Weblogic Server on a cluster, at the time of treaties authenticated in the web console of Oracle Identity Manager, I get the following message:
    A system error was encountered.
    View the full log here
    http://pastebin.com/ucN1LHP4
    BUILD FAILED
    /opt/oim/xellerate/setup/setup.xml:447: The following error occurred while executing this line:
    /opt/oim/xellerate/setup/weblogic-setup.xml:318: weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Task 3 failed: [Deployer:149026]deploy application Nexaweb on oimCluster.
    Target state: deploy failed on Cluster oimCluster
    javax.servlet.ServletException: [HTTP:101249][ServletContext@59809215[app:Nexaweb module:/Nexaweb path:/Nexaweb spec-version:null]]: Servlet class com.nexaweb.loader.ClientLoaderServlet for servlet ClientClassServlet could not be loaded because the requested class was not found in the classpath .
    java.lang.ClassNotFoundException: com.nexaweb.loader.ClientLoaderServlet.
         at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:551)
         at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
         at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
         at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
         at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
         at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
         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)
         at org.apache.tools.ant.ProjectHelper.addLocationToBuildException(ProjectHelper.java:508)
         at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:418)
         at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
         at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
         at org.apache.tools.ant.Task.perform(Task.java:348)
         at org.apache.tools.ant.Target.execute(Target.java:357)
         at org.apache.tools.ant.Target.performTasks(Target.java:385)
         at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
         at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
         at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
         at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
         at org.apache.tools.ant.Main.runBuild(Main.java:758)
         at org.apache.tools.ant.Main.startAnt(Main.java:217)
         at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
         at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
    Caused by: /opt/oim/xellerate/setup/weblogic-setup.xml:318: weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Task 3 failed: [Deployer:149026]deploy application Nexaweb on oimCluster.
    Target state: deploy failed on Cluster oimCluster
    javax.servlet.ServletException: [HTTP:101249][ServletContext@59809215[app:Nexaweb module:/Nexaweb path:/Nexaweb spec-version:null]]: Servlet class com.nexaweb.loader.ClientLoaderServlet for servlet ClientClassServlet could not be loaded because the requested class was not found in the classpath .
    java.lang.ClassNotFoundException: com.nexaweb.loader.ClientLoaderServlet.
         at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:551)
         at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
         at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
         at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
         at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
         at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
         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)
         at weblogic.ant.taskdefs.management.WLDeploy.execute(WLDeploy.java:357)
         at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
         at sun.reflect.GeneratedMethodAccessor167.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
         at org.apache.tools.ant.Task.perform(Task.java:348)
         at org.apache.tools.ant.Target.execute(Target.java:357)
         at org.apache.tools.ant.Target.performTasks(Target.java:385)
         at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
         at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
         at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
         at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:416)
         ... 16 more
    Caused by: weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Task 3 failed: [Deployer:149026]deploy application Nexaweb on oimCluster.
    Target state: deploy failed on Cluster oimCluster
    javax.servlet.ServletException: [HTTP:101249][ServletContext@59809215[app:Nexaweb module:/Nexaweb path:/Nexaweb spec-version:null]]: Servlet class com.nexaweb.loader.ClientLoaderServlet for servlet ClientClassServlet could not be loaded because the requested class was not found in the classpath .
    java.lang.ClassNotFoundException: com.nexaweb.loader.ClientLoaderServlet.
         at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:551)
         at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
         at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
         at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
         at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
         at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
         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)
         at weblogic.Deployer.run(Deployer.java:72)
         at weblogic.Deployer.mainWithExceptions(Deployer.java:62)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at weblogic.ant.taskdefs.management.WLDeploy.invokeMain(WLDeploy.java:419)
         at weblogic.ant.taskdefs.management.WLDeploy.execute(WLDeploy.java:349)
         ... 28 more
    Caused by: weblogic.deploy.api.tools.deployer.DeployerException: Task 3 failed: [Deployer:149026]deploy application Nexaweb on oimCluster.
    Target state: deploy failed on Cluster oimCluster
    javax.servlet.ServletException: [HTTP:101249][ServletContext@59809215[app:Nexaweb module:/Nexaweb path:/Nexaweb spec-version:null]]: Servlet class com.nexaweb.loader.ClientLoaderServlet for servlet ClientClassServlet could not be loaded because the requested class was not found in the classpath .
    java.lang.ClassNotFoundException: com.nexaweb.loader.ClientLoaderServlet.
         at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:551)
         at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
         at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
         at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
         at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
         at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
         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)
         at weblogic.deploy.api.tools.deployer.Jsr88Operation.report(Jsr88Operation.java:542)
         at weblogic.deploy.api.tools.deployer.Deployer.perform(Deployer.java:140)
         at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:88)
         at weblogic.utils.compiler.Tool.run(Tool.java:158)
         at weblogic.utils.compiler.Tool.run(Tool.java:115)
         at weblogic.Deployer.run(Deployer.java:70)
         ... 35 more
    As I can solve this problem, not to reinstall everything again
    thanks

    Not sure if I understand your issue correctly. Your deployment failed during the installation and you have started the servers and trying to login?
    When installing OIM in a clustered WLS domain, the docs specify various cluster configurations needed to be completed in the WLS Admin Console before running the OIM installer. These steps DO NOT include starting up of the first managed server. In fact, if you start up the managed server then you may very well run into deployment issues after the OIM application is built. Instead, when installing OIM, the installer detects that not all nodes are on-line and so will queue the deployment for later. Deployment then takes place in later steps when you are instructed to restart the app server and start managed nodes.
    Thus was your managed server running when you were doing the installation? That has caused the issue. I would suggest to dump this domain (save the .xldatabasekey) if you don't wanna to dump the database part and start the installation again BUT don't start the managed server while doing the installation.
    HTH,
    BB

  • Installing oracle management agent 12.1.0.2.0 in silent mode.

    version: 12.1.0.2.0
    platform: IBM Aix power systems 64bit
    I installed the oracle management service along with the oracle management agent that comes along with the the first installation. I deinstalled the first installed OMA and tried to install it again using the silent install mode with the response file.
    (oms host and the oma host are the same)
    among the 3 modes of silent install described in the installation guide, i used agent deploy method.
    Here are the steps i followed with the install
    1. this the status of my OMS
    <oracle>chh-aix-beta/oem12c/product/oms/bin> ./emctl status oms -details
    Oracle Enterprise Manager Cloud Control 12c Release 2
    Copyright (c) 1996, 2012 Oracle Corporation.  All rights reserved.
    Enter Enterprise Manager Root (SYSMAN) Password :
    Console Server Host        : chh-aix-beta
    HTTP Console Port          : 7788
    HTTPS Console Port         : 7799
    HTTP Upload Port           : 4889
    HTTPS Upload Port          : 1159
    EM Instance Home           : /oem12c/product/gc_inst/em/EMGC_OMS1
    OMS Log Directory Location : /oem12c/product/gc_inst/em/EMGC_OMS1/sysman/log
    OMS is not configured with SLB or virtual hostname
    Agent Upload is locked.
    OMS Console is unlocked.
    Active CA ID: 1
    Console URL: https://chh-aix-beta:7799/em
    Upload URL: https://chh-aix-beta:1159/empbs/upload
    WLS Domain Information
    Domain Name      : GCDomain
    Admin Server Host: chh-aix-beta
    Managed Server Information
    Managed Server Instance Name: EMGC_OMS1
    Managed Server Instance Host: chh-aix-beta
    WebTier is Up
    Oracle Management Server is Up2. I got the version and the platform info of the oms by doing the following
    <oracle>chh-aix-beta/oem12c/product/oms/bin> ./emcli get_supported_platforms
    Getting list of platforms ...
    Check the logs at /oem12c/product/gc_inst/em/EMGC_OMS1/sysman/emcli/setup/.emcli/agent.log
    About to access self-update code path to retrieve the platforms list..
    Getting Platforms list  ...
    Version = 12.1.0.2.0
    Platform = IBM AIX on POWER Systems (64-bit)
    Platforms list displayed successfully.3. I downloaded the management agent software by doing the following ()
    $<OMS_HOME>/bin/emcli get_agentimage -destination=/oem12102 -platform="IBM AIX on POWER Systems (64-bit) "  -version=12.1.0.2.04. I unzipped the management agent software.
    5. I edited the response file as follows. (i edited only the oms_host, em_upload_port, agent_registration_password, since they are the only ones that are mandatory)
    OMS_HOST=172.16.24.65
    EM_UPLOAD_PORT=1159
    AGENT_REGISTRATION_PASSWORD=cchorcl01
    #AGENT_INSTANCE_HOME=
    #AGENT_PORT=
    b_startAgent=true
    #ORACLE_HOSTNAME=
    #s_agentHomeName=
    EM_INSTALL_TYPE="AGENT"6. then i ran the AgentDeploy.sh script using the following.
    ./agentDeploy.sh -ignorePrereqs AGENT_BASE_DIR=/oem12c/base/agent RESPONSE_FILE=/oem12102/agent.rsp(I ignored the prereqs because, i was getting an error with the hostname and the hostname is correct)
    7. this the following output i am getting after running step 6.
    -e Validating the OMS_HOST & EM_UPLOAD_PORT
    Executing command : /oem12c/base/agent/core/12.1.0.2.0/jdk/bin/java -classpath /oem12c/base/agent/core/12.1.0.2.0/jlib/agentInstaller.jar:/oem12c/base/agent/core/12.1.0.2.0/oui/jlib/OraInstaller.jar oracle.sysman.agent.installer.AgentInstaller /oem12c/base/agent/core/12.1.0.2.0 /oem12102 /oem12c/base/agent -prereq
    Validating oms host & port with url: http://172.16.24.65:1159/empbs/genwallet
    Validating oms host & port with url: https://172.16.24.65:1159/empbs/genwallet
    Return status:3
    Unzipping the agentcoreimage.zip to /oem12c/base/agent ....
    12.1.0.2.0_PluginsOneoffs_212.zip
    Executing command : /oem12102/unzip -o /oem12102/12.1.0.2.0_PluginsOneoffs_212.zip -d /oem12c/base/agent
    Executing command : /oem12c/base/agent/core/12.1.0.2.0/jdk/bin/java  -d64 -classpath /oem12c/base/agent/core/12.1.0.2.0/oui/jlib/OraInstaller.jar:/oem12c/base/agent/core/12.1.0.2.0/oui/jlib/xmlparserv2.jar:/oem12c/base/agent/core/12.1.0.2.0/oui/jlib/srvm.jar:/oem12c/base/agent/core/12.1.0.2.0/oui/jlib/emCfg.jar:/oem12c/base/agent/core/12.1.0.2.0/jlib/agentInstaller.jar:/oem12c/base/agent/core/12.1.0.2.0/oui/jlib/share.jar oracle.sysman.agent.installer.AgentInstaller /oem12c/base/agent/core/12.1.0.2.0 /oem12102 /oem12c/base/agent /oem12c/base/agent/agent_inst AGENT_BASE_DIR=/oem12c/base/agent -ignorePrereqs AGENT_BASE_DIR=/oem12c/base/agent RESPONSE_FILE=/oem12102/agent.rsp
    Cloning the agent home...
    Executing command: /oem12c/base/agent/core/12.1.0.2.0/oui/bin/runInstaller -ignoreSysPrereqs -clone -forceClone -silent -waitForCompletion -nowait ORACLE_HOME=/oem12c/base/agent/core/12.1.0.2.0 -responseFile /oem12102/agent.rsp  AGENT_BASE_DIR=/oem12c/base/agent AGENT_BASE_DIR=/oem12c/base/agent RESPONSE_FILE=/oem12102/agent.rsp -noconfig  ORACLE_HOME_NAME=agent12c3 -force b_noUpgrade=true AGENT_PORT=-1
    Clone Action Logs Location:/software/oracle/logs/cloneActions<timestamp>.log
    Cloning of agent home completed successfully
    Attaching sbin home...
    Executing command: /oem12c/base/agent/core/12.1.0.2.0/oui/bin/runInstaller -ignoreSysPrereqs -attachHome -waitForCompletion -nowait ORACLE_HOME=/oem12c/base/agent/sbin ORACLE_HOME_NAME=sbin12c3 -force
    Attach Home Logs Location:/oem12c/base/agent/core/12.1.0.2.0/cfgtoollogs/agentDeploy/AttachHome<timestamp>.log
    Attach home for sbin home completed successfully.
    Updating home dependencies...
    Executing command: /oem12c/base/agent/core/12.1.0.2.0/oui/bin/runInstaller -ignoreSysPrereqs -updateHomeDeps -waitForCompletion HOME_DEPENDENCY_LIST={/oem12c/base/agent/sbin:/oem12c/base/agent/core/12.1.0.2.0,} -invPtrLoc /oem12c/base/agent/core/12.1.0.2.0/oraInst.loc -force
    Update Home Dependencies Location:/oem12c/base/agent/core/12.1.0.2.0/cfgtoollogs/agentDeploy/UpdateHomeDeps<timestamp>.log
    ERROR: Update home dependency failed.I am getting stuck at updating home dependencies. I dont know what that means. If you have faced similar problems while installing oracle management agent please do share your solution. if you need more info please let me know.

    All these commands are run on the host (hostname=chh-lpar20) where the agent is being installed, and these commands are run as root user.
    ifconfig -a
    en0: flags=5e080863,c0<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,CHECKSUM_OFFLOAD(ACTIVE),PSEG,LARGESEND,CHAIN>
            inet 172.16.28.222 netmask 0xfffffc00 broadcast 172.16.31.255
             tcp_sendspace 131072 tcp_recvspace 65536 rfc1323 0
    lo0: flags=e08084b,c0<UP,BROADCAST,LOOPBACK,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,LARGESEND,CHAIN>
            inet 127.0.0.1 netmask 0xff000000 broadcast 127.255.255.255
            inet6 ::1%1/0
             tcp_sendspace 131072 tcp_recvspace 131072 rfc1323 1ping chh-lpar20
    PING chh-lpar20: (172.16.28.222): 56 data bytes
    64 bytes from 172.16.28.222: icmp_seq=0 ttl=255 time=0 ms
    64 bytes from 172.16.28.222: icmp_seq=1 ttl=255 time=0 msnslookup chh-lpar20
    Server:         172.16.29.213
    Address:        172.16.29.213#53
    ** server can't find chh-lpar20: NXDOMAINnslookup 172.16.28.222
    Server:         172.16.29.213
    Address:        172.16.29.213#53
    ** server can't find 222.28.16.172.in-addr.arpa: NXDOMAINto check the if the port 3872 and 1830-1849 are free I ran the follwoing command
    ./agentDeploy.sh -prereqOnly AGENT_BASE_DIR=/oem12102/base/agent
    this was the result i got inregards to the ports
    Check complete: Passed
    ========================================================
    Performing check for PortCheck
    Checking for port availability and hostname validity...
    Trying for host : chh-lpar20/172.16.28.222 and port : 3872
    Trying for host : chh-lpar20/192.168.12.23 and port : 3872
    Port= 3872 is busy.
    Trying for host : chh-lpar20/172.16.28.222 and port : 1830
    Trying for host : chh-lpar20/192.168.12.23 and port : 1830
    Port= 1830 is busy.
    Trying for host : chh-lpar20/172.16.28.222 and port : 1831
    Trying for host : chh-lpar20/192.168.12.23 and port : 1831
    Port= 1831 is busy.
    Trying for host : chh-lpar20/172.16.28.222 and port : 1832
    Trying for host : chh-lpar20/192.168.12.23 and port : 1832
    Port= 1832 is busy.
    Trying for host : chh-lpar20/172.16.28.222 and port : 1833
    Trying for host : chh-lpar20/192.168.12.23 and port : 1833
    Port= 1833 is busy.
    Trying for host : chh-lpar20/172.16.28.222 and port : 1834
    Trying for host : chh-lpar20/192.168.12.23 and port : 1834
    Port= 1834 is busy.
    Trying for host : chh-lpar20/172.16.28.222 and port : 1835
    Trying for host : chh-lpar20/192.168.12.23 and port : 1835
    Port= 1835 is busy.
    Trying for host : chh-lpar20/172.16.28.222 and port : 1836
    Trying for host : chh-lpar20/192.168.12.23 and port : 1836
    Port= 1836 is busy.
    Trying for host : chh-lpar20/172.16.28.222 and port : 1837
    Trying for host : chh-lpar20/192.168.12.23 and port : 1837
    Port= 1837 is busy.
    Trying for host : chh-lpar20/172.16.28.222 and port : 1838
    Trying for host : chh-lpar20/192.168.12.23 and port : 1838
    Port= 1838 is busy.
    Trying for host : chh-lpar20/172.16.28.222 and port : 1839
    Trying for host : chh-lpar20/192.168.12.23 and port : 1839
    Port= 1839 is busy.
    Trying for host : chh-lpar20/172.16.28.222 and port : 1840
    Trying for host : chh-lpar20/192.168.12.23 and port : 1840
    Port= 1840 is busy.
    Trying for host : chh-lpar20/172.16.28.222 and port : 1841
    Trying for host : chh-lpar20/192.168.12.23 and port : 1841
    Port= 1841 is busy.
    Trying for host : chh-lpar20/172.16.28.222 and port : 1842
    Trying for host : chh-lpar20/192.168.12.23 and port : 1842
    Port= 1842 is busy.
    Trying for host : chh-lpar20/172.16.28.222 and port : 1843
    Trying for host : chh-lpar20/192.168.12.23 and port : 1843
    Port= 1843 is busy.
    Trying for host : chh-lpar20/172.16.28.222 and port : 1844
    Trying for host : chh-lpar20/192.168.12.23 and port : 1844
    Port= 1844 is busy.
    Trying for host : chh-lpar20/172.16.28.222 and port : 1845
    Trying for host : chh-lpar20/192.168.12.23 and port : 1845
    Port= 1845 is busy.
    Trying for host : chh-lpar20/172.16.28.222 and port : 1846
    Trying for host : chh-lpar20/192.168.12.23 and port : 1846
    Port= 1846 is busy.
    Trying for host : chh-lpar20/172.16.28.222 and port : 1847
    Trying for host : chh-lpar20/192.168.12.23 and port : 1847
    Port= 1847 is busy.
    Trying for host : chh-lpar20/172.16.28.222 and port : 1848
    Trying for host : chh-lpar20/192.168.12.23 and port : 1848
    Port= 1848 is busy.
    Trying for host : chh-lpar20/172.16.28.222 and port : 1849
    Trying for host : chh-lpar20/192.168.12.23 and port : 1849
    Port= 1849 is busy.
    Check complete. The overall result of this check is: Failed <<<<
    Check complete: Failed <<<<
    Problem: Either port is unavailable or hostname configuration is not valid.
    Recommendation: Make sure the port is available and the hostname configuration i
    s proper.I don't know what to make of the results I got for executing the nslookup command.

  • How to install oracle connection manager on solaris 10

    I have installed oracle application server 10.1.2 on solaris 10. How do i install oracle connection manager utility.
    My end goal is to use applets/jdbc.
    Thanks

    Thank you Zettabyte!!
    Folks, network printers should NOT BE configured like this:
    lpadmin -p somequeue -s someprinter
    that creates a remote style queue and puts all the I/O and processing capability on the basic LPD listener present on network printer interfaces. This will cause problems down the road, not to mention that you cannot control access, get any logging, filter content, or control banner pages.
    Network printers should use any software (or PPD file) supplied by the vendor over the basic lpadmin/netstandard config.
    You can install CUPS, but Oracle won't support it until it's part of the OS (S11, apparently).
    The "System Administration Guide: Solaris Printing" is highly recommended for those administering printers on Solaris.

  • Install oracle enterprise manager

    Hi, I have installed Oracle 10g wanted to install Enterprise manager please help me I'm new in this arena. I don't have cd, I have installed from Oracle side
    Ben

    If you have created a database with the Database Creation Assistant, you have already installed Enterprise Manager. Just make sure the dbconsole is started.
    set/export ORACLE_SID=<dbsid>
    $ORACLE_HOME/bin/emctl start dbconsole
    You can find the URL to access Enterprise Manager DB Control with the following:
    $ORACLE_HOME/bin/emctl status dbconsole

Maybe you are looking for

  • Going to the Bar for a friend = issue?

    Hi all, My friend's has been experiencing issues with their MagSafe adapter (burned, frayed wire). However, my friend is physically unable to go to the local Apple Store/Genius Bar themselves, so I offered to take it to Apple for them, since it is ne

  • Firefox v15.0.1 Back button disappears

    I'm having trouble whenever I left-click a link in a webpage, the link opens in the same tab, but then the back button is grayed out and unavailable. I tried backing up my bookmarks and then created an entirely new profile, restored my bookmarks. Sti

  • Disposition codes not working/ not displaying on CAD when new call arrives and recieved

    Hi, When Agents phone ring they should get a list of disposition codes on their screen however they have the error message as shown in below screenshot this error stays on the screen and doesn't go at the end of the call. CAD v8.5 Guys any idea ?? Th

  • How to avoid return receipt

    Hello all, I am using class cl_bcs for email service and it is working fine. But the problem is after the mail is sent to the receipients, there is a Delivery report ( RETURN RECEIPT ) being sent to the sender informing about all the users to whom th

  • Transfering data between sap and biw

    Hello everyone, I am new biw and am trying to establish communication between r/3 and biw. I have created logical systems in both and I am able to replicate data sources but when I create a infopackage and schedule a job I am not having much success