Server Migration/ Node Failure

Hi,
          I am using 9.2 clustering with 2 nodes, 1 Admin node setup. Each node has two managed servers on it. I am using distributed queue across all the managed servers.
          I am persisting JMS messages data into Oracle 10g for high availabilty.
          The server can be migrated with two ways.
          1. On same node it will restart managed server
          2. On different node it will migrate the entire server.
          I am not able to do option 2. i.e.
          I am sending messages on node 1 and 2. I removed the power chord from node 1 which is configured to migrate to node 2. But managed servers on node 1 are not migrated, they continuously go in a loop of restarting on node 2. It gives following error message.
          Unable to create a server socket for listening on channel "Default". The address <Node 1 IP> might be incorrect or another process is using port 9011: java.net.BindException: Cannot assign requested address.>
          Has anyone came across this error? Am I missing anything?
          Pls. Help.
          Also are there any optimum figures in number of seconds available for migration, i.e. Sever will be migrated within <x> seconds.
          Thanks,
          Alan

Similar Messages

10.3 Whole Server Migration

Hi,
I need some enlightenments from all. Here is my setup (in Windows 2003 R2)
2 physical Server, PS A, PS B (PS: physical server)
PS A contains, 1 Admin Server, 1 Managed server
PS B contains, 1 Managed Server
I've done the necessary clustering setup and tested its working, using node manager (nmenroll, conseus, etc). now what I'm trying to perform is to try out whole sever migration.
I've found out the script, wlsifconfig.cmd (found under %wls_home%\user_projects\domains\abc\bin\server_migration\, contains some linux command such as grep and rm. Workaround installed grep command for windows and replace rm with del.
I've shut down all managed servers and configure the managed servers to be whole server migration ready, set the node manager properties etc. I start the managed server 1 in PS A, PS A contains the floating IP upon starting. I checked using ipconfig, the floating IP is added. Then I tried to start managed server 2 through the admin console in PS A. Here comes the problem, managed server 2 also add in the floating IP which resulted in windows IP conflict. I'm not sure what went wrong, as of now i suspect is the wlsifconfig.cmd is the root of the problem. Therefore writing in to ask help from all. (Could it be im using 10.3 which does not support whole server migration?)
Best Regards

This appears to be working on Windows using 10.0.3 Server. For the lack of step-by-step tutorial, my best suggestion is to read Node Manager Administrator's Guide chapter 1,2,3,4,6 and "Using Clusters" chapter 7. I ran into many error messages and had to apply several hacks from google results.
The whole server migration design does not appear to be too useful though.
I have the whole server migration configured on two hosts.
1. Machine A has AdminServer and M1 (runs a pinned application and happens to be assigned a cluster master)
2. Machine B has node manager and M2.
3. M1 is set up to be migratable to A and B
I shutdown Machine A, but nothing is migrated. From the document, it seems both cluster master and AdminServer need to be running in order for migration to happen. This is still a single point of failure.

BAM Cluster setup - issue with whole server migration configuration

HI,
We are working on a SOA , BAM , BPM Cluster setup on OEL VMs
With Admin server running on Host1 and Soa_server1, BAM_server1 , Host2 - Soa_server2 , Bam_server2.
We were successfully able to setup clustering for Soa without using the webTier utilities in our environment, Just by adding entries in the /etc/hosts file.
Followed the document - except for web tier setup
http://www.namredlek.nl/orasoa/InstallSOASuite11gOnCluster_v1.pdf
1)     Installed Weblogic 11g.
2)     Soa 11g.
3)     Domain creation
4) Configured Node manager
5) Soa Clustering completed successfully.
6) Domain up and running with SOA_Cluster up and running.
7)     Extended the domain with BAM
The issue revolves when we are doing teh Migration configurations from the console for BAM and we restart BAM server we get an error -
Apr 14, 2011 2:30:35 AM weblogic.nodemanager.server.Handler handleStart
WARNING: Exception while starting server 'bam_server1'
java.io.IOException: Command '/oracle/Shared_MWHome/user_projects/domains/SOA_Domain/bin/server_migration/wlsifconfig.sh -addif eth0 192.168.1.6 255.255.255.0 ' returned an unsuccessful exit code '1'. Check NM logs for script output.
and Bam server goes to Failed Not Restartable state.

The error is clearly out there
java.io.IOException: Command '/oracle/Shared_MWHome/user_projects/domains/SOA_Domain/bin/server_migration/wlsifconfig.sh -addif eth0 192.168.1.6 255.255.255.0 ' returned an unsuccessful exit code '1'. Check NM logs for script output.
This error occurs due to a failure in adding the virtual IP of BAM server to the network interface you have specified in nodemanager.properties.
You need to check whether you have specified the correct interface and subnet mask in node manager.properties as below :
The fourth step is to edit the Node Manager's properties file. This file is called nodemanager.properties
and is located in the ORACLE_BASE/product/osbmw/wlserver_10.3/common/nodemanager directory.
For server migration to work properly, you need to add the properties listed below:
Interface=eth0
NetMask=255.255.255.0
UseMACBroadcast=true
· Interface
This property specifies the interface name for the floating IP (for example, eth0).
· NetMask
This property specifies the net mask for the interface for the floating IP. The net mask should the
same as the net mask on the interface; 255.255.255.0 is used as an example in this document.
· UseMACBroadcast
This property specifies whether or not to use a node's MAC address when sending ARP packets,
that is, whether or not to use the -b flag in the arping command.

