Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-2029095.1
Update Date:2015-12-09
Keywords:

Solution Type  Problem Resolution Sure

Solution  2029095.1 :   SuperCluster: "[INS-08109] Unexpected error occurred" While Creating RAC Database With DBCA (can occur on any platform)  


Related Items
  • Oracle Database - Enterprise Edition
  •  
  • SPARC SuperCluster T4-4
  •  
Related Categories
  • PLA-Support>Eng Systems>Exadata/ODA/SSC>SPARC SuperCluster>DB: SuperCluster_EST
  •  




Created from <SR 3-10984915581>

Applies to:

Oracle Database - Enterprise Edition - Version 12.1.0.2 and later
SPARC SuperCluster T4-4 - Version All Versions and later
Information in this document applies to any platform.

Symptoms

When trying to create a new RAC database using DBCA customer encountered the error INS-08109.

DBCA tracefile shows the following error.


WARNING: [WARNING] [INS-08109] Unexpected error occurred while validating inputs at state 'databaseTypePage'.
  CAUSE: No additional information available.
  ACTION: Contact Oracle Support Services or refer to the software manual.
  SUMMARY:
      - maxDatafiles
oracle.install.commons.flow.FlowException: [INS-08109] Unexpected error occurred while validating inputs at state 'databaseTypePage'.
at oracle.install.commons.flow.AbstractFlowExecutor.validate(AbstractFlowExecutor.java:407)
at oracle.install.commons.flow.AbstractFlowExecutor.leaveVertex(AbstractFlowExecutor.java:644)
at oracle.install.commons.flow.AbstractFlowExecutor.transition(AbstractFlowExecutor.java:336)
at oracle.install.commons.flow.AbstractFlowExecutor.nextState(AbstractFlowExecutor.java:276)
at oracle.install.commons.flow.AbstractFlowExecutor.nextViewState(AbstractFlowExecutor.java:235)
at oracle.install.commons.flow.DefaultFlowNavigator.goForward(DefaultFlowNavigator.java:58)
at oracle.install.commons.flow.jewt.FlowWizard$1.run(FlowWizard.java:137)
at oracle.install.commons.flow.jewt.FlowWizard$TransitionManager$1.run(FlowWizard.java:113)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:682)
Caused by: java.lang.NoSuchFieldError: maxDatafiles
at oracle.sysman.assistants.dbca.backend.TemplateManager.updateControlfileAttributes(TemplateManager.java:1796)
at oracle.sysman.assistants.dbca.backend.TemplateManager.getParsedAttributes(TemplateManager.java:1595)
at oracle.sysman.assistants.dbca.backend.TemplateManager.parseCloneTemplate(TemplateManager.java:1341)
at oracle.sysman.assistants.dbca.backend.TemplateManager.loadTemplate(TemplateManager.java:600)
at oracle.sysman.assistants.dbca.backend.TemplateManager.loadCurrentTemplate(TemplateManager.java:658)
at oracle.sysman.assistants.dbca.wizard.view.DatabaseTypePage.doValidate(DatabaseTypePage.java:322)
at oracle.sysman.assistants.util.wizard.WizardPanel.validate(WizardPanel.java:269)
at oracle.install.commons.flow.validation.ValidationHelper.validateView(ValidationHelper.java:168)
at oracle.install.commons.flow.AbstractFlowExecutor.validate(AbstractFlowExecutor.java:391)
... 13 more

 

This error is NOT Supercluster specific and can occur on any platform.

 

Changes

By default SuperCluster is delivered with the following patches installed to customer:

/u01/app/oracle/product/12.1.0.2/dbhome_1/OPatch/opatch lsinventory -detail|grep -i applied
Patch  18639439     : applied on Thu Apr 30 15:10:20 EDT 2015
Patch  20415564     : applied on Wed Apr 29 14:37:00 EDT 2015
Patch  20594149     : applied on Wed Apr 29 14:36:00 EDT 2015
Patch  20299022     : applied on Wed Apr 29 14:33:04 EDT 2015

 

Cause

Oneoff patch 18639439 which was installed on customer system to fix a different DBCA issue is causing the problem.

Solution

1: Rollback patch 18639439 on all the nodes

2: Re-download patch 18639439 dated Aug 21 2015 or later

3: Recreate database using DBCA again.


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback