+ All Categories
Home > Documents > 11iMultiNodeInstalltion

11iMultiNodeInstalltion

Date post: 02-Dec-2014
Category:
Upload: muhammad-qasim
View: 527 times
Download: 0 times
Share this document with a friend
10
Ebusiness Suite 11i Multi Node Installation on Solaris 10
Transcript
Page 1: 11iMultiNodeInstalltion

Ebusiness Suite 11i Multi Node Installation on Solaris 10

Page 2: 11iMultiNodeInstalltion
Page 3: 11iMultiNodeInstalltion

What is Shared Appl_TOP and what is Load Balancing.

Page 4: 11iMultiNodeInstalltion

What are recommended character sets for Ebuisness Suite.

Page 5: 11iMultiNodeInstalltion
Page 6: 11iMultiNodeInstalltion
Page 7: 11iMultiNodeInstalltion

chmod 777 TST16

Page 8: 11iMultiNodeInstalltion
Page 9: 11iMultiNodeInstalltion

Error after Installation : Database Availability Check Failed.

I tried to start database,it started.I tried to start Listener it gave errors:

Log messages written to /u01/app/oracle/product/9.2.0/network/log/listener.log Error listening on: (ADDRESS=(PROTO =tcp)(PORT=1521))TNS-12532: TNS:invalid argument TNS-12560: TNS:protocol adapter error TNS-00502: Invalid argument

I searched for these errors on metalink.oracle.com and found that it could be becase the sqlnet.ora file is corrupt.

Sqlnet.ora file is automatically created along listener.ora and tnsnames.ora.tnsnames.ora is the file through which clients connect to the listener and listener.ora is the file which contains the listener name and other information about listener.sqlnet.ora is the file which contains parameter files for the listener like the init.ora has parameters for database.Doc ID :Note:380506.1 on metalink says that sqlnet.ora is corrupt it should be created manually again.It gave the soloution:

Solution1.Recreate the sqlnet.ora file manually or using NetCA or NetMgr.

-- Save the sqlnet.ora file.

2. Start the TNS Listener(s).

3. Verify the Oracle Net connectivity by using both tnsping and connecting with remote application

select * from v$version will give the version number of the database.

Solution 2 DOC-2--Note:405602.1 Change in sqlnet.ora Set protocol.validnode_checking = no in the sqlnet.ora file. When I changed this the listener started normally and worked properly.

$ tnsping EBSDB

TNS Ping Utility for Solaris: Version 9.2.0.5.0 - Production on 24-AUG-2008 13:46:58

Copyright (c) 1997 Oracle Corporation. All rights reserved.

Used parameter files:/u05/EBSDB/ebsdbdb/9.2.0/network/admin/EBSDB_titus/sqlnet_ifile.ora

Used TNSNAMES adapter to resolve the aliasAttempting to contact (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=TITUS.fujitsu.co.uk)(PORT=1547)) (CONNECT_DATA= (SID=EBSDB)))OK (20 msec)

Page 10: 11iMultiNodeInstalltion

Recommended