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

ORA-19555: invalid LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value

1 Answers  

---

ORA-28004: invalid argument for function specified in PASSWORD_VERIFY_FUNCTION string

1 Answers  

---

SQL*Loader-00461: direct path loading of datatype for column string not supported

1 Answers  

---

NZE-28823: Number of random bytes to generate is not specified.

1 Answers  

---

ORA-02712: osnpop: malloc failed

1 Answers  

---

LFI-01523: rename() failed.

1 Answers  

---

ORA-16591: unknown field "string" in document

1 Answers  

---

ORA-01255: cannot shutdown - file string in recovery manager backup

1 Answers  

---

NNL-00970: System query index number: number

1 Answers  

---

DGM-16900: Unable to initialize client

1 Answers  

---

ORA-15126: component within ASM file name 'string' exceeds maximum length

1 Answers  

---

TNS-02402: Bad CLBGNAMES parameter in tnsnames.ora

1 Answers  

---