Forum Stats

  • 3,782,553 Users
  • 2,254,664 Discussions
  • 7,880,121 Comments

Discussions

Created Domain failed, Forms 11.1.2.1 on Win7

Takurit-Oracle
Takurit-Oracle Member Posts: 6
edited Oct 22, 2013 6:02PM in Forms

Hi

Hope to hear any advice.

Trying to install WLS10.3.6 + Forms11.1.2.1 on Windows7 32bit.

But facing error and failed to Create Domain.

Please let me know cause of this error.

Total Physical Memory:     3,255 MB

Available Physical Memory: 2,065 MB

Virtual Memory: Max Size:  6,508 MB

Virtual Memory: Available: 5,063 MB

Virtual Memory: In Use:    1,445 MB

- nodemanger stoped

- no space or () in PATH

- set C:\TMP

- intall user is not Admin user, but grant Admin priviledges

- Virus Scan set off before config

If this may cause of not enough memory, please let me know how to check not enough memory.

Need to evidence for this

Error: addTemplate() failed. Do dumpStack() to see details.

oracle.as.provisioning.exception.ASProvWorkflowException: Problem invoking WLST - Traceback (innermost last):

  File "C:\TMP\tmp1381374081295.py", line 45, in ?

  File "C:\TMP\WLSTOfflineIni3175891067729527083.py", line 89, in addTemplate

  at com.oracle.cie.domain.script.jython.CommandExceptionHandler.handleException(CommandExceptionHandler.java:51)

  at com.oracle.cie.domain.script.jython.WLScriptContext.handleException(WLScriptContext.java:1538)

  at com.oracle.cie.domain.script.jython.WLScriptContext.addTemplate(WLScriptContext.java:420)

  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

  at java.lang.reflect.Method.invoke(Method.java:606)

com.oracle.cie.domain.script.jython.WLSTException: com.oracle.cie.domain.script.jython.WLSTException: com.oracle.cie.domain.script.ScriptException: unable to parse "template-info.xml" from template jar "D:/ICF_AutoCapsule_disabled/Oracle/Middleware/Oracle_FRHome1/common/templates/applications/classic_template_11.1.2.jar

  at oracle.as.provisioning.weblogic.ASDomain._createDomain(ASDomain.java:2958)

  at oracle.as.provisioning.weblogic.ASDomain.createDomain(ASDomain.java:2476)

  at oracle.as.provisioning.engine.WorkFlowExecutor._createDomain(WorkFlowExecutor.java:633)

  at oracle.as.provisioning.engine.WorkFlowExecutor.executeWLSWorkFlow(WorkFlowExecutor.java:391)

  at oracle.as.provisioning.engine.Config.executeConfigWorkflow_WLS(Config.java:866)

  at oracle.as.install.classic.ca.standard.StandardWorkFlowExecutor.execute(StandardWorkFlowExecutor.java:65)

  at oracle.as.install.classic.ca.standard.AbstractProvisioningTask.execute(AbstractProvisioningTask.java:26)

  at oracle.as.install.classic.ca.standard.StandardProvisionTaskList.execute(StandardProvisionTaskList.java:61)

  at oracle.as.install.classic.ca.ClassicConfigMain.doExecute(ClassicConfigMain.java:124)

  at oracle.as.install.engine.modules.configuration.client.ConfigAction.execute(ConfigAction.java:371)

  at oracle.as.install.engine.modules.configuration.action.TaskPerformer.run(TaskPerformer.java:88)

  at oracle.as.install.engine.modules.configuration.action.TaskPerformer.startConfigAction(TaskPerformer.java:105)

  at oracle.as.install.engine.modules.configuration.action.ActionRequest.perform(ActionRequest.java:15)

  at oracle.as.install.engine.modules.configuration.action.RequestQueue.perform(RequestQueue.java:64)

  at oracle.as.install.engine.modules.configuration.standard.StandardConfigActionManager.start(StandardConfigActionManager.java:160)

  at oracle.as.install.engine.modules.configuration.boot.ConfigurationExtension.kickstart(ConfigurationExtension.java:81)

  at oracle.as.install.engine.modules.configuration.ConfigurationModule.run(ConfigurationModule.java:86)

  at java.lang.Thread.run(Thread.java:662)

oracle.as.provisioning.exception.ASProvisioningException

  at oracle.as.provisioning.engine.Config.executeConfigWorkflow_WLS(Config.java:872)

  at oracle.as.install.classic.ca.standard.StandardWorkFlowExecutor.execute(StandardWorkFlowExecutor.java:65)

  at oracle.as.install.classic.ca.standard.AbstractProvisioningTask.execute(AbstractProvisioningTask.java:26)

  at oracle.as.install.classic.ca.standard.StandardProvisionTaskList.execute(StandardProvisionTaskList.java:61)

  at oracle.as.install.classic.ca.ClassicConfigMain.doExecute(ClassicConfigMain.java:124)

  at oracle.as.install.engine.modules.configuration.client.ConfigAction.execute(ConfigAction.java:371)

  at oracle.as.install.engine.modules.configuration.action.TaskPerformer.run(TaskPerformer.java:88)

  at oracle.as.install.engine.modules.configuration.action.TaskPerformer.startConfigAction(TaskPerformer.java:105)

  at oracle.as.install.engine.modules.configuration.action.ActionRequest.perform(ActionRequest.java:15)

  at oracle.as.install.engine.modules.configuration.action.RequestQueue.perform(RequestQueue.java:64)

  at oracle.as.install.engine.modules.configuration.standard.StandardConfigActionManager.start(StandardConfigActionManager.java:160)

  at oracle.as.install.engine.modules.configuration.boot.ConfigurationExtension.kickstart(ConfigurationExtension.java:81)

  at oracle.as.install.engine.modules.configuration.ConfigurationModule.run(ConfigurationModule.java:86)

  at java.lang.Thread.run(Thread.java:662)

