ORA-12560: TNS:protocol adapter error.

[Former Member]

Iam doing installation on solaries. I got error on create database.

When i connected in sql prompt connect /as sysdba,

i got below error:

ORA-12560: TNS:protocol adapter error.

lisnter is started.

Pls provide the solution

[markus_doehr2 · Accepted solution]

A number of issues can cause this. Please post

- version of Solaris

- version of Oracle

Markus

[Former Member · Accepted solution]

thanxs for u r reply soalris version is 10 and database version is 10.2. we still not getting the solution to resolve it

give me needful information

[markus_doehr2 · Accepted solution]

- did you install Oracle using RUNINSTALLER (all in captials) from the SAP provided DVD?

- did you install patchset 10.2.0.2 (or 10.2.0.4)?

- did you set up /etc/project and /etc/user_attr?

Markus

[Former Member · Accepted solution]

I installed oracle using ./RUNINSTALLER only and i appllied patch also.

I set up /etc/project and /etc/user_attr too.

Know i am getting ORA-27102 problem (Out of memory)

Pls suggest me....to complete the installation

[markus_doehr2 · Accepted solution]

It is very difficult if not impossible to help you without any information what you have done, what you are doing and in which phase of the installation you are.

Please post logfiles (sapinst.log - not the full log put the relevant parts) or other logfiles. If you just say "I´m getting error XY" without a context it´s very unlikely, that someone is able to help.

Markus

[Former Member]

Oracle classify this as a u2018generic protocol adapter erroru2019. In my experience it indicates that Oracle client does not know what instance to connect to or what TNS alias to use.

Possible Remedies:

If running on the server (or workstation) that is running the database (i.e. if the database is local to the machine) then try explicitly setting u2018ORACLE_SIDu2019. e.g.

set ORACLE_SID=<sid>

and then try again. If this works then consider whether to make the change permanent by specifying it as a system variable.

(Possibly 8.1.5 and later:) If running on the server (or workstation) that is running the database then check that the service name u2018OracleService<SID>u2019 ties up with the actual database SID. If the database SID is changed without recreating the service then this can lead to this error. To recreate the service:

oradimxx -delete -sid <old-sid>

oradimxx -new -sid <SID> -intpwd <internal-password> AUTO -pfile <full-init-ora-filename>

Try setting the environment variable u2018LOCALu2019 to the required connection alias (typically the database SID) and then try again. (I am informed that for UNIX systems the environment variable TWO_TASK should instead be used.) Do be sure that the application that is being used picks up the new environment variable setting. Setting this to an invalid connection alias will typically produce ORA-12154: TNS:could not resolve service name.

Ignore the error and try connecting by specifying explicitly which connection alias to use.

Check that the network connection between the client computer and the server has not failed. From the client try pinging the server. (For general guidance on troubleshooting general network connectivity problems click here.)

If the database server has its IP address dynamically allocated by DHCP then its IP address may change. This is not likely to be a problem on a local network where DNS will take care of name resolution issues, but where the database server is on a remote network and its IP address needs to be explicitly specified in the client's lmhosts file then this can be a problem because it requires periodic updates to the client's lmhosts file. If faced with this scenario then push to get the database server allocated a permanent IP address.