Whole Server Migration working on Windows?

Does anyone have experience successfully configure whole server migration on windows? Is it possible to get some step by step guide?

This appears to be working on Windows using 10.0.3 Server. For the lack of step-by-step tutorial, my best suggestion is to read Node Manager Administrator's Guide chapter 1,2,3,4,6 and "Using Clusters" chapter 7. I ran into many error messages and had to apply several hacks from google results.
The whole server migration design does not appear to be too useful though.
I have the whole server migration configured on two hosts.
1. Machine A has AdminServer and M1 (runs a pinned application and happens to be assigned a cluster master)
2. Machine B has node manager and M2.
3. M1 is set up to be migratable to A and B
I shutdown Machine A, but nothing is migrated. From the document, it seems both cluster master and AdminServer need to be running in order for migration to happen. This is still a single point of failure.

Starting managed server using node manager

When i try to start the managed server using node manager i get the following error
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
Abort - core dumped
<Sep 21, 2010 3:58:07 PM> <FINEST> <NodeManager> <Waiting for the process to die: 22708>
<Sep 21, 2010 3:58:07 PM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
<Sep 21, 2010 3:58:07 PM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
The managed server lok file is deleted, port is not in use. With similar node manager settings the managed server on the redundant server starts fine

Hi,
I am getting same issue. Not able to start the soa_server1. Can you pleae tell me the soulution if you able to reslove the issue.
starting weblogic with Java version:
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
[ERROR] aborted
JRockit aborted: Unknown error (50)
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
Starting WLS with line:
D:\Oracle\MIDDLE~1\JROCKI~1.0-6\bin\java -jrockit -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms512m -Xmx512m -Dweblogic.Name=soa_server1 -Djava.security.policy=D:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Dweblogic.system.BootIdentityFile=D:\Oracle\Middleware\user_projects\domains\domain2\servers\soa_server1\data\nodemanager\boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xverify:none -da:org.apache.xmlbeans... -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole... -Dplatform.home=D:\Oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=D:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=D:\Oracle\MIDDLE~1\WLSERV~1.3\server -Ddomain.home=D:\Oracle\MIDDLE~1\USER_P~1\domains\domain2 -Dcommon.components.home=D:\Oracle\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Djrockit.optfile=D:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.domain.config.dir=D:\Oracle\MIDDLE~1\USER_P~1\domains\domain2\config\FMWCON~1 -Doracle.server.config.dir=D:\Oracle\MIDDLE~1\USER_P~1\domains\domain2\config\FMWCON~1\servers\soa_server1 -Doracle.security.jps.config=D:\Oracle\MIDDLE~1\USER_P~1\domains\domain2\config\fmwconfig\jps-config.xml -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Digf.arisidbeans.carmlloc=D:\Oracle\MIDDLE~1\USER_P~1\domains\domain2\config\FMWCON~1\carml -Digf.arisidstack.home=D:\Oracle\MIDDLE~1\USER_P~1\domains\domain2\config\FMWCON~1\arisidprovider -Dweblogic.alternateTypesDirectory=D:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,D:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Dweblogic.jdbc.remoteEnabled=false -Doracle.security.jps.policy.migration.validate.principal=false -da:org.apache.xmlbeans... -Dsoa.archives.dir=D:\Oracle\Middleware\Oracle_SOA1\soa -Dsoa.oracle.home=D:\Oracle\Middleware\Oracle_SOA1 -Dsoa.instance.home=D:\Oracle\MIDDLE~1\USER_P~1\domains\domain2 -Dtangosol.coherence.clusteraddress=227.7.7.9 -Dtangosol.coherence.clusterport=9778 -Dtangosol.coherence.log=jdk -Djavax.xml.soap.MessageFactory=oracle.j2ee.ws.saaj.soap.MessageFactoryImpl -Djava.protocol.handler.pkgs="oracle.mds.net.protocol|oracle.fabric.common.classloaderurl.handler|oracle.fabric.common.uddiurl.handler|oracle.bpm.io.fs.protocol" -Dweblogic.transaction.blocking.commit=true -Dweblogic.transaction.blocking.rollback=true -Djavax.net.ssl.trustStore=D:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\DemoTrust.jks -Dem.oracle.home=D:\Oracle\Middleware\oracle_common -Djava.awt.headless=true -Dbam.oracle.home=D:\Oracle\Middleware\Oracle_SOA1 -Dums.oracle.home=D:\Oracle\Middleware\Oracle_SOA1 -Dweblogic.management.discover=false -Dweblogic.management.server=http://192.168.1.102:7001 -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=D:\Oracle\MIDDLE~1\patch_wls1033\profiles\default\sysext_manifest_classpath;D:\Oracle\MIDDLE~1\patch_oepe1033\profiles\default\sysext_manifest_classpath;D:\Oracle\MIDDLE~1\patch_ocp353\profiles\default\sysext_manifest_classpath weblogic.Server
[WARN ] Use of -Djrockit.optfile is deprecated and discouraged.
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
[ERROR] aborted
JRockit aborted: Unknown error (50)
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
<Oct 4, 2010 6:25:39 AM> <FINEST> <NodeManager> <Waiting for the process to die: 700>
<Oct 4, 2010 6:25:39 AM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
<Oct 4, 2010 6:25:39 AM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>

