Monday, October 29, 2012

Step Creating ASInstance failed

We were getting this error during PFRD config.sh execution to create domain and instance.

Checked the install<timestamp>.out file and saw below messages:

java.lang.Exception: oracle.as.provisioning.exception.ASProvisioningException
    at oracle.as.install.classic.ca.standard.InstanceProvisioningTask.doExecute(InstanceProvisioningTask.java:222)
    at oracle.as.install.classic.ca.standard.StandaloneTool.execute(StandaloneTool.java:50)
    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:335)
    at oracle.as.install.engine.modules.configuration.action.TaskPerformer.run(TaskPerformer.java:87)
    at oracle.as.install.engine.modules.configuration.action.TaskPerformer.startConfigAction(TaskPerformer.java:104)
    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:63)
    at oracle.as.install.engine.modules.configuration.standard.StandardConfigActionManager.start(StandardConfigActionManager.java:158)
    at oracle.as.install.engine.modules.configuration.boot.ConfigurationExtension.kickstart(ConfigurationExtension.java:81)
    at oracle.as.install.engine.modules.configuration.ConfigurationModule.run(ConfigurationModule.java:83)
    at java.lang.Thread.run(Thread.java:619)
Caused by: oracle.as.provisioning.exception.ASProvisioningException
    at oracle.as.provisioning.engine.Config.executeConfigWorkflow_WLS(Config.java:872)
    at oracle.as.install.classic.ca.standard.InstanceProvisioningTask.doExecute(InstanceProvisioningTask.java:218)
    ... 12 more
Caused by: oracle.as.provisioning.engine.CfgWorkflowException
    at oracle.as.provisioning.engine.Engine.processEventResponse(Engine.java:596)
    at oracle.as.provisioning.fmwadmin.ASInstanceProv.createInstance(ASInstanceProv.java:178)
    at oracle.as.provisioning.fmwadmin.ASInstanceProv.createInstanceAndComponents(ASInstanceProv.java:116)
    at oracle.as.provisioning.engine.WorkFlowExecutor._createASInstancesAndComponents(WorkFlowExecutor.java:523)
    at oracle.as.provisioning.engine.WorkFlowExecutor.executeWLSWorkFlow(WorkFlowExecutor.java:439)
    at oracle.as.provisioning.engine.Config.executeConfigWorkflow_WLS(Config.java:866)
    ... 13 more
Caused by: oracle.as.provisioning.util.ConfigException:
Error creating ASInstance inb_inst.
Cause:
An internal operation has failed: Error in starting opmn server
Operation aborted because of a system call failure or internal error

Action:
See logs for more details.
    at oracle.as.provisioning.util.ConfigException.createConfigException(ConfigException.java:123)
    at oracle.as.provisioning.fmwadmin.ASInstanceProv._createInstance(ASInstanceProv.java:317)
    at oracle.as.provisioning.fmwadmin.ASInstanceProv.createInstance(ASInstanceProv.java:166)
    ... 17 more
Caused by: oracle.as.management.opmn.optic.OpticException: Error in starting opmn server
Operation aborted because of a system call failure or internal error
    at oracle.as.management.opmn.optic.OpmnAdmin.executeCommand(OpmnAdmin.java:310)
    at oracle.as.management.opmn.optic.OpmnAdmin.startOpmnServer(OpmnAdmin.java:87)
    at oracle.as.provisioning.fmwadmin.ASInstanceProv._createInstance(ASInstanceProv.java:254)
    ... 18 more
opmnctl start: opmn failed to start.
 
 Cause:
An internal operation has failed: Error in starting opmn server
Operation aborted because of a system call failure or internal error

This is mostly related to network issues. So checked /etc/hosts file. It had no issues.
Then tried "nslookup" for the hostname and it timed out for DNS server and then used local DNS(/etc/hosts) to successfully resolve the name.

Later we found that the timeout received from DNS server was the main reason behind this instance creation failure, as the instance creation would timeout and report error if it doesnt complete in certain amount of time which seem to be lower than dns timeout.

We realized that the DNS server setting were incorrect and after correcting that nslookup did not fail. 

Also the instance creation step was successful.

HTH.

Monday, October 15, 2012

TNS-12599: TNS:cryptographic checksum mismatch

Lately noticing these errors a lot in alert.log of our newly upgraded 11g databases.

NI cryptographic checksum mismatch error: 12599.

  VERSION INFORMATION:
        TNS for Linux: Version 11.2.0.2.0 - Production        Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.2.0 - Production
        TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.2.0 - Production
  Time: 13-OCT-2012 14:37:56
  Tracing not turned on.
  Tns error struct:
    ns main err code: 12599

TNS-12599: TNS:cryptographic checksum mismatch
    ns secondary err code: 2526
    nt main err code: 0
    nt secondary err code: 0
    nt OS err code: 0

Our sqlnet.ora does have ASO parameters:

 SQLNET.ENCRYPTION_SERVER = REQUESTED

I see bunch of these errors right after start of the Oracle database. After investigating found that this is caused by dbconsole.

Whenever I tried to login to dbconsole it generated this error message in alert.log. There was no error on dbconsole screen.

I haven't found any solution to this error yet apart from stopping dbconsole. I will update once I have found a solution to this.

Wednesday, October 3, 2012

ORA-00972 or ORA-00903 while creating an object

I am reading 2 Day DBA for 11gR2 and came across below statement:

A schema object name must abide by certain rules. In addition to being unique within a schema, a schema object name cannot be longer than 30 bytes and must begin with a letter. If you attempt to create an object with a name that violates any of these rules, then the database raises an error.

I was curious to see what error codes would be that if the rules are violated. Below is the answer:


SQL> create table aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa(srno number);
create table aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa(srno number)
             *
ERROR at line 1:
ORA-00972: identifier is too long


SQL> create table aaaaaaaaaaaaaaaaaaaaaaaaaaaaaa(srno number);

Table created.

SQL> create table 1a(srno number);
create table 1a(srno number)
             *
ERROR at line 1:
ORA-00903: invalid table name