Caused by: oracle.as.provisioning.exception.ASProvWorkflowException: Error Executing workflow.

  at oracle.as.provisioning.engine.WorkFlowExecutor._createDomain(WorkFlowExecutor.java:686)

  at oracle.as.provisioning.engine.WorkFlowExecutor.executeWLSWorkFlow(WorkFlowExecutor.java:391)

  at oracle.as.provisioning.engine.Config.executeConfigWorkflow_WLS(Config.java:866)

  ... 13 more

Tagged:

Answers

  • 979801
    979801 Member Posts: 164

    This is due to mismatch version compatibility. oracle forms 11.1.2.1 compatible with weblogic server 10.3.5

  • Hi

    Thank you for your update.

    You mean we have to use WLS10.3.5 + Forms11.1.2.1?

    However Certification Matrix said

    "Oracle Forms and Reports 11.1.2.1.0 is certified with WebLogic Server and 10.3.5 and 10.3.6."

    Let me know if i misunderstanding

    Thanks

  • lake
    lake Member Posts: 1,154

    I would go over the install directions again about what version of jdk it wants (and that includes bitness). Just because that's an important thing to check.

    There are many points of failure possible. You must follow the installation instructions extremely carefully in every regard.

  • 979801
    979801 Member Posts: 164

    You may use weblogic 10.3.6. but you have to put a deep eye on log files during installation.As my suggestion weblogic 10.3.5 works better with forms11.1.2.1.

  • Scott_Symonds
    Scott_Symonds Member Posts: 73 Blue Ribbon

    Actually, it is recommended to install Forms 11.1.2.1 with WebLogic 10.3.6 as this allows you to use Java 7, the most secure Java version to date where WebLogic 10.3.5 only allows Java 6. I have done dozens of Forms 11.1.2.1 installations using WebLogic 10.3.6. From these installs, I have found a couple other root causes to the problem that you have not noted that you tried yet. I'll post some ideas below:

    1. Check to see if your PC or server name contains any underscores “_”. This has been known to cause domain creation failures. Try modifying your PC or server hostname to remove any underscores (the best recommendation would be to only use alphanumeric characters and hyphens). NOTE: A PC/server reboot will be required to activate this change.
      1. Example of a bad hostname: oracle_server123.oracle.com
      2. Example of a good hostname: oracle-server123.oracle.com
    2. Verify the admin user permissions your account has by going to %MIDDLEWARE_HOME%\user_projects\domains\%DOMAIN_NAME%\config\fmwconfig\bootstrap and try to open cwallet.sso using Notepad (the file is not text-friendly, but this can be used as a quick test). If you happen to get permission errors, try the following steps:
      • Go to the location where your Oracle folder is located. (Example: C:\Oracle)
      • Right-click on the Oracle folder and select Properties.
      • Select the Security tab and select the Administrators group. NOTE: Make sure your user account you are using is the same one who installed WebLogic and the Forms/Reports binaries and has full control permissions to the Oracle folder. If not, please do this first before continuing.
      • Click the Advanced button at the bottom of the window.
      • In the Advanced Security Settings for the folder location, you’ll see that the “Inherited From” column is set to “<not inherited>”.
      • Select your user account and click the “Change Permissions” button
      • Near the bottom, check the box that says “Replace all existing inheritable permissions on all descendants with inheritable permissions from this object” or any similar message. It should be the second check box in this window.
      • Click OK.
      • It may take a little bit of time (usually not more than a minute) to modify the permissions for all files in the directory and subdirectories. NOTE: If it tells you that access to cwallet.sso is denied or if it prompts you that you need administrative privileges to access, you can ignore this message as you’ll need to reconfigure the domain anyway (a new cwallet.sso file will get created when you retry the Forms configuration). When finished, click OK, then click OK again.

    Other useful tips can also be found at this knowledge base article at http://pitss.com/us/2012/10/08/oracle-forms-configuration-hangs-at-creating-domain/. Hope this helps!

    Thanks,

    Scott

    Scott_Symonds
  • lake
    lake Member Posts: 1,154
    edited Oct 22, 2013 6:12PM

    Wow great information. Thanks so much for taking the time to share this. I will be installing the most recent version of forms in the upcoming months and I know from past experience that there are many things that can go wrong.

    One thing though. The all time best way to deal with bad directory names in the path like "program files (x86)", excessively large directory names, some other unexpected characters, etc is to create a junction (soft link)  to that directory. Then the junction name is put in the path where the bad directory name used to be.

    http://msdn.microsoft.com/en-us/library/windows/desktop/aa363878%28v=vs.85%29.aspx

    Creating soft links is done with mklink

    http://en.wikipedia.org/wiki/NTFS_symbolic_link
    mklink [[/d] | [/h] | [/j]] <Link> <Target>
This discussion has been closed.