Unable to start SOA server through Node Manager

Hi All,
I am trying to install AIA 11.1.1.6.0 on the top of SOA Suite 11.1.1.6.0.
I was able to install successfully the weblogic server, rcu, soa and osb servers. Now, before installing the AIA, the document i am following it says, make sure to start the soa server through the node manager.
Now i start the admin server, then the node manager, to make sure i have checked that the node manager is up, i logged in to the weblogic console, went to Machines, and i can see that it is up and reachable.
Now using the WLST commands, first i connected to the node manager using command nmConnect(), then i am trying to start the soa server through node manager using the command start('soa_server1') command.
I am getting an error while trying to start soa server with nmStart() command, below is the error message...
"Error starting server soa_server1: weblogic.nodemanager.NMException: Exception while starting server 'soa_server1'"
I executed the dumpStack() command, and i am getting the output as "No stack trace available"
If i am able to start the soa server through the node manager, i can go ahead and install the AIA pack but this is not letting me go forward.
I also tried to start the soa server through the weblogic console., go to servers tab, select the soa_server1 and start, the soa server state is going to "FAILED_NOT_RESTARTABLE".
I followed some of the blogs like...
http://neeraj-soa-tips.blogspot.com/2010/06/starting-admin-and-managed-servers.html
http://www.javamonamour.org/2011/09/nmconnect-nmstart-nmkill.html
Experts, please give your advice.
Many Thanks,
N

Hi Narsing,
I'm assuming that you've followed the required Pre-config steps. If it is not working, I'd suggest to start the Admin and SOA server without node manager first. Then start your node manager and see if it is reachable from the WLS console. Then shut down your SOA server from command prompt and restart your SOA server from WLS console.
Verify the Listen Address of your Node Manager and start your node manager from command prompt by explicitly specifying the same address and port.
As WLS console internally uses node manager only to start your server, you would not need to use WLST scripts to do the same and only SOA server needs to be started using node manager.
Regards,
Neeraj Sehgal
Hi Neeraj,
I made sure that in the weblogic console, in the machines tab, local machine-->configuration--->Node Manager, I have given the correct Listen Address (Narsing-PC) and the listen port 5556.
I have made sure the property StartScriptEnabled= true.
I have started the admin server through startWebLogic.cmd command, now i start the node manager by going to the C:\Oracle\Middleware\wlserver_10.3\server\bin and running the command startNodeManager.cmd, then i go to the weblogic console--->servers--->control--->soa_server1--->start , it is going to      FAILED_NOT_RESTARTABLE status.
If i see the log messages in the nodemanager.log, this is the below message...
<Jun 28, 2012 11:25:09 PM> <INFO> <soa_domain> <soa_server1> <Server output log file is 'C:\Oracle\Middleware\user_projects\domains\soa_domain\servers\soa_server1\logs\soa_server1.out'>
<Jun 28, 2012 11:25:11 PM> <INFO> <soa_domain> <soa_server1> <Server failed during startup so will not be restarted>
<Jun 28, 2012 11:25:11 PM> <WARNING> <Exception while starting server 'soa_server1'>
java.io.IOException: Server failed to start up. See server output log for more details.
     at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServerManager.java:196)
     at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23)
     at weblogic.nodemanager.server.Handler.handleStart(Handler.java:609)
     at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:121)
     at weblogic.nodemanager.server.Handler.run(Handler.java:71)
     at java.lang.Thread.run(Thread.java:662)
