• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1309
  • Last Modified:

cannot start Oracle RAC instances

I have installed Oracle 9i RAC on Solaris with a Clustered file system on two nodes. It has been a very learning experience. They two nodes share the same database. The machines were rebooted suddenly and I had to restart the services manually. There is now a core dump(I suspect from the crash). When I connect as sysdba on one node
I get a message instance connected and then ORA-3113: end of file communication channel. The catch all error. I verified the logs and there was a ORA-07445 export error from the crash. On my second node which should be identical except different SID
It's like another world. I try and connect as sysdba get connected to idle instance , try to manually startup and receive ORA-0019: invalid specification and ORA-00132: syntax errors and network name 'LISTENER_SANS'   If both instances are identical with the exception of the SID names, they should both read ORA-3113. any help would be fabulous I am stumped.
0
a_coder
Asked:
a_coder
  • 2
1 Solution
 
schwertnerCommented:
About ORA-0019:

Oracle9i Information
·      Note: Default values and ranges may differ from those shown here due to variations between releases..
Parameter type       Integer
Default value       0
Parameter class       Dynamic: ALTER SYSTEM
Range of values       0 to number of session licenses
Oracle9i Real Application Clusters       Multiple instances can have different values, but the total for all instances mounting a database should be less than or equal to the total number of sessions licensed for that database.

·      LICENSE_MAX_SESSIONS specifies the maximum number of concurrent user sessions allowed. When this limit is reached, only users with the RESTRICTED SESSION privilege can connect to the database. Users who are not able to connect receive a warning message indicating that the system has reached maximum capacity.
·      A zero value indicates that concurrent usage (session) licensing is not enforced. If you set this parameter to a nonzero number, you might also want to set LICENSE_SESSIONS_WARNING (see <Parameter:LICENSE_SESSIONS_WARNING>).
·      Do not enable both concurrent usage licensing and user licensing. Set either LICENSE_MAX_SESSIONS or LICENSE_MAX_USERS to zero.
0
 
schwertnerCommented:
On startup of a RAC or single instance, if you are using local_listener
specification you may encounter failure to startup the instance.
 
Symptom(s)
~~~~~~~~~~
SQL> startup                                                        
ORA-00119: invalid specification for system parameter local_listener
ORA-00132: syntax error or unresolved network name 'LISTENER_TEST2'  
 
Change(s)
~~~~~~~~~~
Removing or hashing out the following entires in the sqlnet.ora
NAMES.DEFAULT_DOMAIN = us.oracle.com
NAMES.DIRECTORY_PATH= (TNSNAMES, ONAMES, HOSTNAME)  
 
Cause
~~~~~~~
On startup the named address for the local_listener parameter stored in tnsnames.ora
cannot be found, the NAMES.DIRECTORY_PATH resolves the  
lookup of the TNSNAMES.ORA
 
Fix
~~~~
Include in the sqlnet.ora  
NAMES.DIRECTORY_PATH= (TNSNAMES, ONAMES, HOSTNAME)  
NAMES.DEFAULT_DOMAIN = us.oracle.com
 
0
 
a_coderAuthor Commented:
Absolutely correct fixed problem #2 . I had reread all of my startup files and totally paid no attention to the fact that this was missing all the info but a single line.
Thank You
0

Featured Post

Granular recovery for Microsoft Exchange

With Veeam Explorer for Microsoft Exchange you can choose the Exchange Servers and restore points you’re interested in, and Veeam Explorer will present the contents of those mailbox stores for browsing, searching and exporting.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now