Answer / guest

Cause: Either Shared Sequence Number OS component was not
installed properly, or an MC hardware failure may have
occurred or a previous instance was not shut down properly.

Action: Verify that there are no background or foreground
Oracle processes from a previous instance on this node using
the OS command ps -ef|grep <instance_name>. Verify that
there are no shared memory segments belonging to the user
which owns the Oracle installation by isuing the ipcs -b OS
command. If there are shared memory segments or processes
still on the system, use svrmgrl to shutdown the instance
with the abort option. If the instance is not up, verify
that the cluster software and/or the hardware is installed
and working. Log in as superuser and issue the cnxshow
command. Are all of the nodes in the cluster listed? Are
they members of the cluster? Is the communications between
nodes okay? If the answer to any of these questions is
false, contact Digital's customer support organization.

Please add more information about this Error

SQL*Loader-00604: Error occurred on an attempt to commit

1 Answers  

---

ORA-30454: summary contains STDDEV without corresponding SUM & COUNT

1 Answers  

---

ORA-01503: CREATE CONTROLFILE failed

1 Answers  

---

TNS-12657: No algorithms installed

1 Answers  

---

ORA-19019: Invalid context passed to DBMS_XMLGEN.GETXML

1 Answers  

---

ORA-26518: push queue synchronization error detected

1 Answers  

---

TNS-01061: The password has not been set

1 Answers  

---

RMAN-04015: error setting target database character set to string

1 Answers  

---

ORA-35578: (SQLOUT11) SQL cursor 'number' cannot be used with CURRENT OF <cursor name> syntax

1 Answers  

---

NNF-04003: Entry in inputfile is too long

1 Answers  

---

TNS-12233: TNS:Failure to accept a connection

1 Answers  

---

DRG-11119: operation is not supported by this index type

1 Answers  

---