The log message in the soa_server1.out file is as below...
Starting WLS with line:
C:\Oracle\MIDDLE~1\JDK160~1\bin\java -client -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms512m -Xmx1024m -XX:PermSize=128m -XX:MaxPermSize=512m -Dweblogic.Name=soa_server1 -Djava.security.policy=C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Dweblogic.system.BootIdentityFile=C:\Oracle\Middleware\user_projects\domains\soa_domain\servers\soa_server1\data\nodemanager\boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xverify:none -da:org.apache.xmlbeans... -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole... -Dplatform.home=C:\Oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dcommon.components.home=C:\Oracle\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1 -Djrockit.optfile=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config.dir=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1\servers\soa_server1 -Doracle.domain.config.dir=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1 -Digf.arisidbeans.carmlloc=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1\carml -Digf.arisidstack.home=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1\arisidprovider -Doracle.security.jps.config=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\servers\soa_server1\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol"|"oracle.fabric.common.classloaderurl.handler"|"oracle.fabric.common.uddiurl.handler"|"oracle.bpm.io.fs.protocol -Dweblogic.jdbc.remoteEnabled=false -Doracle.security.jps.policy.migration.validate.principal=false -da:org.apache.xmlbeans... -Dbpm.enabled=true -Dsoa.archives.dir=C:\Oracle\Middleware\Oracle_SOA1\soa -Dsoa.oracle.home=C:\Oracle\Middleware\Oracle_SOA1 -Dsoa.instance.home=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1 -Dtangosol.coherence.clusteraddress=227.7.7.9 -Dtangosol.coherence.clusterport=9778 -Dtangosol.coherence.log=jdk -Djavax.xml.soap.MessageFactory=oracle.j2ee.ws.saaj.soap.MessageFactoryImpl -Dweblogic.transaction.blocking.commit=true -Dweblogic.transaction.blocking.rollback=true -Djavax.net.ssl.trustStore=C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\DemoTrust.jks -Dem.oracle.home=C:\Oracle\Middleware\oracle_common -Djava.awt.headless=true -Dbam.oracle.home=C:\Oracle\Middleware\Oracle_SOA1 -Dums.oracle.home=C:\Oracle\Middleware\Oracle_SOA1 -Dweblogic.management.discover=false -Dweblogic.management.server=http://localhost:7001 -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\Oracle\MIDDLE~1\patch_wls1036\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_oepe180\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_ocp371\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_adfr1111\profiles\default\sysext_manifest_classpath weblogic.Server
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
<Jun 28, 2012 11:25:11 PM> <FINEST> <NodeManager> <Waiting for the process to die: 4808>
<Jun 28, 2012 11:25:11 PM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
<Jun 28, 2012 11:25:11 PM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
Someone please help, if i am able to start the soa manged server, i can go ahead and install the AIA Foundation pack...
Many Thanks.

SOA Cluster- Server Migration

Hi All,
I m installing SOA suite in high availability environment (cluster) and I want to understand why I do need to configure Server Migration for SOA and OSB managed servers, what will happened if one of the managed serves fails and I didn't migrate it to the node? Does this affect the running BPEL instance by any mean? And how the users will be affected?
Any helpful answers will be appreciated
Regrads,
Ahmed Saber

Thank you Robert for your reply.
I still want to understand what will happen for the BPEL process and oracle service bus if server migration is not configured and one of the node get down.
I understood from the link you sent that there are some singleton services that can only run on one node that's fine but I still want to understand from the business point of view how this might affect BPEL process and oracle service bus?
Regards,
Ahmed

Weblogic Server Migration (WINDOWS)

Hi Experts,
I'm new on configuring server migration in windows environment, I'm Having trouble on providing the interface in nodemanager.properties for windows, for unix environments you can specify the interfaceusing the parameter below (if you want to use eth0). is there an equivalent interface (ex. eth0) in windows? if you run 'ipconfig /all' in windows cmd there are no indicated interface for every connection. please advise on this. Thanks in advance, hope someone could help me.
Thanks,
Villy
Interface=eth0
NetMask=255.255.255.0
UseMACBroadcast=true
C:\Documents and Settings\weblogic>ipconfig /all
Windows IP Configuration
        Host Name . . . . . . . . . . . . : wls2
        Primary Dns Suffix . . . . . . . :
        Node Type . . . . . . . . . . . . : Unknown
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
        Connection-specific DNS Suffix . :
        Description . . . . . . . . . . . : AMD PCNET Family PCI Ethernet Adapter
        Physical Address. . . . . . . . . : 08-00-27-5C-8F-96
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 192.168.1.107
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.1.1
        DHCP Server . . . . . . . . . . . : 192.168.1.1
        DNS Servers . . . . . . . . . . . : 192.168.10.254
                                            8.8.8.8
                                            8.8.4.4
        Lease Obtained. . . . . . . . . . : Tuesday, April 08, 2014 2:55:54 AM
        Lease Expires . . . . . . . . . . : Wednesday, April 09, 2014 2:55:54 AM
Ethernet adapter Local Area Connection 2:
        Connection-specific DNS Suffix . :
        Description . . . . . . . . . . . : AMD PCNET Family PCI Ethernet Adapter #2
        Physical Address. . . . . . . . . : 08-00-27-83-2B-31
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 192.168.1.120
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.1.1
        DHCP Server . . . . . . . . . . . : 192.168.1.1
        DNS Servers . . . . . . . . . . . : 192.168.10.254
                                            8.8.8.8
                                            8.8.4.4
        Lease Obtained. . . . . . . . . . : Tuesday, April 08, 2014 2:55:54 AM
        Lease Expires . . . . . . . . . . : Wednesday, April 09, 2014 2:55:54 AM
C:\Documents and Settings\weblogic>

Hi Prakash,
Thanks for the reference, i disabled on of my network connection and created a floating iP address. then i used the configuration below for my nodemanager.properties. my manage servers are now up and running. thanks for the help
IPCONFIG:
C:\Documents and Settings\weblogic>netsh interface ip show address "Local Area C
onnection 2"
Configuration for interface "Local Area Connection 2"
    DHCP enabled:                         No
    IP Address:                           192.168.1.112
    SubnetMask:                           255.255.255.0
    IP Address:                           192.168.1.13
    SubnetMask:                           255.255.255.0
    Default Gateway:                      192.168.1.1
    GatewayMetric:                        0
    InterfaceMetric:                      0
