Help required in installing VM Server and Manager 3.1.1 + latest patch.

Hi,
I have 3 servers with 12GB ram and two 300 GB HDD (local) each, No Shared storage.
I am planning to install Oracle VM server 3.1.1 Build 544 and VM Manager 3.1.1 Build 524.
VM manager installed on Dom0 in one of the VM server (found some blog which describes how to implement it).
I have some questions running through my mind and help to solve it s really appreciated.
1) Is ORACLE VM SERVER PATCH 3.1.1-524 RELEASE is complete OS or its just patch which has to installed over 3.1.1 VM server. Because the patch readme says *"This patch update is a complete Oracle VM Server 3.1.1 installer ISO" ??*
2) I read somewhere in the forum that the 3.X version cannot use the disk where OS is installed as storage repository. in that case i will be loosing around 250 GB on each machine, on which i have installed VM server. Is it TRUE??
3) Is it possible to update VM server first and then update VM manager ( before creating server pool etc) ??
The servers are not connected to internet or SAN no i cannot use YUM or SAN update methods and I have very limited access to this servers physically.
Thanks in advance.

1. Its patch 544. Both can be downloaded and are complete installs. If you have YUM setup in an existing environment.... the VM servers can be upgraded via YUM. The VM Manager has to be upgraded via the installer.
2. Yes. This is true. Maybe your local RAID controller can present the storage as two separate LUNS/Disks even though they maybe setup as a mirror. If not, then you're out of luck. Virtual box can use local storage that OS is installed on. Oracle VM 3.1.1 can't.
3. Yes. You can install the 544 version of 3.1.1 on the servers before attaching them to the VM Manager. YUM should be used to upgrade the servers if they are already attached to a VM Manager. You would then upgrade the manager first and then upgrade the servers.

