ORACLE RESOURCE MANAGER - POOR RESULTS

Hi all.
Created a smple test case - basically consumed FULL server CPU with queiing by generic user.
Then came in with a user who has 40% allocaiton at P1.
here are the basic results
NO LOAD (server idle) => 7 secs
100% LOAD (user in TOP CPU group -> 40% at P1) => 35 secs
100% LOAD (user in TOP CPU group -> 50% only at P5) => 90 secs
So - on a basic level - ORM works to prevent queries going from 7 secs to 90 secs.
But from an SLA perspective the business isn't going to be too happy if it still goes from 7 to 34 secs ??
thoughts ?

bump

Similar Messages

  • Oracle Resource Manager

    hi,
    In the GROUP section of the ubb file I have defined a Oracle Resource Manager.
    GRP1
    LMID = SITE1 GRPNO =1
    TMSNAME = TMS_ORA TMSCOUNT = 2
    OPENINFO = "Oracle_XA:Oracle_XA+Acc=P/usr1/usr1+SesTm=0+LogDir=/tmp/xa_logs+Objects=T+Loose_Coupling=false+SesWt=60"
    when i boot the application, the TMS_ORA gets booted.
    Now if I change just the login information to another valid user (say usr2/usr2)of
    the database in the OPENINFO parameter and try to boot the TMS_ORA fails.
    Can you please let me know as to what can be the possible reason behind this.
    Thanks

    Hi,
    If you are using ORACLE Version 7.X,
    You should grant the SELECT privilege of v$xatrans$ to usr2.
    The checking is like the following.
    1. sqlplus usr2/usr2
    2. desc v$xatrans$
    Here, If the desc command's result gets a error, then the privilege is
    not granted to usr2.
    info) v$xatrans$ view table owner is sys, therefore you should login sys
    using sqlplus
    and then "grant select on v$xatrans$ to usr2" statement is
    executed in sqlplus prompt.
    3. reboot TMS.
    If you are using ORACLE Version 8.X,
    Maybe, You should grant the SELECT privilege of DBA_PENDING_TRANSACTIONS
    view table to usr2.
    The checking is like the following.
    1. sqlplus usr2/usr2
    2. desc dba_pending_transactions
    Here, If the desc command's result gets a error, then the privilege is
    not granted to usr2.
    info) DBA_PENDING_TRANSACTIONS view table owner is sys, therefore you
    should login sys using sqlplus
    and then "grant select on dba_pending_transactions to usr2"
    statement is executed in sqlplus prompt.
    3. reboot TMS.
    This hopes help.
    Thanks.
    "vipul" <[email protected]> wrote in message
    news:[email protected]..
    >
    hi,
    In the GROUP section of the ubb file I have defined a Oracle ResourceManager.
    >
    GRP1
    LMID = SITE1 GRPNO =1
    TMSNAME = TMS_ORA TMSCOUNT = 2
    OPENINFO ="Oracle_XA:Oracle_XA+Acc=P/usr1/usr1+SesTm=0+LogDir=/tmp/xa_logs+Objects=T+L
    oose_Coupling=false+SesWt=60"
    >
    >
    when i boot the application, the TMS_ORA gets booted.
    Now if I change just the login information to another valid user (sayusr2/usr2)of
    the database in the OPENINFO parameter and try to boot the TMS_ORA fails.
    Can you please let me know as to what can be the possible reason behindthis.
    >
    Thanks

  • Oracle Profile Vs Oracle Resource Manager in Oracle 11g

    Hi Friends,
    Whats is the Avantages / Dis advantages of using Oracle Profile and Oracle Resource Manager to limit the oracle resources to oracle users in Oracle 11.2.0.1
    Regards,
    DB

    If you have a single database servicing multiple Services / Applications / Schemas (e.g. a typical database consolidation), you could use Profiles and Resource Manager to place limits on resource usage by Service / Application / Schema. That way, for example, a 32 CPU database server running a single database can still limit the number of cores for each Service / Application / Schema using the Resource Manager.
    Hemant K Chitale

  • Oracle Resource Manager function with SAP BI7

    Hi,
    Have anyone considered or using Oracle Database Resource Manager (Oracle 10.2) feature for SAP BI application in your site? I dont see a single OSS hit on this feature.
    We have a SAP BI system that has few power users (who can run large STAR_TRANSFORMATION queries that analyzes large volume of data) and the main user community (our sales force > 3000+ users) who can run smaller queries of such nature or queries of different types.
    We want to see if there is any way we can control the resource utilization on the database server.
    Thanks in advance,
    Raj

    > Of course, this would require an additional specifications such as SERVICE in the TNS and Listener files.
    Yes - but I'm not sure if that would give the necessary effect. Once the statement reaches the database kernel engine, it gets processed, no matter if you limit the TNS/listener usage because TNS is no more involved when the statement reaches the OLAP engine.
    > In the BI environment, I'm thinking you need this db feature to control database resources when loads and reports overlaps or even several small and large queries run concurrently despite however many app server a system has, all these come to the database.
    I think SAPs answer is: Buy a bigger box (or use RAC to distribute the load)
    > The big question is whether SAP would support such a setup.
    The feature is not listed explicitly in note 105047 - Support for Oracle functions in the SAP environment. I'd make a call at BC-DB-ORA and ask what they think about that.
    I understand your problem very well but I doubt, that there's an easy way of accomplishing this with standard tools.
    Markus

  • Error Implementing Oracle Projects Resource Management

    I'm implementing Oracle Resource Management and I've followed all the requirement/steps in the Implementation Guide. I realized that after I changed the flag "Include in Utilization" to Yes in the Job Definition, the request showed me the following error in log:
    Current NLS_LANG and NLS_NUMERIC_CHARACTERS Environment Variables are :
    American_America.WE8ISO8859P1
    Enter Password:
    REP-1401: 'beforereport': Fatal PL/SQL error occurred.
    ORA-06503: PL/SQL: Function returned without value
    REP-0069: Internal error
    REP-57054: In-process job terminated:Terminated with error:
    REP-1401: 'beforereport': Fatal PL/SQL error occurred.
    ORA-06503: PL/SQL: Function returned without value
    Thanks in Advance.

    Hi Dean and Dina,
    Thanks for your answers. Following is the missing info:
    - Yes, we are using the AIA PIP
    - We are using 'Workplan enabled' projects for integration with a 'Partially Shared Structure'
    - In integration options, we are only integrating 'Workplan' with a 'Working Version'
    - We are trying to send only progress information from P6 to Oracle Projects, not the time card info
    Iniitially, when trying to send progress from P6 to Oracle Projects, we were getting the error - 'You cannot update a published version of the workplan'
    However, after checking the following flags, we stopped getting any errors in AIA/middleware and still not getting any data into Oracle Projects:
    Projects --> Setup --> Integration settings:
    Integrate - Workplan - Send Task - Current Working Version
    Integrate - Workplan - Receive Task
    Workplan --> setup:
    Allow Physical Percent Complete Collection
    Allow Physical Percent Complete Overrides
    Thanks for your help.

  • 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

  • Resource Manager Understanding

    Hi DBA,
    While going through the documents of Oracle Resource Manager , I have a Resource Plan execution can be based on CPU or Forcefully. Means Once the CPU utilization reaches 100% only then resource plan comes into the picture or we can forced it even it is not 100%.
    My doubt is if I allocate a 100% CPU to resource manager plan by creating the consumer group and we are forcing that resource plan,
    If some other application is running on the servers what will be impact on that application, does that application get the CPU.What will the impact on internal system processing (Kernels). How the CPU is going to be distributed ?
    I understand that 100% CPU utilization on a server is different thing and that causes the performance issue.
    Regards
    Sourabh Gupta

    Hi,
    During the month end activity , In our Project CPU and IO utilization increases( Almost Doubled) , since some reports required by business fired.
    We want to implement resource plan for that users.
    Suppose I create two Consumer group Full_MONTH and Month_end and create a plan.
    If I assign 80% CPU to full_month consumer and 20% to Month_end Consumer and forcing this plan to run as mentioned yesterday .
    So I want to understand if I implement above plan in the Resource Manager , What will be the impact on Other application and Server Processing.
    Since I forcing to Give 100% CPU to my resource manager plan.
    Thanks and Regards
    Sourabh Gupta

  • Oracle 10g database as Resource manager and heuristic transaction decision

    Hi,
    I have read in documents about distributed tarnsaction that resource manager like oracle databasecthat are involved in distributed transaction can take heuristic decision(unilateral decision) and can either rollback or commit the transaction associated with itself without having confirmation from the transaction manager.
    I want to know how a resource manager take this unilateral decision and can we set this as parameter either in resource manager or in application server.
    Thanks in advance

    Hi,
    Following are some links to documents.
    Handling Heuristic Completions
    http://edocs.bea.com/wls/docs81/ConsoleHelp/jta.html
    A heuristic completion (or heuristic decision) occurs when a resource makes a unilateral decision during the completion stage of a distributed transaction to commit or rollback updates. This can leave distributed data in an indeterminate state. Network failures or resource timeouts are possible causes for heuristic completion. In the event of an heuristic completion, one of the following heuristic outcome exceptions may be thrown:
    HeuristicRollback—one resource participating in a transaction decided to autonomously rollback its work, even though it agreed to prepare itself and wait for a commit decision. If the Transaction Manager decided to commit the transaction, the resource's heuristic rollback decision was incorrect, and might lead to an inconsistent outcome since other branches of the transaction were committed.
    HeuristicCommit—one resource participating in a transaction decided to autonomously commit its work, even though it agreed to prepare itself and wait for a commit decision. If the Transaction Manager decided to rollback the transaction, the resource's heuristic commit decision was incorrect, and might lead to an inconsistent outcome since other branches of the transaction were rolled back.
    HeuristicMixed—the Transaction Manager is aware that a transaction resulted in a mixed outcome, where some participating resources committed and some rolled back. The underlying cause was most likely heuristic rollback or heuristic commit decisions made by one or more of the participating resources.
    2. Understanding EJB Transaction
    http://www2.sys-con.com/itsg/virtualcd/Java/archives/0504/tyagi/index.html
    Unilateral Decisions
    The transaction manager allows certain heuristic or speculative decisions to be made based on the state of all participating resources in a transaction and the underlying two-phase commit protocol. A heuristic decision occurs when one of the resources in the transaction unilaterally decides to commit or roll back the transaction without permission from the transaction manager
    3. Oracle® Containers for J2EE
    http://download.oracle.com/docs/cd/B31017_01/web.1013/b28958.pdf
    Heuristics
    To achieve consensus, two-phase commit is a blocking protocol. This means that, if a coordinator fails before delivering the final phase messages, the participants must remain blocked, holding onto resources. Modern transaction systems add heuristics to two-phase commit, which allows such participants to make unilateral decisions about whether they will commit or rollback. If a participant makes a choice that turns out to be different from the one taken by other participants, then non-atomic behavior occurs.
    I got this problem while trying to do a distributed J2EE tarnsaction with two XA (one MQ and other Oracle 10g database XA) and one non-xa (oracle 10g database). According to above docs a resource manager can decide tarnsaction final state unilaterally and that can result in unatomic transaction.
    Do oracle also make such decision and if yes then on what ground it takes decision? Can we change this according to our requirement either always rollback/commit anywhere as parameter setting?
    Thanks

  • DATABASE RESOURCE MANAGER ( ORACLE 8I NEW FEATURE )

    제품 : ORACLE SERVER
    작성날짜 : 2004-08-16
    DATABASE RESOURCE MANAGER ( ORACLE 8I NEW FEATURE )
    ===================================================
    SCOPE
    8i~10g Standard Edition 에서는 Database Resource Manager 를 지원하지 않는다.
    Explanation
    Database Resource Manager란 OS에서 제공하는 자원 (예 : CPU 자원 )에 대해 DB
    차원에서 계획을 세워, 세부 관리를 할 수 있도록 해 주는 서비스이다.
    예를 들어 주간에 batch 작업을 처리하더라도, OLTP 업무에는 지장을 주지 않아야
    할 경우 batch 작업에 CPU 자원을 적게 할당해 주는 것이 바람직 하며, Resource
    Manager를 활용하여 CPU 자원을 batch 작업과 OLTP 업무에 서로 다르게 할당해 줄
    수 있다. ( Oracle 8.1.6 까지는 Resouurce Manager에서 CPU 자원에 대해서만
    관리만 가능하다 )
    1. 용어
    1) Resource Consumer Group
    사용자 session들의 집합. Resource에 대한 요구사항에 따라 나뉘어진 그룹.
    2) Resource Plan
         Consumer Group에 자원을 할당 해 주기 위한 resource plan directive들을
    포함.
    3) Resource Allocation Method
         Resource Manager에서 자원을 할당해 주는 방법/정책.
    4) Resource Plan Directive
         Resource Plan에 대해 자원을 할당해 주는 세부 내역.
    2. Resource Consumer Group
    * 기본 group
         [ 사용자가 삭제, 수정할 수 없는 group ]
         OTHER_GROUPS : active plan schema에 속하지 않는 consumer group의 모든
    session
         DEFAULT_CONSUMER_GROUP : consumer group을 지정하지 않은 모든
    session.(default)
         [ 기본적으로 제공되나 사용자가 삭제하거나 변경할 수 있는 group ]
         SYS_GROUP : SYSTEM_PLAN에 대한 high priority consumer group
    SYSTEM, SYS user에 할당한다.
         LOW_GROUP : SYSTEM_PLAN에 대한 low priority consumer group
    3. Resource Plan
         Consumer group에 속하는 session들은 해당 group에 대한 resource plan에
    따라 자원 할당이 결정되며, 자원 할당에 대한 세부 사항은 resource plan에
    대한 resource plan directive에서 지정된다.
         Resource plan은 subplan을 둘 수 있다.
    4. Resource Allocation Method
         Round-robin Method : Consumer group 내에서 session들에 대한 CPU 할당
         Emphasis Method : Consumer group에 할당되는 CPU
         Absolute Method : Parallel degree 한계 ( 예 : Parallel Query에서의
    degree )
    5. Resource Plan Directive
         Resource Plan Directive에 지정된 내용들은 resource plan에 따라
    consumer group에 자원을 할당할 때 반영된다.
    6. 구현 예제
         MYDB PLAN +-> MAILDB PLAN +-> POSTMAN GROUP (40% Level 1)
         | (30% Level 1) |
         | +-> USERS GROUP (80% Level 2)
         | |
         | +-> MAILMAINT GROUP (20% Level 2)
         | |
         | +-> OTHER GROUP (100% Level 3)
         |
         +-> BUGDB PLAN  +-> ONLINE GROUP (80% Level 1)
         (70% Level 1) |
         +-> BATCH GROUP (20% Level 1)
         |
         +-> BUGMAINT GROUP (100% Level 2)
         |
         +-> OTHER GROUP (100% Level 3)
         위 예에서 MYDB PLAN에는 2개의 subplan ( MAILDB PLAN, BUGDB PLAN )이
         있으며 각각 30%와 70%의 CPU 자원을 할당하였다.
         Level 1, Level 2, Level 3 는 우선순위 레벨을 의미하며, 하나의
         resource plan에서 동일한 level의 합이 100%를 넘지 못한다.
         ( Level 은 1부터 8까지 지정할 수 있으며 level 1이 가장 우선순위가
         높으며 level 8이 가장 우선순위가 낮다 )
         예를 들어 전체 CPU 자원의 70%를 할당 받은 BUGDB PLAN은 다시
         ONLINE GROUP과 BATCH GROUP을 두고 있는데, 이 둘의 Level이 모두 1이며
         두개의 percentage의 합이 100%이다. 하지만, 즉, level 1인 ONLINE GROUP
    에 90%를 할당하였다면, level 1인 BATCH GROUP에는 10% 이상을 할당할 수
    없다.
    Example
         * 구현을 위한 코드
         BEGIN
         /* PLAN schema 작업 영역 생성 */
         DBMS_RESOURCE_MANAGER.CREATE_PENDING_AREA();
         /* BUGDB PLAN, MAILDB PLAN, MYDB PLAN 생성 */
         DBMS_RESOURCE_MANAGER.CREATE_PLAN(PLAN => 'bugdb_plan',
         COMMENT => 'Resource plan/method for bug users sessions');
         DBMS_RESOURCE_MANAGER.CREATE_PLAN(PLAN => 'maildb_plan',
         COMMENT => 'Resource plan/method for mail users sessions');
         DBMS_RESOURCE_MANAGER.CREATE_PLAN(PLAN => 'mydb_plan',
         COMMENT => 'Resource plan/method for bug and mail users sessions');
         /* CONSUMER GROUP 생성 */
         DBMS_RESOURCE_MANAGER.CREATE_CONSUMER_GROUP(CONSUMER_GROUP =>
    'Bug_Online_group', COMMENT => 'Resource consumer group/method for
    online bug users sessions');
         DBMS_RESOURCE_MANAGER.CREATE_CONSUMER_GROUP(CONSUMER_GROUP =>
    'Bug_Batch_group', COMMENT => 'Resource consumer group/method for
    bug users sessions who run batch jobs');
         DBMS_RESOURCE_MANAGER.CREATE_CONSUMER_GROUP(CONSUMER_GROUP =>
    'Bug_Maintenance_group', COMMENT => 'Resource consumer group/method
    for users sessions who maintain the bug db');
         DBMS_RESOURCE_MANAGER.CREATE_CONSUMER_GROUP(CONSUMER_GROUP =>
    'Mail_users_group', COMMENT => 'Resource consumer group/method for
    mail users sessions');
         DBMS_RESOURCE_MANAGER.CREATE_CONSUMER_GROUP(CONSUMER_GROUP =>
    'Mail_Postman_group', COMMENT => 'Resource consumer group/method for
    mail postman');
         DBMS_RESOURCE_MANAGER.CREATE_CONSUMER_GROUP(CONSUMER_GROUP =>
    'Mail_Maintenance_group', COMMENT => 'Resource consumer group/method
    for users sessions who maintain the mail db');
         /* BUGDB PLAN에 대한 DIRECTIVE 생성 */     
         DBMS_RESOURCE_MANAGER.CREATE_PLAN_DIRECTIVE(PLAN => 'bugdb_plan',
    GROUP_OR_SUBPLAN => 'Bug_Online_group',     COMMENT => 'online bug users
    sessions at level 1', CPU_P1 => 80, CPU_P2=> 0,
         PARALLEL_DEGREE_LIMIT_P1 => 8);
         DBMS_RESOURCE_MANAGER.CREATE_PLAN_DIRECTIVE(PLAN => 'bugdb_plan',
    GROUP_OR_SUBPLAN => 'Bug_Batch_group',      COMMENT => 'batch bug users
    sessions at level 1', CPU_P1 => 20, CPU_P2 => 0,
         PARALLEL_DEGREE_LIMIT_P1 => 2);
         DBMS_RESOURCE_MANAGER.CREATE_PLAN_DIRECTIVE(PLAN => 'bugdb_plan',
    GROUP_OR_SUBPLAN => 'Bug_Maintenance_group',COMMENT => 'bug
    maintenance users sessions at level 2', CPU_P1 => 0, CPU_P2 => 100,
         PARALLEL_DEGREE_LIMIT_P1 => 3);
         DBMS_RESOURCE_MANAGER.CREATE_PLAN_DIRECTIVE(PLAN => 'bugdb_plan',
    GROUP_OR_SUBPLAN => 'OTHER_GROUPS', COMMENT => 'all other users
    sessions at level 3', CPU_P1 => 0, CPU_P2 => 0, CPU_P3 =>
         100);
    (참고) CPU_P1 : cpu allocation for level 1
         /* MAILDB PLAN에 대한 DIRECTIVE 생성 */
         DBMS_RESOURCE_MANAGER.CREATE_PLAN_DIRECTIVE(PLAN => 'maildb_plan',
    GROUP_OR_SUBPLAN => 'Mail_Postman_group',COMMENT => 'mail postman at
    level 1', CPU_P1 => 40, CPU_P2 => 0, PARALLEL_DEGREE_LIMIT_P1 => 4);
         DBMS_RESOURCE_MANAGER.CREATE_PLAN_DIRECTIVE(PLAN => 'maildb_plan',
    GROUP_OR_SUBPLAN => 'Mail_users_group',     COMMENT => 'mail users
    sessions at level 2', CPU_P1 => 0, CPU_P2 => 80,
         PARALLEL_DEGREE_LIMIT_P1 => 4);
         DBMS_RESOURCE_MANAGER.CREATE_PLAN_DIRECTIVE(PLAN => 'maildb_plan',
    GROUP_OR_SUBPLAN => 'Mail_Maintenance_group',COMMENT => 'mail
    maintenance users sessions at level 2', CPU_P1 => 0, CPU_P2 => 20,
         PARALLEL_DEGREE_LIMIT_P1 => 2);
         DBMS_RESOURCE_MANAGER.CREATE_PLAN_DIRECTIVE(PLAN => 'maildb_plan',
    GROUP_OR_SUBPLAN => 'OTHER_GROUPS', COMMENT => 'all other users
    sessions at level 3', CPU_P1 => 0, CPU_P2 => 0, CPU_P3 =>
         100);
         /* MYDB PLAN에 대한 DIRECTIVE 생성 */
         DBMS_RESOURCE_MANAGER.CREATE_PLAN_DIRECTIVE(PLAN => 'mydb_plan',
    GROUP_OR_SUBPLAN => 'maildb_plan', COMMENT=> 'all mail users
    sessions at level 1', CPU_P1 => 30);
         DBMS_RESOURCE_MANAGER.CREATE_PLAN_DIRECTIVE(PLAN => 'mydb_plan',
    GROUP_OR_SUBPLAN => 'bugdb_plan', COMMENT => 'all bug users sessions
    at level 1', CPU_P1 => 70);
         /* PLAN schema 작업 내용을 저장 */
         DBMS_RESOURCE_MANAGER.VALIDATE_PENDING_AREA();
         DBMS_RESOURCE_MANAGER.SUBMIT_PENDING_AREA();
         end;
    7. CONSUMER GROUP에 사용자나 세션을 할당하는 방법
         먼저 인스턴스에서 사용할 TOP Level resource plan 을 지정한다.
    initSID.ora에 RESOURCE_MANAGER_PLAN = MRDB_PLAN 지정이나 아래와 같이
    session level에 ALTER SYSTEM command를 사용하여 지정한다.
         ALTER SYSTEM SET RESOURCE_MANAGER_PLAN = MYDB_PLAN;
         그리고 SCOTT 계정에 BUG_ONLINE_GROUP과 BUB_BATCH_GROUP 에 속할 수 있는
    권한을 부여     
    DBMS_RESOURCE_MANAGER_PRIVS.GRANT_SWITCH_CONSUMER_GROUP ('SCOTT',
    'BUG_ONLINE_GROUP', TRUE);
         DBMS_RESOURCE_MANAGER_PRIVS.GRANT_SWITCH_CONSUMER_GROUP ('SCOTT',
    'BUG_BATCH_GROUP', TRUE);
         * DBMS_RESOURCE_MANAGER.SET_INITIAL_CONSUMER_GROUP( user in
    varchar2, consumer_group in varchar2);
         예)
         DBMS_RESOURCE_MANAGER.SET_INITIAL_CONSUMER_GROUP('SCOTT',
    'BUG_ONLINE_GROUP');
         SCOTT 계정을 BUG_BATCH_GROUP에 할당
         * DBMS_RESOURCE_MANAGER.SWITCH_CONSUMER_GROUP_FOR_SESS (
                             session_id IN NUMBER,
                             session_serial IN NUMBER,
                             consumer_group IN VARCHAR2);
         예)
         DBMS_RESOURCE_MANAGER.SWITCH_CONSUMER_GROUP_FOR_SESS( 11, 2,
    'BUG_ONLINE_GROUP');
         * DBMS_RESOURCE_MANAGER.SWITCH_CONSUMER_GROUP_FOR_USER (
                             user IN VARCHAR2,
                             consumer_group IN VARCHAR2);
         예)
         DBMS_RESOURCE_MANAGER.SWITCH_CONSUMER_GROUP_FOR_USER('SCOTT',
    'BUG_BATCH_GROUP');
    8. 관련된 Dictionary
    DBA_RSRC_PLANS : Resource plan과 status
    DBA_RSRC_PLAN_DIRECTIVES : Resource plan directives와 status
    DBA_RSRC_CONSUMER_GROUPS : Consumer group과 status
    DBA_RSRC_CONSUMER_GROUP_PRIVS : 사용자에게 부여된 Consumer group
    DBA_USERS : INITIAL_RSRC_CONSUMER_GROUP라는 새로운 column이 추가
    V$SESSION : RESOURCE_CONSUMER_GROUP라는 새로운 column이 추가
    V$RSRC_PLAN : 새로운 view로 active resource plan을 보여준다
    V$RSRC_CONSUMER_GROUP : 새로운 view로 consumer group의 active session
    을 보여준다.
    Reference Ducumment
    ---------------------

    user1 is the schema present in DB1
    user2 is the schema present in DB2. I just have a DB link
    as below:
    create database link link_to_DB2 connect to user2 identified by user2 using 'DB2';---Connects from user1 of DB1 to user2 of DB2.
    Requirement is as below:
    CPU for DB2 - 25%
    Out of above 25%, CPU for user2 - 70%
    CPU for user1 30% -- whenever it conncts using the link)
    Please help me out.

  • Oracle Access Manager-Protecting resources

    Hi,
    I have installed the Oracle Access Server/Identity Server/Policy managerWebpass/Webgate etc...I want to create policy domains and resources in the policy manager to protect certain internal websites. Is there any crisp documentation that some one can share to do the basics atleast? the oracle documentation is insanely extensive with links/references all over the place and I find it very difficult to understand how the policies are constructed. I have created couple of authentication schemes (basic/Form) that can be used. to start off i have a basic login page created in IIS that can be used for user input and also have a couple of other html files in a folder under it. If some one can share a document that takes me step by step to protecting a resource, it will be great.
    Thanks in advance.
    Naresh

    Two suggestions:
    1) Ask the question in a group inhabited by OAM users ... this group is generically for doc issues. (ANd yes, you mention a doc issue, but very few OAM users visit here.)
    - a place for that might be: http://forums.oracle.com and scroll down to Identify Management
    2) Look through OTN in the product portal (http://otn.oracle.com > Products: Middleware > Identify Management: Identity Management > Oracle Access Manager)

  • Oracle 9i resource manager

    Hello experts.
    I would like to know if assigning a particular CPU level to the group, will affect as well the DDL operations that are performed by users in this group
    (in my case it's dropping partitions, creating them, rebuilding indexes, make tablespaces read write, etc...). I can understand effect of resource manager on DML, but I doubt what's the way oracle controls ddl statements.
    Thanks in advance for your replies.
    Artyom.

    No. Oracle will use the assignd core/s cpu for the instance or DDL and DML both.

  • Does Oracle Database Resource Manager work at all?

    I have been testing Oracle Database Resource Management...
    Environment: OS IBM AIX 5L 64 bit core, DB Oracle8i 8.1.7.4 Enterprise Edition.
    To test, I followed the procedure in the Oracle Metalink Bulletin Note:106948., Oracle8i: Database Resource Manager samples.
    But I was not able to reproduce any succes. There seems to be no difference running with at plan and not running with af plan enabled.
    Does anydody know of a problem with the combination of Oracle and AIX, or any other problems that could explain why it doesn't work?
    /Jørn Hansen

    if the cpu is 100% loaded then you can see any affects..
    this is the way how oracle database resource manager works..
    Message was edited by:
    mkocaer

  • RH10: Snippets from resource manager show in search results

    I'm new to using the resource manager, so there's a good chance I've done something stupid here... but...
    I have 2 projects (I am the only tech writer, so running off one PC, no version control). I want to share snippets between the projects, so I'm using the resource manager to keep them synched up. Both are compiled as CHMs.
    When I search, I'm getting search results that appear to be the snippets in the results. When you double click them, they don't open.
    Here's a screenshot of what I'm seeing.
    Has anyone else seen this before? I'm using RH10.

    I have set up a test and cannot get snippets to show in search results.
    I am a little puzzled by the fact that you say they appear to be snippets, thus casting some doubt.
    Do you have snippets with those names and do the snippets contain the term being searched.
    Do you have topics with those names?
    Does it happen in a new project?
    Try creating a new SSL, not a duplicate.
    See www.grainge.org for RoboHelp and Authoring tips
    @petergrainge

  • Oracle Enterprise Manager 10gR4 is Released

    Here is the press release. Material is already posted on OTN. Enjoy!
    Oracle(R) Enterprise Manager Delivers Unique New Capabilities for Top-Down Application Management
    Tuesday November 13, 8:15 am ET
    New Capabilities Address Cross-Tier Performance Diagnostics, Integrated Incident and Problem Management and Application Data Sharing
    ORACLE OPENWORLD, SAN FRANCISCO, Nov. 13 /PRNewswire-FirstCall/ -- Building upon its "top-down" approach to managing application and Information Technology (IT) infrastructure resources, Oracle today announced key new enhancements to Oracle® Enterprise Manager 10g. The new enhancements deliver a broad range of capabilities, across the application lifecycle, for custom and SOA-based applications and pre-packaged applications and include faster performance diagnostics for production applications; simplified incident and problem management through integration with Oracle's Siebel CRM HelpDesk and PeopleSoft Enterprise HelpDesk applications; expanded capabilities to manage Oracle Business Intelligence; and easy and secure data sharing across the application lifecycle.
    Oracle's top-down approach to application management uniquely addresses the need for an end-to-end application perspective -- whether technology-focused or business-focused -- while enabling administrators to virtually eliminate the confusion caused by low-level system alerts that cannot be easily correlated to business exceptions. This has been a common and costly shortfall in traditional systems management software and frequently contributes to prolonged application downtime.
    "Helping customers drive better business results is the essence of Oracle's top-down approach to application management," said Richard Sarwal, senior vice president of Systems Management Products, Oracle. "With the addition of Connectors enabling closed-loop incident and problem tracking with Siebel CRM and PeopleSoft Enterprise HelpDesk applications and breakthrough application performance management capabilities using Oracle Enterprise Manager's Application Diagnostics for Java feature, Oracle takes another significant step in fulfilling our top-down application management strategy."
    "With this new release, Oracle is expanding both the breadth and depth of the application management capabilities available through Oracle Enterprise Manager, providing features designed for detailed diagnosis of Java application performance issues in production environments, with the ability to trace transactions between Java application servers and database sessions," according to Tim Grieser, Program Vice President, Enterprise System Management Software, IDC
    Taking Application Performance Management to the Next Level
    The new Oracle Application Diagnostics for Java capability in Oracle Enterprise Manager can monitor and diagnose performance problems in production Java applications with minimal impact on application performance and availability. Unlike most Java performance management tools that utilize bytecode instrumentation, Oracle Enterprise Manager's new feature has a highly innovative diagnostics engine that introduces less than one percent performance overhead on production applications and does not require IT operations to have a deep understanding of the application logic. The new feature also has a hot-pluggable architecture that enables the diagnostics engine to be deployed in heterogeneous middleware environments, without shutting down the application server. Oracle Application Diagnostics for Java is included in the Oracle Application Server Diagnostics Pack and the new Oracle Diagnostics Pack for Non-Oracle Middleware.
    Improving Performance Diagnostics Across Application Tiers
    Diagnosing end user performance problems has become increasingly difficult because of the increased deployment of multi-tiered web applications and the dynamic nature of web-based applications. With Oracle Application Diagnostics for Java, administrators now have powerful diagnostic capabilities by enabling application administrators to trace in-flight transactions and correlate user request activities in the Java application to corresponding activity in the database. Similarly, database administrators can quickly identify Java applications that may be causing resource contention in the database. This cross-tier diagnostics helps accelerate problem resolution by identification of resource bottlenecks across tiers.
    Tighter Integration for Siebel CRM Diagnostics and Oracle Enterprise Manager
    Siebel CRM diagnostic capabilities have been integrated with Oracle Enterprise Manager, providing a single integrated tool for problem diagnostics in Siebel CRM and its underlying infrastructure. Siebel CRM administrators can use Oracle Enterprise Manager for end-to-end management of Siebel CRM and to simplify Siebel CRM diagnostics based on user and server performance analysis. In addition, Siebel CRM customers can benefit from broader application support including Siebel CRM 8.0, 7.8 and 7.7.
    Enhancing Management Capabilities Across the Application Lifecycle
    New Management Connectors for Siebel CRM HelpDesk and Peoplesoft Enterprise HelpDesk applications allow the deployment of end-to-end IT incident and problem management solutions capable of unprecedented levels of automation and closed-loop remediation. The connectors enable Siebel CRM and PeopleSoft Enterprise HelpDesk customers to benefit from an integrated solution that spans the service lifecycle from incident logging and tracking to top-down management of applications including problem management, patching and provisioning across the technology stack. The bi-directional integration between Oracle Enterprise Manager and Siebel CRM and PeopleSoft Enterprise HelpDesk applications helps streamline key support processes by automatically creating service requests for incidents captured in Oracle Enterprise Manager. Support analysts using these help desk products are automatically empowered with respective corrective actions to accelerate problem resolution.
    Expanded Capabilities for Business Intelligence Management
    Oracle Management Pack for Business Intelligence is a new Oracle Enterprise Manager pack that extends the benefits of top-down application management to Oracle Business Intelligence Enterprise Edition Plus. Using the BI management pack, customers can receive proactive alerts on impending problems, troubleshoot and tune performance problems, manage configurations, proactively enforce configuration policies, and enforce service level agreements on Oracle Business Intelligence Enterprise Edition Plus deployments.
    Easy and Secure Data Sharing Across the Application Lifecycle
    Also new is the Oracle Data Masking Pack, to protect sensitive production data by using masking rules to replace confidential or sensitive production information with realistic but scrubbed data. This pack provides a scalable, secure solution for application data sharing for a wide variety of needs ranging from application development, testing, quality assurance as well as business processing. See related news release dated today.
    Availability and Pricing
    The enhancements listed above are generally available today with Oracle Enterprise Manager 10g Release 4.
    Oracle Application Server Diagnostics Pack and Oracle Diagnostics Pack for Non-Oracle Middleware are priced at $6,000 each per CPU. Management Connectors are priced at $5,000. The Oracle Management Pack for Business Intelligence is priced at $10,000 per CPU. The Oracle Data Masking Pack is priced at $10,000 per CPU of the server where data is being masked.
    For more information about Oracle Enterprise Manager 10g Release 4 and the family of Plug-ins, Connectors and Management Packs and to download free evaluation software go to: http://www.oracle.com/enterprisemanager/. Terms, conditions and restrictions apply.
    About Oracle Enterprise Manager 10g
    Spanning applications, middleware, and database management, Oracle Enterprise Manager 10g delivers integrated enterprise management for Oracle and non-Oracle systems to more than 21,000 Management Pack customers worldwide. Employing a unique "top-down" approach to managing application and IT infrastructure resources, Oracle Enterprise Manager allows customers to focus on what matters for its business -- greater agility, better service quality and lower operational costs. With a broad set of administration, configuration management, provisioning, end-to-end monitoring, service level management, and security capabilities, Oracle Enterprise Manager 10g helps customers manage service levels, proactively isolate business exceptions before they become emergencies, and remediate issues at any level spanning application and heterogeneous infrastructure -- all within one management solution. Learn more at http://www.oracle.com/enterprisemanager/.
    About Oracle
    Oracle (Nasdaq: ORCL - News) is the world's largest enterprise software company. For more information about Oracle, visit our Web site at http://www.oracle.com.
    Trademarks
    Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
    This announcement is provided to you solely for information purposes, is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. Many factors can materially affect Oracle's product development plans and the nature and timing of future product releases. The development, release, and timing of any features or functionality described remains at the sole discretion of Oracle. This information may not be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. Oracle specifically disclaims any liability with respect to this information.
    Message was edited by:
    Chung Wu

    This is expected behavious. It is because Enterprise Manager cannot run with the new server name. You can either go through loads to change the config files or simply drop and recreate the console.

  • How Transaction Manager work with Resource Manager, like Connection pool?

    hi,
    I'm using BEA Webloigc8.1 Stateless Session Bean/DAO/Oracle stored proc.
    but I'm not quite clear how Transaction Manager work with Resource Manager, like Connection pool.
    my understanding is that, in a weblogic transaction, a stateless session bean interact with several DAOs, and for each method of DAO a connection is acquired from connection pool. I've heard that the connection will not return to pool until the transaction commits.
    My question is that, does it mean that for a weblogic transaction, multiple connections might be allocated to it? and if multiple connections are allocated, then how many oracle transactions would be started? or multiple connections share the same oracle transaction?
    I didn't feel it make sense to start multiple oracle transactions, cause deadlock might be incurred in a single weblogic transaction.
    any help appreciated!

    Xin Zhuang wrote:
    hi,
    I'm using BEA Webloigc8.1 Stateless Session Bean/DAO/Oracle stored proc.
    but I'm not quite clear how Transaction Manager work with Resource Manager, like Connection pool.
    my understanding is that, in a weblogic transaction, a stateless session bean interact with several DAOs, and for each method of DAO a connection is acquired from connection pool. I've heard that the connection will not return to pool until the transaction commits.
    My question is that, does it mean that for a weblogic transaction, multiple connections might be allocated to it? and if multiple connections are allocated, then how many oracle transactions would be started? or multiple connections share the same oracle transaction?
    I didn't feel it make sense to start multiple oracle transactions, cause deadlock might be incurred in a single weblogic transaction.
    any help appreciated!Hi. If you configure your WLS DataSource to use keep a connection for
    the duration of a tx, it will do that, and in any case there can be
    no deadlock however many connections operate for a given XA transaction.
    Here is the best coding form for DAOs or any other user-written code
    for using WebLogic DataSources. This is important for two reasons:
    1 - Thread-safety is maintained as long as the connection is a
    method-level object.
    2 - It is crucial to notify WebLogic that you are done with a connection
    ASAP, by your calling close() on it. We will then put it back in the
    pool, or keep it under the covers for your next request if it's in a
    transaction etc. The pool is optimized for quick get-use-close scenarios.
    public void one_of_my_main_JDBC_Methods()
    Connection con=null; // Must be a method level object for thread-safety
    // It will be closed by the end of the method.
    try {
    con = myDataSource.getConnection(); // Get the connection in the try
    // block, directly from the WebLogic
    // datasource
    // do all the JDBC within this try block. You can pass the
    // connection to subordinate methods, but not to anywhere
    // that thinks it can use the connection later.
    rs.close(); // close any result set asap
    stmt.close(); // then close any statement asap
    // When you're done with JDBC
    con.close(); // close the connection asap
    con = null; // nullify it so the finally knows it's done
    catch (Exception e) {
    // do whatever catch stuff you want. You don't
    // need a catch block if you don't want one...
    finally {
    // It is important to close a JDBC connection ASAP when it's not needed.
    // without fail, and regardless of exit path. Do everything in your
    // finally block in it's own try-catch-ignore so everything is done.
    try { if (con != null) con.close();} catch (Exception ignore){}
    return ret;
    }

Maybe you are looking for

  • All the attachments both in SRM and R/3 must be saved in IXOS database

    Dear all, I am having the following requirements: We are creating Shopping Cart in SRM with attachments and these attachments are saving in the IXOS database. All these (same attachments) are relpicating to R/3 whenever system generates PR or PO auto

  • Which home hub gives the best wireless connection?

    Hello, I have the old home hub 1.0 (BT Total broadband option 3) and I am thinking about a wireless connection. Apparantly this home hub does have wireless ability but do the more recent hubs allow a better wireless connection? Thanks Adam

  • Gmail distribution list

    Is there a way to access my gmail distribution group when sending an email? For example, my Family Group in Gmail contacts, has all the family email addresses and I would like to just type in "family" when sending an email and having all the email ad

  • Apps purchased in another app store

    I changed my region of appstore to US once and the apps I bought before can't be seen in purchased list any more. Although they could be installed without charge and well notified, it's still difficult for me to remember if I've bought this app when

  • IMovie won't play in any of my default media players on my PC including Quicktime. Solutions?

    I wanted to upload this movie to youtube and I tried multiple times to do so from my iPod Touch. After many failed attempts I sent the movie to iTunes so that i could just upload the movie myself from my PC. But the movie will not play on any of my m