nodemanager.properties
Interface="Local Area Connection 2"
NetMask=255.255.255.0
UseMACBroadcast=true
Thanks.
Villy

BW Steps before and after R3 server migration

Hi Friends,
We are using ECC6 and BW 3.5.
My client is going for R3 server migration, yes it's just a migration of server and not any upgrade. This server is quite old so migrating to a higher end server.
BASIS will do a system copy during downtime i.e. a homogeneous client copy where they would just copy the DB tables. As per them all data will remain same and only the IP will change i.e. i will have to make a change in R3-BW RFC connection.
I need to know what other pre and post migration steps are involved in this case?
Thanks,
BJ

Hi,
I dont think that there would be any impact on queues etc due to server migration. We flush out data from queues only in cases of upgrade/ patch application etc. because there is a chance that after the upgrade the structure of datasource may change. In that case, any data lying in queue beforehand would get corrupted and cannot be loaded.
in your case, there is no such change going to happen, therefore no need to worry about queues. You can go ahead without worrying about any dataloss due to queues.

Unable to start Manager server using Node Manager

Hi,
I have deployed Admin server in one of my unix machine(machine1) and i able to start my Admin server using node manager, and when i try to start my Managed server in another machine(machine2) using the node manager(that machine node manager) its throwing error;
Note: am able to start Managed server using Adminurl and able to connect to Managed server node manager successfully,
but not able to start Managed server using node manager
its giving exception as below;
error:- wls:/nm/webdomain> nmStart('ms1')
Starting server ms1 ...
Error Starting server ms1: weblogic.nodemanager.NMException: Exception while starting server 'ms1'
Managed server log: -
<Dec 13, 2011 3:40:17 PM> <INFO> <NodeManager> <Working directory is '/root/Oracle/Middleware/user_projects/domains/webdomain'>
[root@LinuxVM ~]# cat /root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out00071
<Dec 13, 2011 3:40:17 PM> <INFO> <NodeManager> <Starting WebLogic server with command line: /root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/bin/java -Dweblogic.Name=ms1 -Dbea.home=/root/Oracle/Middleware -Djava.security.policy=/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Djava.library.path="/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386/jrockit:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/../lib/i386:/root/Oracle/Middleware/patch_wls1035/profiles/default/native:/root/Oracle/Middleware/patch_ocp360/profiles/default/native:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686/oci920_8" -Djava.class.path=/root/Oracle/Middleware/patch_wls1035/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/patch_ocp360/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/lib/tools.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/root/Oracle/Middleware/modules/features/weblogic.server.modules_10.3.5.0.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/root/Oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/root/Oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar::/root/Oracle/Middleware -Dweblogic.system.BootIdentityFile=/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true weblogic.Server >
<Dec 13, 2011 3:40:17 PM> <INFO> <NodeManager> <Working directory is '/root/Oracle/Middleware/user_projects/domains/webdomain'>
Nodemanager log:
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Rotated server output log to "/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out00070">
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Server error log also redirected to server log>
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Starting WebLogic server with command line: /root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/bin/java -Dweblogic.Name=ms1 -Dbea.home=/root/Oracle/Middleware -Djava.security.policy=/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Djava.library.path="/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386/jrockit:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/../lib/i386:/root/Oracle/Middleware/patch_wls1035/profiles/default/native:/root/Oracle/Middleware/patch_ocp360/profiles/default/native:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686/oci920_8" -Djava.class.path=/root/Oracle/Middleware/patch_wls1035/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/patch_ocp360/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/lib/tools.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/root/Oracle/Middleware/modules/features/weblogic.server.modules_10.3.5.0.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/root/Oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/root/Oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar::/root/Oracle/Middleware -Dweblogic.system.BootIdentityFile=/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true weblogic.Server >
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Working directory is '/root/Oracle/Middleware/user_projects/domains/webdomain'>
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Rotated server output log to "/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out00071">
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Server error log also redirected to server log>
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Server output log file is '/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out'>
<Dec 13, 2011 3:40:26 PM> <INFO> <webdomain> <ms1> <Server failed during startup so will not be restarted>
<Dec 13, 2011 3:40:26 PM> <WARNING> <Exception while starting server 'ms1'>
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServerManager.java:200)
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:604)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:119)
at weblogic.nodemanager.server.Handler.run(Handler.java:71)
at java.lang.Thread.run(Thread.java:662)

You can start a managed server as follows:
print 'START NODE MANAGER';
startNodeManager(verbose='true', NodeManagerHome=nodemanagerhomelocation, ListenPort='5556', ListenAddress='localhost');
print 'CONNECT TO NODE MANAGER';
nmConnect(adminusername, adminpassword, 'localhost', '5556', domainname, domainlocation, 'ssl');
print 'START ADMIN SERVER';
nmStart('AdminServer');
nmServerStatus('AdminServer');
print 'CONNECT TO ADMIN SERVER';
connect(adminusername, adminpassword);
print 'START MANAGED SERVER';
start('VideotheekWebServer','Server');
nmServerStatus('VideotheekWebServer');
print 'START CLUSTER';
start('VideotheekCluster','Cluster');
nmServerStatus('VideotheekServer1');
nmServerStatus('VideotheekServer2');JVM properties are set using the admin console and edit the startup properties of your managed server (configuration, server start).
The properties file (startup.properties) is saved in the directory <domain-home>/servers/<server-name>/data/nodemanager.

