ORA-04930: open sequence number failed or initial state is valid
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
Is This Answer Correct ? | 0 Yes | 0 No |
ORA-07474: snclrd: close error, unable to close sgadef.dbf file.
LFI-01007: Line is too long; encountered in function string.
ORA-22310: ALTER TYPE error. Refer to table "string"."string" for errors
ORA-00028: your session has been killed
RMAN-06106: this command requires that target database be mounted
ORA-01353: existing Logminer session
ORA-31660: metadata filter name can not be defaulted
ORA-09833: addCallback: bad message format.
TNS-01039: %s has string service handler(s)
TNS-04143: Unable to write the new CMAN.ORA file.
DRG-52204: error while registering index
TNS-12608: TNS: Send timeout occurred