Similar Messages

  • Error installing sql server 2008 management studio express

    Hello,
    I need to install sql server 2008 management studio express on a sql server 2k8 R2 instance.
    First of all, I've downloaded this one from this link: http://www.microsoft.com/en-us/download/details.aspx?id=7593 (for 32 bits).
    Once I've the downloaded file I run this file and choose the first option (New sql server stand-alone...) in the installation part. Finally, in the installation type I choose the option 'Add features to an existing instance of SQL Server 2008' with the instance
    selected. I push Next and then I get the following error: 'The instance ID is required but it is missing'.
    Can anybody help me?
    Thanks a lot.
    Regards.

    Hello,
    What’s the edition of the SQL Server 2008 R2? If you had installed SQL Server 2008 R2 Developer edition, you should install “SQL Server 2008 Express with Tools” edition or “SQL Server 2008 Express with Advanced Services” edition.
    Please refer to the following article for more information:
    http://www.benlittler.com/2009/06/how-to-install-sql-management-studio-express-2008/
    Regards,
    Fanny Liu
    Fanny Liu
    TechNet Community Support

  • Different service packs in admin server and managed server

    Hi,
    Has anybody successfully used a WebLogic 6.1 SP1 managed server that
    connects to a WebLogic 6.1 SP 2 admin server?
    BEA's docs claim:
    "The Administration Server must be running the same version of
    WebLogic Server as the Managed Servers in its domain. The
    Administration Server must also have the same or later service pack
    installed as the Managed Servers in its domain. For example, the
    Administration Server could be running version 6.1, Service Pack 2
    while the Managed Servers are running version 6.1, Service Pack 1."
    This is precisely what we want to do, but it's not working. In this
    case, we need to run the admin server and managed server on the same
    machine, but we need the managed server to run SP 1 to work around a
    bug in SP 2. So to our initial installation of WebLogic 6.1 SP 2,
    where I run the admin server, I added a second installation, this time
    WebLogic 6.1 SP 1, with a different BEA_HOME. When I start the
    managed server from this second installation, I can see from the logs
    that it is starting up correctly as 6.1 SP 1. But then it fails with
    a ClassCastException when connecting to the admin server (I have
    included the stack trace below). This seems typical of version
    compatibility problems I've had when I've tried connecting to a server
    with a client of a different version.
    But in this case, you are supposed to be able to have the managed
    server with a lower service pack. Does this work for anybody? Has
    anybody encountered the problem I'm having? Note that the servers are
    not clustered, if that makes any difference, and we have a custom
    security realm in addition to the default file realm (though "system"
    of course is in the default file realm).
    Thanks in advance for any help,
    Jim Doyle
    [email protected]
    ####<Aug 8, 2002 10:25:38 AM EDT> <Emergency> <Server></server>
    <chile.iso-ne.com> <webui
    server> <main> <system> <> <000000> <Unable to initialize the server:
    'Fatal ini
    tialization exception
    Throwable: java.lang.ClassCastException:
    weblogic.security.acl.DefaultUserInfoImpl
    Start server side stack trace:
    java.lang.ClassCastException:
    weblogic.security.acl.DefaultUserInfoImpl
    at weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
    at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
    at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
    at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
    at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:164)
    at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
    at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
    at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
    at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    End server side stack trace

    Hi,
    Has anybody successfully used a WebLogic 6.1 SP1 managed server that
    connects to a WebLogic 6.1 SP 2 admin server?
    BEA's docs claim:
    "The Administration Server must be running the same version of
    WebLogic Server as the Managed Servers in its domain. The
    Administration Server must also have the same or later service pack
    installed as the Managed Servers in its domain. For example, the
    Administration Server could be running version 6.1, Service Pack 2
    while the Managed Servers are running version 6.1, Service Pack 1."
    This is precisely what we want to do, but it's not working. In this
    case, we need to run the admin server and managed server on the same
    machine, but we need the managed server to run SP 1 to work around a
    bug in SP 2. So to our initial installation of WebLogic 6.1 SP 2,
    where I run the admin server, I added a second installation, this time
    WebLogic 6.1 SP 1, with a different BEA_HOME. When I start the
    managed server from this second installation, I can see from the logs
    that it is starting up correctly as 6.1 SP 1. But then it fails with
    a ClassCastException when connecting to the admin server (I have
    included the stack trace below). This seems typical of version
    compatibility problems I've had when I've tried connecting to a server
    with a client of a different version.
    But in this case, you are supposed to be able to have the managed
    server with a lower service pack. Does this work for anybody? Has
    anybody encountered the problem I'm having? Note that the servers are
    not clustered, if that makes any difference, and we have a custom
    security realm in addition to the default file realm (though "system"
    of course is in the default file realm).
    Thanks in advance for any help,
    Jim Doyle
    [email protected]
    ####<Aug 8, 2002 10:25:38 AM EDT> <Emergency> <Server></server>
    <chile.iso-ne.com> <webui
    server> <main> <system> <> <000000> <Unable to initialize the server:
    'Fatal ini
    tialization exception
    Throwable: java.lang.ClassCastException:
    weblogic.security.acl.DefaultUserInfoImpl
    Start server side stack trace:
    java.lang.ClassCastException:
    weblogic.security.acl.DefaultUserInfoImpl
    at weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
    at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
    at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
    at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
    at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:164)
    at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
    at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
    at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
    at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    End server side stack trace

  • Error 25011. A file required to install the Rescue and Recovery environment could not be located

    Hello everybody,
    May I have your help and support on this error I faced with in installing the new Rescue and Recovery Version 4.5
    "Error 25011. A file required to install the Rescue and Recovery environment could not be located. This setup cannot proceed. Make sure that the correct .tv.t file is located in the same as this setup package and restart this setup."
    Awaiting,
    Thanks
    Hossein

    heya,
    I hope you managed to sort your issue out.
    It's namely mentioned here - http://www-307.ibm.com/pc/support/site.wss/MIGR-69170.html
    cheers
    norbs

  • Creating Weblogic domain with Admin Server and managed servers on different

    I am trying to create Weblogic domain where Admin Server and managed servers on different machines. However I am unable to find any steps which would allow me to do so. The config.sh script always creates an Admin Server. Please help.

    Whilst the method that Lawrence gives can result in a domain that is perfectly functional, it is a method that can result in errors as you are having to enter the same information twice. Also you will create two admin servers, as the second domain creation will have the console added to it on the renamed admin server and this will give issues.
    The best method to create a domain spamming multiple physical machines, is to create the domain with all the components on the first machine. This means planning the domain and making sure all components are added once; so having the information about the domain written out is wise. Ensure that the WLS software is installed in the same path on each machine before starting.
    Then copy the domain that you have created from one machine to the other, keeping the same paths. You can simply copy (I've used this method multiple times without issue) but the supported way would be to use the WLST PACK and UNPACK methods. These create and extract domains from templates. Some more information on these is given here -> http://docs.oracle.com/cd/E13179_01/common/docs100/pack/intro.html#wp1069056

  • Help require with installing Adobe Acrobat onto my Macbook Pro Retina.

    Help require with installing Adobe Acrobat onto my Macbook Pro Retina.
    I have successfully installed all of my creative cloud apps with the exception being acrobat.
    I cannot print from Indesign to PDF.
    I have unistalled, reinstalled and still no Adobe Acrobat.
    I now have to go back to Windows 8 and create the PDF's there.
    Any one know how to get around this issue?
    Thanks in advance
    Kelvin

    OSX has effectively killed the ability to print to pdf, (print to pdf eliminates most of the "Rich features" of current pdf).
    Export from InDesign, always, excpet for the 1% of the time where you know why print to pdf would produce a better result.

  • Communication protocol between Admin Server and Managed Server

    Hello - I am hoping someone can help me here to understand the communication protocols used in my setup.
    Here is my understanding of the protocol that are used between each component.
    End User <--->HTTPS<--->LoadBalancer Device<--->HTTPS<--->Web Server<---->HTTPS<--->WebLogic Server(Managed Server)<--->LDAP/JDBC<-->Data tier components
    AdminServer<--->T3<--->Managed Server i.e. The communication protocol between Admin Server and Managed server is T3
    The communication protocol between Managed Servers running in one cluster on two seperate machine is What?
    Thank you.

    Hello, interesting question.
    In the documentation " [cluster multicast communication|http://download.oracle.com/docs/cd/E13222_01/wls/docs90/cluster/features.html#1007001] " don't specify the used protocol to pack the information for example in a session replication.
    Although in a session replication all objects must be serializable i don't think rmi protocol is used.
    I hope some expert give us some light in this issue :-)
    http://download.oracle.com/docs/cd/E13222_01/wls/docs90/cluster/features.html#1007001

  • How to identify the installed Weblogic Server and JDK are 32bit or 64bit?

    Hi everyone,
    I have a question ~
    Both Weblogic Server and JAVA JDK are installed on the server already, but I only know the Weblogic Server is 10.3.4.0 and JAVA JDK version is 1.6.0_25.
    I know the 64bit Weblogic Server installation file is a wlsXXXX_generic.jar package and 64bit JAVA JDK needed also.
    But, since the Weblogic installed already, there are no such installation files on the Linux Server now.
    I have tried the "java -version" for java version and check the Weblogic version from Weblogic console.
    How to identify the installed Weblogic Server and JDK are 32bit or 64bit with Linux command? Or is there any way to check it?

    What you can try to do is use WLST (or an MBean browser, such as JConsole or JRockit Mission Control) and connect to the adminserver.
    For example when using WLST:
    # set the environment by using setWLSEnv.sh (located in the ${WL_HOME}/server/bin directory).
    # start WLST by using: java weblogic.WLST
    # connect to the adminserver
    connect('adminusername','adminpassword');
    # change to the serverruntime environment
    serverRuntime();
    # show the attributes
    ls();
    # Here an attribute is shown called WebLogicVersion that shows the version of WebLogic
    -r--   WeblogicVersion                              WebLogic Server 10.3.5.0  Fri Apr 1 20:20:06 PDT 2011 1398638
    # Note that this does not show if is 32 bits or 64 bits to retrieve this information you have obtain the JVM version
    # change the directory
    cd('JVMRuntime/AdminServer');
    # show the attributes
    ls();
    -r--   Version                                      R28.0.1-21-133393-1.6.0_20-20100512-2126-linux-x86_64
    # when you have something like x86 at the you are running a 32 bit version, if you have something like x86_64 you are running a 64 bits versionAs mentioned above you can also retrieve this information by using a MBean browser.

  • Problem creating a domain w/ one Admin Server and Managed Server

    I went through the config wizard (Weblogic 10.2) and set up a domain w/ 1 Admin Server and Managed Server. When I start the Admin server I get the following error:
    ####<Jul 30, 2008 6:05:28 PM PDT> <Error> <Store> <BLUDAF222452> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1217466328289> <BEA-280061> <The persistent store "pfProliferationJMSStore" could not be deployed: weblogic.store.PersistentStoreException: Can't find JDBC DataSource portalFrameworkPoolNeverXA: javax.naming.NameNotFoundException: Unable to resolve 'portalFrameworkPoolNeverXA'. Resolved ''; remaining name 'portalFrameworkPoolNeverXA'
    weblogic.store.PersistentStoreException: Can't find JDBC DataSource portalFrameworkPoolNeverXA: javax.naming.NameNotFoundException: Unable to resolve 'portalFrameworkPoolNeverXA'. Resolved ''; remaining name 'portalFrameworkPoolNeverXA'
         at weblogic.store.admin.JDBCAdminHandler.createDataSource(JDBCAdminHandler.java:105)
         at weblogic.store.admin.JDBCAdminHandler.makeStoreIO(JDBCAdminHandler.java:184)
         at weblogic.store.admin.JDBCAdminHandler.makeStore(JDBCAdminHandler.java:162)
         at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:57)
         at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
         at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
         at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
         at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
         at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
         at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    javax.naming.NameNotFoundException: Unable to resolve 'portalFrameworkPoolNeverXA'. Resolved ''; remaining name 'portalFrameworkPoolNeverXA'
         at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1138)
         at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:251)
         at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:171)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:205)
         at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
         at javax.naming.InitialContext.lookup(InitialContext.java:351)
         at weblogic.store.admin.JDBCAdminHandler.createDataSource(JDBCAdminHandler.java:100)
         at weblogic.store.admin.JDBCAdminHandler.makeStoreIO(JDBCAdminHandler.java:184)
         at weblogic.store.admin.JDBCAdminHandler.makeStore(JDBCAdminHandler.java:162)
         at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:57)
         at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
         at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
         at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
         at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
         at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
         at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    >
    ####<Jul 30, 2008 6:05:28 PM PDT> <Warning> <Management> <BLUDAF222452> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1217466328289> <BEA-141197> <The deployment of pfProliferationJMSStore failed.
    weblogic.management.DeploymentException:
         at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:60)
         at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
         at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
         at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
         at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
         at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
         at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    javax.naming.NameNotFoundException: Unable to resolve 'portalFrameworkPoolNeverXA'. Resolved ''; remaining name 'portalFrameworkPoolNeverXA'
         at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1138)
         at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:251)
         at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:171)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:205)
         at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
         at javax.naming.InitialContext.lookup(InitialContext.java:351)
         at weblogic.store.admin.JDBCAdminHandler.createDataSource(JDBCAdminHandler.java:100)
         at weblogic.store.admin.JDBCAdminHandler.makeStoreIO(JDBCAdminHandler.java:184)
         at weblogic.store.admin.JDBCAdminHandler.makeStore(JDBCAdminHandler.java:162)
         at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:57)
         at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
         at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
         at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
         at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
         at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
         at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    >
    ####<Jul 30, 2008 6:05:28 PM PDT> <Error> <JMS> <BLUDAF222452> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1217466328368> <BEA-040123> <Failed to start JMS Server "pfJMSServer" due to weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist.
    weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist
         at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:296)
         at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:184)
         at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
         at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
         at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
         at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
         at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
         at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    >
    ####<Jul 30, 2008 6:05:28 PM PDT> <Warning> <Management> <BLUDAF222452> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1217466328368> <BEA-141197> <The deployment of pfJMSServer failed.
    weblogic.management.DeploymentException: Internalrror activating the JMS Server pfJMSServer: weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist
         at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:198)
         at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
         at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
         at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
         at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
         at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
         at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist
         at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:296)
         at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:184)
         at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
         at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
         at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
         at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
         at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
         at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    >
    ####<Jul 30, 2008 6:05:28 PM PDT> <Error> <Deployer> <BLUDAF222452> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1217466328461> <BEA-149231> <Unable to set the activation state to true for the application 'pf-proliferation-jms'.
    weblogic.application.ModuleException: ERROR: Could not activate pf-proliferation-jms!pfProliferationQueue
         at weblogic.jms.backend.BEDestinationRuntimeDelegate.activate(BEDestinationRuntimeDelegate.java:238)
         at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1717)
         at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1667)
         at weblogic.jms.module.JMSModule$EntityState.access$100(JMSModule.java:1608)
         at weblogic.jms.module.JMSModule.activate(JMSModule.java:332)
         at weblogic.jms.module.ModuleCoordinator.activate(ModuleCoordinator.java:182)
         at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:63)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:182)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:359)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:42)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    weblogic.messaging.kernel.KernelException: The Messaging Kernel pfJMSServer has not yet been opened
         at weblogic.messaging.kernel.internal.KernelImpl.checkOpened(KernelImpl.java:191)
         at weblogic.messaging.kernel.internal.DestinationImpl.activate(DestinationImpl.java:279)
         at weblogic.messaging.kernel.internal.QueueImpl.activate(QueueImpl.java:1633)
         at weblogic.messaging.kernel.internal.DestinationImpl.resume(DestinationImpl.java:263)
         at weblogic.messaging.kernel.internal.QueueImpl.resume(QueueImpl.java:1809)
         at weblogic.jms.backend.BEDestinationImpl.start(BEDestinationImpl.java:609)
         at weblogic.jms.backend.BEDestinationRuntimeDelegate.activate(BEDestinationRuntimeDelegate.java:235)
         at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1717)
         at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1667)
         at weblogic.jms.module.JMSModule$EntityState.access$100(JMSModule.java:1608)
         at weblogic.jms.module.JMSModule.activate(JMSModule.java:332)
         at weblogic.jms.module.ModuleCoordinator.activate(ModuleCoordinator.java:182)
         at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:63)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:182)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:359)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:42)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    >

    I am using the default db the installation uses which is PointBase. I am not using any specific db, JDBC Datasource/Connection pool Configuration.
    Just to try something different, I tried creating a domain w/ one Admin and Managed Server which uses a Cluster and I did not get any errors. From what I read, a cluster is not necessary but not sure why it works without errors w/ a cluster.
    I will try commenting out the datasource from the config and see what happens and will let you know.

  • Gateway server and Management server in SCOM 2012

    What are the main Different between Gateway server and Management server in SCOM 2012?
    I have referred this , is there anything ?
    http://blogs.technet.com/b/momteam/archive/2008/02/19/10-reasons-to-use-a-gateway-server.aspx

    1) Management server can write data , gathered from agent, directly into operations manager database. Gateway server should forward data, collected from managed agent to management server.
    2) In a unturst environment for example workgroup or untrust domain, and you do not want to deploy a certificate to every monitored agent, you should deploy gateway server rather than managment server.
    Roger

  • Installing Grid Control and managing DBs on desktop

    I want to install Grid Control, and manage DB on my own testing environment on desktops...I tried one time to install Grid Control on my desktop i become very slow. Now i am thinking to buy new Desktop dedicated for Grid Control only and see how it goes...any suggestions?
    2nd how i can access my DB on the other desktop? Like i should install agents on that...and how to configure....

    When teaching this class I typically have 6 pairs of students sharing a single P4 3Ghz with 4Gb of RAM gridserver. (combined 10.1.0.4 emrep with single OMS on RH 3 AS)
    THis is more than enough for the 150 or so targets that we configure during class
    The agents are deployed in any of several methods.(the install DVD is probabally the easiest for 1's and 2's) If you are monitoring a db expect to use about 150Mb of RAM for the agent. After setting up the agent ensure that your computer has local security policy configured so that "Login as Batch" is enabled for the user account that will be used for authentication to the desktop. (this also means that you need to have a windows password configured for that account as well).
    The database configuration is semi-automatic once you have the agent installed on the desktop (it's called discovery)

  • Move SCOM agent between gateway server and management server ?

    Dear all,
    IN SCOM 2012 R2 is it possible to move SCOM agent between gateway server and management server ? I mean if one agent is reporting to Gateway server , in case if i want to shutdown that Gateway server , can i move to another Management server and
    Vice versa ?
    Thanks,
    Sengo

    Hi,
    http://blogs.catapultsystems.com/cfuller/archive/2012/06/05/how-does-the-failover-process-work-in-opsmgr-2012-scom-sysctr.aspx
    and links at the bottom of
    the article

  • OVM server : Change IP of server and manager

    Hi,
    does anyone know where I can find a metalink note to change the IP addresses of OVM server and manager ?
    Thanks in advance

    user11969500 wrote:
    does anyone know where I can find a metalink note to change the IP addresses of OVM server and manager ?Changing the IP address of an Oracle VM Server is pretty simple: remove it from Oracle VM Manager, change the IP address and then add it back.
    Changing the IP address of the Oracle VM Manager is even easier: just change it's IP address. :) All communication between VM Manager and the pool is initialized by the Manager itself. The pool doesn't know (or care) what that IP address of the Manager is. Remember to change the /etc/hosts file though, otherwise you may have issues with Oracle XE and oc4j not starting correctly.

  • I installed Lion Server and when I click on the Profile Manager I get an error and nothing shows - I can't figure out how to re install Lion Server to fix this - any ideas

    I installed Lion Server on my Mac Pro.  Everything looked to be working until I checked Profile Manager and I get an error message "Error Reading Settings"  Not sure how to fix it.  Tried to download Server agian but can't.

    Look at /usr/lib/libpq library. I have had the same problem. There were following files:
    -rwxr-xr-x  1 root  wheel  163680 30 jul 21:17 /usr/lib/libpq.5.4.dylib
    lrwxr-xr-x  1 root  wheel      15 30 jul 21:20 /usr/lib/libpq.dylib -> libpq.5.4.dylib
    Result for command sudo /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/wipeDB .sh was:
    Password:
    devicemgr:state = "STOPPED"
    postgres:state = "RUNNING"
    (in /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend)
    Couldn't drop device_management : #<RuntimeError: Please install the postgresql adapter: `gem install activerecord-postgresql-adapter` (dlopen(/Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backen d/vendor/gems/pg-0.9.0/lib/pg_ext.bundle, 9): Library not loaded: /usr/lib/libpq.5.dylib
      Referenced from: /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /gems/pg-0.9.0/lib/pg_ext.bundle
      Reason: image not found - /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /gems/pg-0.9.0/lib/pg_ext.bundle)>
    (in /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend)
    Please install the postgresql adapter: `gem install activerecord-postgresql-adapter` (dlopen(/Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backen d/vendor/gems/pg-0.9.0/lib/pg_ext.bundle, 9): Library not loaded: /usr/lib/libpq.5.dylib
      Referenced from: /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /gems/pg-0.9.0/lib/pg_ext.bundle
      Reason: image not found - /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /gems/pg-0.9.0/lib/pg_ext.bundle)
    /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor/ rails/activerecord/lib/active_record/connection_adapters/abstract/connection_spe cification.rb:76:in `establish_connection'
    /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor/ rails/railties/lib/tasks/databases.rake:69:in `create_database'
    /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor/ rails/railties/lib/tasks/databases.rake:31
    /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rake.rb: 636:in `call'
    /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rake.rb: 636:in `execute'
    /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rake.rb: 631:in `each'
    /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rake.rb: 631:in `execute'
    /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rake.rb: 597:in `invoke_with_call_chain'
    /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/monitor. rb:242:in `synchronize'
    /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rake.rb: 590:in `invoke_with_call_chain'
    /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rake.rb: 583:in `invoke'
    /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rake.rb: 2051:in `invoke_task'
    /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rake.rb: 2029:in `top_level'
    /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rake.rb: 2029:in `each'
    /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rake.rb: 2029:in `top_level'
    /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rake.rb: 2068:in `standard_exception_handling'
    /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rake.rb: 2023:in `top_level'
    /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rake.rb: 2001:in `run'
    /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rake.rb: 2068:in `standard_exception_handling'
    /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rake.rb: 1998:in `run'
    /usr/bin/rake:31
    Couldn't create database for {"adapter"=>"postgresql", "username"=>"_devicemgr", "encoding"=>"UTF8", "pool"=>5, "database"=>"device_management"}
    devicemgr:state = "STARTING"
    There was missing symlink to right version of libpq dynamic library!
    After I entered the following commands and now it works well for me:
    $ cd /usr/lib
    $ sudo ln -s libpq.5.4.dylib libpq.5.dylib
    $ sudo /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/wipeDB .sh
    devicemgr:state = "STOPPED"
    postgres:state = "RUNNING"
    (in /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend)
    (in /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend)
    devicemgr:state = "RUNNING"
    Milan

  • Silent Install w/Admin and Managed Servers

    I noticed on versions 11 and 12 of Weblogic, it seems the parameters available for a silent install have been greatly simplified to where it just does a base install.  How would I go about getting it to do a silent install with an Admin server and 2 Managed servers?  Do I need to do an install and update-install or is there a way I can do all this in 1 shot?
    Thanks In Advance
    Nic

    An example is given here: Middleware Snippets: Automate WebLogic 12.1.2 Deployment.

Maybe you are looking for