Stop managed server without node manager and admin server

What are the commonly used ways to stop managed Weblogic server without node manager running and without administration server running?
(I have only one solution: on the managed server startup dump process ID to a file, and then when I want to stop it, send a signal to this process ID and kill JVM. But it seems not very clean way.)
(The managed server is started when both node manager and admin server are down, and I provide boot.properties of admin server to the managed server to start.)
UPDATED: And I don't want to start neither admin server, nor node manager even temporarily.
Edited by: user12163080 on Jun 24, 2010 4:40 AM

Hai,
I read the Oracle weblogic wlst script document without Admin server you cannot connect the managed server through the WLST script. see the below lines
"The start command starts Managed Servers or clusters in a domain using Node Manager.
To use the start command, WLST must be connected to a running Administration Server.
To start Managed Servers without requiring a running Administration Server, use the
nmStart command with WLST connected to Node Manager."
"You shut down a server to which WLST is connected by entering the shutdown command
without any arguments.
When connected to a Managed Server instance, you only use the shutdown command to shut
down the Managed Server instance to which WLST is connected; you cannot shut down another
server while connected to a Managed Server instance.
WLST uses Node Manager to shut down a Managed Server. When shutting down a Managed
Server, Node Manager must be running.
In the event of an error, the command returns"
They are two option if you are using adminserver then we can stop the any Managed server.
The option is if you are using the nodemanager without admin server we can stop the any Managed server.
The last final solution to kill the particular Managed server pid.
Regards,
S.vinoth babu

Calendar Server Migration from iplanet5.2 to Sunjava messaging server

Hi
Can any one help me on Calendar server migration.
How can i migrate the calendar server from iplanet 5.2 to sunjava messaging server
Users
Calendar resources
Groups
Attributes

Hi,
I assume you mean iplanet calendar server 5.1.1 to the latest calendar server (6.3). If so, I suggest you start by reading through the calendar server admin guide which goes through the steps involved and tools to use to migrate from 5.1.1 onto calendar server 6.3.
http://www.sun.com/bigadmin/hubs/comms/library/manuals.calendar.jsp
Regards,
Shane.

Server Migration

I'm having a problem setfing up migration on my Managed Servers on Welbogic 9.2 mp2. First, My problem.
When I try to manually migrate ManagedServer1 from MachineA to MachineB:
Nodemanger shutdowns ManagedServer1
Nodemanager removes the interface with the floating IP (so far so good)
(here is where the problem starts)
Nodemanager brings up the interface back on MachineA
Nodemanager starts ManagesServer1 on MachineA (all this is suppose to happen on MachineB).
This doesn't help me if it migrates it to the same machine!!!
I quick overview of how things are set up.
1) I have two machines, MachineA and MachineB running Solaris 10
2) I have the admin server running on MachineA listening on the static ip of 139 and ManagedServer1 listening on the floating IP of 169 (fyi, don't want give out IP, so I made a number up)
3) I have ManagedServer2 running on MachineB with the floating IP of 170.
4) I created a weblogic user that has ssh trust config between the two machines and has the proper authority to create and bring down an interface.
5) Created 2 Unix machines, Type SSH with the shell command ssh -l legalint -o PasswordAuthentication=no -p %P %H /opt/bea/weblogic92/common/bin/wlscontrol.sh -d %D -n /legalint/mtdom/ndmgr -c -f startManagedWebLogic.sh -s %S %C
6) Network Time Protocal Config is set
7) Lease database schema is created with corresponding data source and has two tables ACTIVE and ACTIVE_MT
8) Server migration progerties configured: cluster datasource is set (In my directions it tells me to leave the Canidate machines blank). Managed servers auto migration set to true and primary and back-up machine set and auto-restart set to true.
Any help is appreciated.
Tom.

The best way to deal with certificates and FQDN's in ZESM is to use commercial issued certificates or from the company's internal CA. Don't use the built-in product self-signed certificates under any reason for production deployments. The reason behind that, is that the internal ZESM certificate has its private key marked as non-exportable. So you'll not be able to export it from one server and move to another.
For the server FQDN, create an A or Alias record in DNS to something like: "zesm.company.com", and point it to the actual ZESM server, that way, once you need to move all users from server, all that you need to do is to import the commercial certificate and point the DNS record to the new server IP Address.
I did a couple of deployments in that way, with no issues.
Hope this helps.
>>>
From: mauro vaccari<[email protected]>
To:novell.support.zenworks.endpoint-security-management
Date: 1/19/2010 7:36 AM
Subject: Server Migration
Hi,
planning the upgrade to the imminent release of ZESM 4.1 we would like
to reinstall the server because it has undergone many installations.
For security reason and for don't stop production we want to install
ZESM 4.1 in a new server with the same ip and name of the actual then we
want try It in a test VLAN.
My question is:
when we want to pass the new server in production or before ZESM
instalation could we migrate the IIS certificate from the old server to
new one? so the client should not be involved.
Thank you for help
mauro_vaccari
mauro_vaccari's Profile: http://forums.novell.com/member.php?userid=16902
View this thread: http://forums.novell.com/showthread.php?t=398639

Oracle HTTP Server and Node Manager

Hi,
I installed Oracle HTTP Server with Node Manager. I set "CrashRecoveryEnabled=true" in the nodemanager.properties. It works fine when I reboot the machine, but when I kill the root process (kill -9), the new process can not be started as the previous process does not have enough time to die and still uses the ports. I tried to run "nmGenBootStartupProps" in wlst, or set the
RestartMax=2
RestartDelaySeconds=5
variables in "[domain_name]/servers/[server_name]/data/nodemanager/startup.properties" - no success.
Any ideas, how to set the number of retries and the delay between restarts?
Versions:
Oracle HTTP Server: version="12.1.3.0.0"
java version "1.7.0_79"
OHS log:
[2015-05-04T11:43:48.0653+02:00] [OHS] [NOTIFICATION:16] [OHS-9999] [mod_weblogic.c] [host_id: dev-oep-soalb-1] [host_addr: 192.168.0.226] [pid: 18651] [tid: 140166670751552] [user: app] [VirtualHost: main] WebLogic Server Plugin version 12.1.3 <WLSPLUGINS_12.1.3.0.0_LINUX.X64_140421.1459>
[2015-05-04T11:43:48.0854+02:00] [OHS] [NOTIFICATION:16] [OHS-9999] [core.c] [host_id: dev-oep-soalb-1] [host_addr: 192.168.0.226] [pid: 18651] [tid: 140166670751552] [user: app] [VirtualHost: main] Oracle-HTTP-Server-12c/12.1.3.0.0 (Unix) mod_ssl/12.1.3.0.0 OtherSSL/0.0.0 mod_plsql/11.1.1.0.0 configured -- resuming normal operations
[2015-05-04T11:48:53.9584+02:00] [OHS] [INCIDENT_ERROR:32] [OHS-9999] [worker.c] [host_id: dev-oep-soalb-1] [host_addr: 192.168.0.226] [pid: 18838] [tid: 140103489120064] [user: app] [VirtualHost: main] (98)Address already in use: make_sock: could not bind to address 192.168.0.226:80
[2015-05-04T11:48:53.9585+02:00] [OHS] [INCIDENT_ERROR:20] [OHS-9999] [worker.c] [host_id: dev-oep-soalb-1] [host_addr: 192.168.0.226] [pid: 18838] [tid: 140103489120064] [user: app] [VirtualHost: main] no listening sockets available, shutting down
[2015-05-04T11:48:53.9585+02:00] [OHS] [ERROR:32] [OHS-9999] [core.c] [host_id: dev-oep-soalb-1] [host_addr: 192.168.0.226] [pid: 18838] [tid: 140103489120064] [user: app] [VirtualHost: main] Unable to open logs
Node Manager log:
<May 4, 2015 11:37:50 AM CEST> <INFO> <Loading domains file: /opt/app/soalb_domain/nodemanager/nodemanager.domains>
<May 4, 2015 11:40:18 AM CEST> <INFO> <Loading identity key store: FileName=/opt/app/soalb_domain/security/DemoIdentity.jks, Type=jks, PassPhraseUsed=true>
<May 4, 2015 11:40:18 AM CEST> <INFO> <Loaded NodeManager configuration properties from '/opt/app/soalb_domain/nodemanager/nodemanager.properties'>
<May 4, 2015 11:40:18 AM CEST> <INFO> <Node manager v12.1.3 #1604337>
<May 4, 2015 11:40:18 AM CEST> <INFO> <soalb_domain> <soalb_server1> <Startup configuration properties loaded from "/opt/app/soalb_domain/servers/soalb_server1/data/nodemanager/startup.properties">
<May 4, 2015 11:40:19 AM CEST> <INFO> <Secure socket listener started on port 5556, host localhost/127.0.0.1>
<May 4, 2015 11:43:53 AM CEST> <INFO> <soalb_domain> <soalb_server1> <The server 'soalb_server1' is running now.>
<May 4, 2015 11:48:53 AM CEST> <INFO> <soalb_domain> <soalb_server1> <The server 'soalb_server1' with process id 18672 is no longer alive; waiting for the process to die.>
<May 4, 2015 11:48:53 AM CEST> <INFO> <soalb_domain> <soalb_server1> <Server failed so attempting to restart (restart count = 1)>
<May 4, 2015 11:48:54 AM CEST> <SEVERE> <soalb_domain> <soalb_server1> <Unexpected error while monitoring server>
java.io.IOException: Failed to start the server soalb_server1
Check log file /opt/app/soalb_domain/system_components/OHS/ohs_nm.log
Check log file /opt/app/soalb_domain/servers/soalb_server1/logs/soalb_server1.log
        at oracle.ohs.plugin.nodemanager.OhsProcessManagementPlugin$ProcessImpl.buildIoException(Unknown Source)
        at oracle.ohs.plugin.nodemanager.OhsProcessManagementPlugin$ProcessImpl.start(Unknown Source)
        at weblogic.nodemanager.server.DecoratedSystemComponentManager$DecoratedProcess.start(DecoratedSystemComponentManager.java:129)
        at weblogic.nodemanager.server.ServerMonitor.startProcess(ServerMonitor.java:441)
        at weblogic.nodemanager.server.ServerMonitor.runMonitor(ServerMonitor.java:406)
        at weblogic.nodemanager.server.ServerMonitor.run(ServerMonitor.java:295)
        at java.lang.Thread.run(Thread.java:744)
ohs_nm.log:
<2015-05-04 11:48:53> <INFO> <OHS-0> <The server 'soalb_server1' with process id 18672 is no longer alive; waiting for the process to die.>
<2015-05-04 11:48:53> <INFO> <OHS-0> <Server failed so attempting to restart (restart count = 1)>
<2015-05-04 11:48:53> <INFO> <OHS-4018> <Starting server soalb_server1>
<2015-05-04 11:48:53> <INFO> <OHS-0> <Running /opt/app/ohs12c/wlserver/../ohs/bin/httpd.sh httpd.worker -k start -f /opt/app/soalb_domain/config/fmwconfig/components/OHS/instances/soalb_server1/httpd.conf>
<2015-05-04 11:48:53> <INFO> <OHS-0> <[Mon May 04 11:48:53 2015] [warn] Errors will be logged into /opt/app/soalb_domain/servers/soalb_server1/logs/soalb_server1.log>
<2015-05-04 11:48:54> <INFO> <OHS-0> </opt/app/ohs12c/wlserver/../ohs/bin/httpd.sh httpd.worker -k start -f /opt/app/soalb_domain/config/fmwconfig/components/OHS/instances/soalb_server1/httpd.conf: exit status = 1>
<2015-05-04 11:48:54> <INFO> <OHS-4005> <Check the instance log file for more information: /opt/app/soalb_domain/servers/soalb_server1/logs/soalb_server1.log>
<2015-05-04 11:48:54> <SEVERE> <OHS-0> <Failed to start the server soalb_server1>
<2015-05-04 11:48:54> <SEVERE> <OHS-0> <Unexpected error while monitoring server>
Node Manager properties:
#Wed Apr 29 18:31:26 CEST 2015
#Node manager properties
#Wed Apr 29 17:18:21 CEST 2015
DomainsFile=/opt/app/soalb_domain/nodemanager/nodemanager.domains
LogLimit=0
PropertiesVersion=12.1.3
AuthenticationEnabled=true
NodeManagerHome=/opt/app/soalb_domain/nodemanager
JavaHome=/opt/app/jdk1.7.0_79
LogLevel=INFO
DomainsFileEnabled=true
StartScriptName=startWebLogic.sh
ListenAddress=localhost
NativeVersionEnabled=true
ListenPort=5556
LogToStderr=true
SecureListener=true
LogCount=1
StopScriptEnabled=false
QuitEnabled=false
LogAppend=true
StateCheckInterval=5000
CrashRecoveryEnabled=true
StartScriptEnabled=true
LogFile=/opt/app/soalb_domain/nodemanager/nodemanager.log
LogFormatter=weblogic.nodemanager.server.LogFormatter
ListenBacklog=50
Startup properties:
#SSLArguments=-Dweblogic.security.SSL.ignoreHostnameVerification\=false -Dweblogic.ReverseDNSAllowed\=false
RestartMax=2
RestartDelaySeconds=5
FileTimeSpan=24
RestartInterval=3600
FileTimeSpanFactor=3600000
RotatedFileCount=7
RotationType=bySize
#AdminURL=http\://192.168.0.224\:7001
NumberOfFilesLimited=true
AutoRestart=true
RotationTimeStart=00\:00
FileSizeKB=500
Regards,
András

To deploy your FMX you need AS 10.1.2 Forms installed, and then you can use AS control or Forms server configuration file.
For more information regarding FMX deployment, refer to http://download.oracle.com/docs/cd/B14099_19/web.1012/b14032/toc.htm
Regards,
Preet

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider,

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider,
error: 40 - Could not open a connection to SQL Server)

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named
Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Hello,
Make sure your SQL Server service is started.
Make sure TCP\IP and names pipes protocol is enabled
Make sure you have made an exception in firewall for SQL Server connection
Make sure SQL Server browser service is enabled
Make sure you connect with correct name hostname\instance name for named instance,MSSQLSERVER for default instance and Hotname\SQLEXPRESS for express edition.
Please make sure you use port no when connecting to SQL server listeing on different port (hostname\instance ,portno)
http://blogs.msdn.com/sql_protocols/archive/2006/09/30/SQL-Server-2005-Remote-Connectivity-Issue-TroubleShooting.aspx
Hope this helps
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Server Migration/ Node Failure

Similar Messages

Maybe you are looking for