I Google[d] for this error ORA-12560: TNS:protocol adaptor error but not able to find the actual reason and how to solve this error ?
Can anyone tell me a perfect solution to solve login problem.
asked Aug 1, 2011 at 5:39
Vishwanath DalviVishwanath Dalvi
34.8k41 gold badges122 silver badges153 bronze badges
- Go to the windows machine that hosts the Oracle database server
-
Go to Start -> Run -> Services.msc in Windows.
Locate OracleService < SID > (hereOracleServiceORCL) and click onStartto start the oracle database service (if not already running)
-
Once it is up and running, from the command prompt run the following:
tnsping < tnsalias >(tnsalias entry you can find it in
tnsnames.orafile)
answered Aug 1, 2011 at 21:06
BharathiBharathi
1,5332 gold badges10 silver badges13 bronze badges
6
Seems like database is not up. It might be due to restarting machine and the instance is not set to autostart and it so not started munually after starting from services Screen.
Just goto Command prompt
-
Set Oracle SID
C:>set oracle_sid=ORCL -
Now run Net start command.
C:>net start oracleserviceORCL
answered Dec 6, 2012 at 6:32
Yasir AhmedYasir Ahmed
2993 silver badges2 bronze badges
2
from command console, if you get this error you can avoid it by typing
c:> sqlplus /nolog
then you can connect
SQL> conn user/pass @host:port/service
maruf
5593 gold badges6 silver badges22 bronze badges
answered Feb 26, 2016 at 17:27
demiandemian
5926 silver badges14 bronze badges
Add to the enviroment vars the following varibale and value to identify the place of the tnsnames.ora file:
TNS_ADMIN
C:oracleproduct10.2.0client_1networkadmin
answered May 14, 2013 at 14:33
1
In my case (for OracleExpress) the service was running, but I got this issue when trying to access the database via sqlplus without connection identifier:
sqlplus sys/mypassword as sysdba
To make it work I needed to add the connection identifier (XE for Oracle Express), so following command worked ok:
sqlplus sys/mypassword@XE as sysdba
If you still get ORA-12560, make sure you can ping the XE service. Use:
tnsping XE
And you should get OK message along with full connection string (tnsping command is located in oracle’s installation dir: [oracle express installation dir]apporacleproduct11.2.0serverbin). If you can not ping make sure your tnsnames.ora file is reachable for sqlplus. You might need to set TNS_ADMIN environment variable pointing to your ADMIN directory, where the file is located, for example:
TNS_ADMIN=[oracle express installation dir]apporacleproduct11.2.0servernetworkADMIN
answered Mar 14, 2017 at 14:09
walkeroswalkeros
4,5804 gold badges34 silver badges46 bronze badges
After searching alot got a simple way to solve it.
Just follow the steps.
- Check status of your listener.
- open command prompt and type
lsnrctl status - You will get no listener.
- open command prompt and type
-
Now open
listener.orafile which is present in following directory:C:oraclexeapporacleproduct11.2.0servernetworkADMIN- Open that file and change the host parameter with you computer name
-
You can get your computer name by right click on
My Computerand check you computer name, and replace host parameter with your computer name as follows:LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
(ADDRESS = (PROTOCOL = TCP)(HOST = Electron-PC)(PORT = 1521)
)
)
)So here you can observe
HOST = Electron-PC, which is my computer name. -
Save the listener.ora file and again return to cammand propt
3.Type the following in command prompt
lsnrctl start
This will start the OracleTNSListner.
you can check it in the service by opening services tab of Task Manager. if not started automatically you can start it.
Just this much and you are ready to work again on oracle.
Best of Luck.
Ori Lentz
3,6586 gold badges21 silver badges28 bronze badges
answered Jan 19, 2016 at 6:56
MrinmoyMrinmoy
1,3702 gold badges18 silver badges28 bronze badges
1
Quite often this means that the listener hasn’t started. Check the Services panel.
On Windows (as you are) another common cause is that the ORACLE_SID is not defined in the registry. Either edit the registry or set the ORACLE_SID in a CMD box. (Because you want to run sqlplusw.exe I suggest you edit the registry.)
answered Aug 1, 2011 at 10:15
APCAPC
143k19 gold badges172 silver badges281 bronze badges
I have solved the problem the easy way. My oracle was running just fine in the past. After I installed MS SQL Server was when I noticed this problem. I just uninstalled MS SQL Server on my machine then the problem was gone. Make sure you restart your computer after that. Now I can connect to Oracle database through SQLPlus again. My guess is that there’s some conflict between the two. Hope this helps.
answered Aug 22, 2013 at 5:19
Another possible solution that just worked for me…considering I was using my local login as the dba permissions.
Follow the steps to get to Services. Right click on the instance and go to ‘Log On’? (might not be the name but it’s one of the tabs containing permissions). Change the settings to use LOCAL.
answered Jul 15, 2016 at 14:01
0
If none the above work, then try this :
Modify the LISTENER.ora (mine is found in : oracleproduct11.2.0dbhome_1NETWORKADMINlistener.ora) ==> add a custom listener that points to your database(SID), example my SID is XZ0301, so :
## Base XZ03001
SID_LIST_LISTENER_XZ03001=(SID_LIST=(SID_DESC=(ORACLE_HOME =
E:oracleproduct11.2.0dbhome_1)(SID_NAME= XZ03001)))
LISTENER_XZ03001=(DESCRIPTION_LIST=(ADDRESS=(PROTOCOL =
TCP)(HOST=MyComputerName)(PORT= 1521)))
DIAG_ADR_ENABLED_LISTENER_XZ03001=ON
ADR_BASE_LISTENER_XZ03001=E:oracle
Restart your machine
For Windows 7, use the following to modify the LISTENER.ora:
— Go to Start > All Programs > Accessories
— Right click Notepad and then click Run as Administrator .
— File>open and navigate to the tnsnames.ora file.
— Make the changes then it should allow you to save
answered Sep 22, 2013 at 16:20
It really has worked on my machine. But instead of OracleServiceORCL I found OracleServiceXE.
answered Oct 6, 2013 at 7:03
Flow the flowing steps :
-
Edit your listener.ora and tnsnames.ora file in
$Oracle_homeproduct11.2.0client_1NETWORKADMIN locationa. add listener.ora file
LISTENER = (DESCRIPTION_LIST = (DESCRIPTION = (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521)) (ADDRESS = (PROTOCOL = TCP)(HOST = 127.0.0.1)(PORT = 1521)) ))
ADR_BASE_LISTENER = C: [here c is oralce home directory]
b. add in tnsnames.ora file
SCHEMADEV =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = dabase_ip)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = SCHEMADEV)
)
)
- Open command prompt and type
sqlplus username/passowrd@oracle_connection_alias
Example :
username : your_database_username
password : Your_database_password
oracle_connection_alias : SCHEMADEV for above example.
answered May 22, 2017 at 9:02
Just to add up, follow the screenshot and choose local account to start if not selected. Then start the service.
answered Jul 31, 2020 at 6:12
VaibsVaibs
1,97822 silver badges29 bronze badges
You need to tell SQLPlus which database you want to log on to. Host String needs to be either a connection string or an alias configured in your TNSNames.ora file.
answered Aug 1, 2011 at 5:46
Andrew CooperAndrew Cooper
32k5 gold badges79 silver badges115 bronze badges
ORA-12560: TNS:erro de adaptador de protocolo
- set Environment Variables: ORACLE_BASE, ORACLE_HOME, ORACLE_SID
- make sure your user is part of ORACLE_GROUP_NAME (Windows)
- make sure the file ORACLE_HOME/network/admin/sqlnet.ora is:
SQLNET.AUTHENTICATION_SERVICES = (NTS) - (Windows) Be carefull when you add a new Oracle client: adding a new path to the PATH env. variable can mess things up. The first entry in this variable makes a difference: certify that the sqlplus executable in the ORACLE_HOME (ORACLE_HOME/bin) comes first in the PATH env. variable.
answered Sep 25, 2017 at 17:24
I try 2 option:
- You change service OracleService in Service Tab -> Running
- Login with cmd command: sqlplus user_name/pass_word@orcl12C
Note: orcle12c -> name of OracleService name run in you laptop
answered Oct 19, 2020 at 6:58
Below fixes can be applied to resolve TNS 12560 error
- Get Latest patch for
SQL*NETclient software - Set
$ORACLE_HOMEand$PATHvariable (should be accessible for System user) - Check permissions on PC client
- Check
$TNS_ADMINvariable - Check if network has firewall or antivirus issues
- Check if windows services Run >> Services.msc has OracleXE or OracleORCL service running
Check below link in case of net tracing error:
http://dba-oracle.com/t_sql_net_tracing.htm
C. Peck
3,5763 gold badges18 silver badges36 bronze badges
answered May 24, 2021 at 17:41
In my case, (ORA-12560: TNS protocol adapter error)Issue cause of database connection issue like database, user name and password.
Once you got the issue. Initially you have to check connection details, after check the oracle service and further more.
I missed some connection details, So only i got TNS protocol adapter error,
I will changed the connection details, It would be working fine.
answered Feb 13, 2017 at 12:27
muthukumarmuthukumar
1481 silver badge10 bronze badges
As we all know that Oracle is free and open business management software that is available for both personal and commercial use. Oracle database uses object-relational database management system that allows to process credit card payments, support and manages customer orders, handles customers, etc.
This networking software does the task of exchange of data between machines using underlying services to establish communication between the components. Establishment of communication happens due to some set of services, these services are known as Transparent Network Substrate (TNS). However, sometimes due to some uncertain reasons, when this service is taken into action, throws an error stated as ‘ORA-12560 TNS Protocol Adapter Error’
So, here, in this blog today, I will let you know how to fix ora-12560 tns protocol adapter error in easy ways. But before that, let us have a brief look at the Oracle TNS which throws an error.
About Oracle Transparent Network Substrate (TNS)
Transparent Network Substrate is a service that handles communication with oracle components with its database codes and pre-programmed schema. The acronym TNS occurs in various instances, when you get an error. TNS uses various protocols, which could be TCP/IP, DECNET, SPX/IPX, AppleTalk etc.
All these combination of TNS and the hidden protocols used to help in networking makes the connection establish between components. The Oracle Transparent Network Substrate (TNS) facilitates simple inter-database communication and has an built-in management layer over the standard network topology. But sometimes there may occur some communication error while connecting to the database. And one of the errors is ORA-12560 TNS Protocol Adapter Error which happens whenever there is a problem in accessing a specific server of the database.
ORA-12560 TNS Protocol Adapter Error takes place due to several reasons, but the most common is the server problem. This problem arises when a user does not specify which database or server was being accessed or there may be incorrect password provided to the database. Instead of giving exact reasons for the connection error, Oracle simply prompts ORA-12560 TNS Protocol Adapter Error. In short, if you want to troubleshoot this error, then you have to ensure the following:
- Listener is up and pointing to the desired database service
- Database service is up
- Oracle variables are configured in a correct manner which includes ORACLE_BASE, ORACLE_HOME, ORACLE_SID, PATH, TNS_ADMIN
- Cross check the firewall and the network configurations
- Full access is applicable to ORACLE_HOME including its sub-directories
Ways To Fix ORA-12560 TNS Protocol Adapter Error
Here are the best ways you can try to fix ORA-12560 TNS Protocol Adapter Error. Try them one by one and see which fix works in your case. Let’s get started with the first solutions…..
Fix #1: Set Correct ORACLE_SID
If you are running on a server that is running the database (i.e. database is local to machine) then it is important to first make sure that you have set a correct ORACLE_SID. If it is set correctly then it is good and if not then you have to try the below steps:
First of all, go to the command prompt and then run the below command:
- Set Oracle Database SID as
Set oracle_sid=ORCL
- Next, run Net Start command
Net start oracleserviceORCL
Fix #2: Check The Service Name ‘Oracleservice<SID>’ Ties Up With The Actual Database SID
Another method you can try to fix ora-12560 tns protocol adapter error is to check the service name ties up with the actual database SID. If, in any case, database SID changes without recreating service then this can lead this error. In this case, you have to recreate this service by following this step:
oradimxx -delete -sid <old-sid>
oradimxx -new -sid <SID> –intpwd <internal-password> AUTO –pfile <full-init-ora-filename>
Fix #3: Restart The Oracle Service
If the above method doesn’t work, maybe the OracleService for the database is not running. Check for the service, if it is not running then starts the service. If it is running then restart the service. To do so, you have to follow the below steps:
- First of all, you have to go to Start option.
- Next, you have to type Run and open it.
- Now, on the dialogue box, you have to type services.msc and then hit Enter.
- After this, you have to navigate to find OracleServicesORCL and then select the service and simply click on Start to initiate oracle database server if it’s not already running.
- After it has been done and running, from the command prompt run the following:
Tnsping<tnsalias> (tnsalias entry you can find it in tnsnames.ora file)
Fix #4: Try Oracle File Repair Tool To Fix ORA 12560: TNS: protocol adapter Error
If the above guides are out of your mind and you are perplexed what to do and wonder now how to fix ORA 12560 TNS protocol adapter error then don’t worry. For your rescue, there is a tool named Oracle File Repair Tool which will help you out. This tool doesn’t require any technical knowledge to use the steps.
Steps To Fix ORA 12560 TNS Protocol Adapter Using Tool
Step 1: Run Oracle File Repair Tool and you would see options to select or search corrupt Oracle databases in your computer.
Step:2 Click on Scan File to start the scan process after selecting the oracle database. On the left-side pane, recoverable objects get listed.
Step 3: Click an object to see its preview.
Step 4: : Click Start Repair in the icon bar to start the repair process. A prompt message occurs which will guide you further. Click next and continue.
Step 5: Provide user name, password and path of the blank database where you want to save the repaired database objects.
Step 6: Repairing and restoring various database objects after establishing a connection with blank oracle database.
This way you could fix ORA 12560: TNS protocol adapter error. Hope it helps.
Final Verdict
While using Oracle database if you ever come across and error stated as ‘ora-12560 tns protocol adapter error’ then you have come to the right place. I am saying so because I have already mentioned here the best fixes you can try to fix ora-12560 tns protocol adapter error.
All these fixes are easy to apply and the best part is that you do not need any technical knowledge to perform these fixes. All you have to do is to just follow the step by step guide to resolve ora-12560 tns protocol adapter error.
Jacob Martin is a technology enthusiast having experience of more than 4 years with great interest in database administration. He is expertise in related subjects like SQL database, Access, Oracle & others. Jacob has Master of Science (M.S) degree from the University of Dallas. He loves to write and provide solutions to people on database repair. Apart from this, he also loves to visit different countries in free time.
Fatal NI connect error TNS-12545,12560,ORA-609 in Database alert log (Doc ID 2318699.1)
Last updated on MARCH 31, 2022
Applies to:
Symptoms
Connections seems to be failing and reporting following errors in alert log .
Fatal NI connect error 12545, connecting to:
(LOCAL=NO)
VERSION INFORMATION:
TNS for 64-bit Windows: Version 12.2.0.1.0 — Production
Oracle Bequeath NT Protocol Adapter for 64-bit Windows: Version 12.2.0.1.0 — Production
Windows NT TCP/IP NT Protocol Adapter for 64-bit Windows: Version 12.2.0.1.0 — Production
Time: 16-OCT-2017 13:47:17
Tracing not turned on.
Tns error struct:
ns main err code: 12545
TNS-12545: Connect failed because target host or object does not exist
ns secondary err code: 12560
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
2017-10-16T13:47:17.930336+02:00
opiodr aborting process unknown ospid (35868) as a result of ORA-609
2017-10-16T13:49:47.338831+02:00
Changes
New installation or Ip address for the database server has been changed to a new static entry
Cause
To view full details, sign in with your My Oracle Support account.
Don’t have a My Oracle Support account? Click to get started!
In this Document
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.
Oracle offers a comprehensive and fully integrated stack of cloud applications and platform services. For more information about Oracle (NYSE:ORCL), visit oracle.com. пїЅ Oracle | Contact and Chat | Support | Communities | Connect with us | 


Источник
«Fatal NI connect error 12560, connecting to: » when running report to PDF
While using Report Builder 10.1.2.0.2, I am running into a problem with some of my reports. All of my reports will run to screen in without a problem. As soon as I try and run a report to PDF the the builder closes and produces 2 files. What is very strange is that the reports work fine if i run them to screen. I need to run them to PDF. The 2 files producded are sqlnet.log and hs_err_pid1420.log file:
hs_err_pid1420.log looks like this:
Unexpected Signal : EXCEPTION_ACCESS_VIOLATION (0xc0000005) occurred at PC=0x80675E0
Function=[Unknown.]
Library=C:DevSuiteHome_1jdkjrebinclientjvm.dll
NOTE: We are unable to locate the function name symbol for the error
just occurred. Please refer to release documentation for possible
reason and solutions.
Current Java thread:
at oracle.reports.engine.EngineImpl.CRunReport(Native Method)
at oracle.reports.engine.EngineImpl.run(EngineImpl.java:437)
at oracle.reports.server.JobManager.runJobInEngine(JobManager.java:916)
— locked (a oracle.reports.engine.EngineImpl)
at oracle.reports.server.ExecAsynchJobThread.run(ExecAsynchJobThread.java:54)
Dynamic libraries:
0x00400000 — 0x00533000 C:DevSuiteHome_1binrwbuilder.exe
0x7C900000 — 0x7C9B0000 C:WINDOWSsystem32ntdll.dll
0x7C800000 — 0x7C8F5000 C:WINDOWSsystem32kernel32.dll
0x77C10000 — 0x77C68000 C:WINDOWSsystem32MSVCRT.dll
0x7E410000 — 0x7E4A0000 C:WINDOWSsystem32USER32.dll
0x77F10000 — 0x77F57000 C:WINDOWSsystem32GDI32.dll
0x66220000 — 0x6623C000 C:DevSuiteHome_1binnn.dll
0x64CE0000 — 0x64DBD000 C:DevSuiteHome_1binUIW.dll
0x64CA0000 — 0x64CB1000 C:DevSuiteHome_1binUTL.dll
0x77DD0000 — 0x77E6B000 C:WINDOWSsystem32ADVAPI32.dll
0x77E70000 — 0x77F02000 C:WINDOWSsystem32RPCRT4.dll
0x77FE0000 — 0x77FF1000 C:WINDOWSsystem32Secur32.dll
0x64CD0000 — 0x64CD7000 C:DevSuiteHome_1binUTC.dll
0x60730000 — 0x607DC000 C:DevSuiteHome_1binoracore10.dll
0x608D0000 — 0x60963000 C:DevSuiteHome_1binoranls10.dll
0x62B40000 — 0x62B53000 C:DevSuiteHome_1binoraunls10.dll
0x60C40000 — 0x60C47000 C:DevSuiteHome_1binorauts.dll
0x71AB0000 — 0x71AC7000 C:WINDOWSsystem32WS2_32.dll
0x71AA0000 — 0x71AA8000 C:WINDOWSsystem32WS2HELP.dll
0x76B40000 — 0x76B6D000 C:WINDOWSsystem32WINMM.dll
0x774E0000 — 0x7761D000 C:WINDOWSsystem32ole32.dll
0x64CC0000 — 0x64CC9000 C:DevSuiteHome_1binUTJ.dll
0x64F10000 — 0x64F21000 C:DevSuiteHome_1binUIIM.dll
0x73000000 — 0x73026000 C:WINDOWSsystem32WINSPOOL.DRV
0x5D090000 — 0x5D12A000 C:WINDOWSsystem32COMCTL32.dll
0x64ED0000 — 0x64EF6000 C:DevSuiteHome_1binUIOLE.dll
0x763B0000 — 0x763F9000 C:WINDOWSsystem32comdlg32.dll
0x77F60000 — 0x77FD6000 C:WINDOWSsystem32SHLWAPI.dll
0x7C9C0000 — 0x7D1D6000 C:WINDOWSsystem32SHELL32.dll
0x663D0000 — 0x66414000 C:DevSuiteHome_1binCA.dll
0x66340000 — 0x6636A000 C:DevSuiteHome_1binmmc.dll
0x616B0000 — 0x61891000 C:DevSuiteHome_1binoraclient10.dll
0x62B60000 — 0x62B66000 C:DevSuiteHome_1binoravsn10.dll
0x60D30000 — 0x60DE8000 C:DevSuiteHome_1binoracommon10.dll
0x60300000 — 0x60720000 C:DevSuiteHome_1binorageneric10.dll
0x629C0000 — 0x629D2000 C:DevSuiteHome_1binorasnls10.dll
0x62B80000 — 0x62C86000 C:DevSuiteHome_1binoraxml10.dll
0x00320000 — 0x00331000 C:WINDOWSsystem32MSVCIRT.dll
0x607E0000 — 0x608CC000 C:DevSuiteHome_1binoran10.dll
0x62000000 — 0x6202C000 C:DevSuiteHome_1binoranl10.dll
0x62030000 — 0x62042000 C:DevSuiteHome_1binoranldap10.dll
0x62090000 — 0x62184000 C:DevSuiteHome_1binorannzsbb10.dll
0x61E10000 — 0x61E52000 C:DevSuiteHome_1binoraldapclnt10.dll
0x61F30000 — 0x61F47000 C:DevSuiteHome_1binorancrypt10.dll
0x71AD0000 — 0x71AD9000 C:WINDOWSsystem32WSOCK32.dll
0x76D60000 — 0x76D79000 C:WINDOWSsystem32iphlpapi.dll
0x77120000 — 0x771AB000 C:WINDOWSsystem32OLEAUT32.dll
0x621A0000 — 0x621D7000 C:DevSuiteHome_1binoranro10.dll
0x621F0000 — 0x621FC000 C:DevSuiteHome_1binorantcp10.dll
0x61F70000 — 0x61F76000 C:DevSuiteHome_1binoranhost10.dll
0x61F20000 — 0x61F26000 C:DevSuiteHome_1binorancds10.dll
0x62210000 — 0x62216000 C:DevSuiteHome_1binorantns10.dll
0x60970000 — 0x60C31000 C:DevSuiteHome_1binorapls10.dll
0x62500000 — 0x62507000 C:DevSuiteHome_1binoraslax10.dll
0x627B0000 — 0x628B3000 C:DevSuiteHome_1binoraplp10.dll
0x618B0000 — 0x61905000 C:DevSuiteHome_1binorahasgen10.dll
0x622B0000 — 0x622E6000 C:DevSuiteHome_1binoraocr10.dll
0x622F0000 — 0x62315000 C:DevSuiteHome_1binoraocrb10.dll
0x5B860000 — 0x5B8B4000 C:WINDOWSsystem32NETAPI32.dll
0x76BF0000 — 0x76BFB000 C:WINDOWSsystem32PSAPI.DLL
0x62A80000 — 0x62AF6000 C:DevSuiteHome_1binorasql10.dll
0x65050000 — 0x6576D000 C:DevSuiteHome_1binrw.dll
0x64AB0000 — 0x64AC4000 C:DevSuiteHome_1binZRC.dll
0x66AC0000 — 0x66AC5000 C:DevSuiteHome_1binD2SC.dll
0x66810000 — 0x66A2B000 C:DevSuiteHome_1binDE.dll
0x627A0000 — 0x627AF000 C:DevSuiteHome_1binoraplc10.dll
0x64E30000 — 0x64E93000 C:DevSuiteHome_1binUIREM.dll
0x659A0000 — 0x659EE000 C:DevSuiteHome_1binROS.dll
0x662F0000 — 0x66320000 C:DevSuiteHome_1binmmi.dll
0x64F50000 — 0x64F66000 C:DevSuiteHome_1binUICC.dll
0x662C0000 — 0x662DF000 C:DevSuiteHome_1binmms.dll
0x662A0000 — 0x662B0000 C:DevSuiteHome_1binmmv.dll
0x73B50000 — 0x73B67000 C:WINDOWSsystem32AVIFIL32.dll
0x77BE0000 — 0x77BF5000 C:WINDOWSsystem32MSACM32.dll
0x75A70000 — 0x75A91000 C:WINDOWSsystem32MSVFW32.dll
0x66250000 — 0x6627E000 C:DevSuiteHome_1binmmw.dll
0x64FB0000 — 0x64FDA000 C:DevSuiteHome_1binUCOL.dll
0x665F0000 — 0x665F5000 C:DevSuiteHome_1bindfc.dll
0x66210000 — 0x66215000 C:DevSuiteHome_1binobs.dll
0x65010000 — 0x6503E000 C:DevSuiteHome_1binrws.dll
0x64AD0000 — 0x64C05000 C:DevSuiteHome_1binVGS.dll
0x76390000 — 0x763AD000 C:WINDOWSsystem32IMM32.DLL
0x773D0000 — 0x774D3000 C:WINDOWSWinSxSx86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2982_x-ww_ac3f9c03comctl32.dll
0x10000000 — 0x10007000 C:Program FilesLogitechMouseWareSystemLgWndHk.dll
0x755C0000 — 0x755EE000 C:WINDOWSsystem32msctfime.ime
0x08000000 — 0x08139000 C:DevSuiteHome_1jdkjrebinclientjvm.dll
0x00F80000 — 0x00F87000 C:DevSuiteHome_1jdkjrebinhpi.dll
0x00FA0000 — 0x00FAE000 C:DevSuiteHome_1jdkjrebinverify.dll
0x00FB0000 — 0x00FC9000 C:DevSuiteHome_1jdkjrebinjava.dll
0x00FD0000 — 0x00FDD000 C:DevSuiteHome_1jdkjrebinzip.dll
0x03C30000 — 0x03C3F000 C:DevSuiteHome_1jdkjrebinnet.dll
0x71A50000 — 0x71A8F000 C:WINDOWSSystem32mswsock.dll
0x76F20000 — 0x76F47000 C:WINDOWSsystem32DNSAPI.dll
0x76FB0000 — 0x76FB8000 C:WINDOWSSystem32winrnr.dll
0x76F60000 — 0x76F8C000 C:WINDOWSsystem32WLDAP32.dll
0x76FC0000 — 0x76FC6000 C:WINDOWSsystem32rasadhlp.dll
0x03DA0000 — 0x03DA6000 C:DevSuiteHome_1BINrwu.dll
0x047D0000 — 0x04828000 C:WINDOWSsystem32hnetcfg.dll
0x71A90000 — 0x71A98000 C:WINDOWSSystem32wshtcpip.dll
0x04940000 — 0x04946000 C:DevSuiteHome_1jdkjrebinioser12.dll
0x04A60000 — 0x04D25000 C:WINDOWSsystem32xpsp2res.dll
0x04F50000 — 0x04FB6000 C:WINDOWSSystem32spoolDRIVERSW32X863LMAAT2DA.DLL
0x04FC0000 — 0x04FF1000 C:WINDOWSSystem32spoolDRIVERSW32X863LMAAT2DU.DLL
0x77C00000 — 0x77C08000 C:WINDOWSsystem32VERSION.dll
0x05000000 — 0x050B5000 C:WINDOWSSystem32spoolDRIVERSW32X863LMAAT2DL.DLL
0x050C0000 — 0x051C8000 C:WINDOWSSystem32spoolDRIVERSW32X863LMAAT2UI.DLL
0x76380000 — 0x76385000 C:WINDOWSsystem32MSIMG32.dll
0x052E0000 — 0x05347000 C:WINDOWSSystem32spoolDRIVERSW32X863LMAAT2DD.DLL
0x06300000 — 0x06412000 C:DevSuiteHome_1jdkjrebinawt.dll
0x06420000 — 0x06471000 C:DevSuiteHome_1jdkjrebinfontmanager.dll
0x73760000 — 0x737A9000 C:WINDOWSsystem32ddraw.dll
0x73BC0000 — 0x73BC6000 C:WINDOWSsystem32DCIMAN32.dll
0x73940000 — 0x73A10000 C:WINDOWSsystem32D3DIM700.DLL
0x06AE0000 — 0x06AEC000 C:DevSuiteHome_1bind2scrw32.dll
0x06AF0000 — 0x06B25000 C:DevSuiteHome_1binrmdll61.dll
0x06B30000 — 0x06B83000 C:DevSuiteHome_1binOCI.dll
0x06B90000 — 0x06B9C000 C:DevSuiteHome_1binrmdg61.dll
0x73DD0000 — 0x73ECE000 C:WINDOWSsystem32MFC42.DLL
0x06BA0000 — 0x06C5B000 C:DevSuiteHome_1binckver61.dll
0x06C60000 — 0x06C74000 C:DevSuiteHome_1binrsj61.dll
0x06C80000 — 0x06C94000 C:DevSuiteHome_1binrmum61.dll
0x06CA0000 — 0x06CB5000 C:DevSuiteHome_1binrmf61.dll
0x06CC0000 — 0x06CDD000 C:DevSuiteHome_1binrmzip61.dll
0x06CE0000 — 0x06D1B000 C:DevSuiteHome_1binckmta61.dll
0x06D20000 — 0x06D38000 C:DevSuiteHome_1bincwbsoc61.dll
0x06D40000 — 0x06D4B000 C:DevSuiteHome_1bincwblclient61.dll
0x06D50000 — 0x06D59000 C:DevSuiteHome_1bincwbmsg61.dll
0x06D60000 — 0x06D66000 C:DevSuiteHome_1bincwnls61.dll
0x06D70000 — 0x06DAB000 C:DevSuiteHome_1bincwg61.dll
0x06DB0000 — 0x06E0B000 C:DevSuiteHome_1binawrdll61.dll
0x06E10000 — 0x06E1A000 C:DevSuiteHome_1binawrs61.dll
0x06E20000 — 0x06E27000 C:DevSuiteHome_1binawre61.dll
0x06E30000 — 0x06E3E000 C:DevSuiteHome_1bincwicon61.dll
0x06E40000 — 0x06EE7000 C:DevSuiteHome_1binckprp61.dll
0x6DB60000 — 0x6DB71000 C:WINDOWSsystem32CTL3D32.dll
0x06EF0000 — 0x06EFC000 C:DevSuiteHome_1bincwa61.dll
0x06F00000 — 0x06F29000 C:DevSuiteHome_1bincwr61.dll
0x06F30000 — 0x06F3A000 C:DevSuiteHome_1binuwwiz61.dll
0x06F40000 — 0x06F47000 C:DevSuiteHome_1binrmum61l.dll
0x07360000 — 0x0736D000 C:DevSuiteHome_1bincwnls61l.dll
0x07780000 — 0x0778A000 C:DevSuiteHome_1binawrdl61l.dll
0x07790000 — 0x077EC000 C:DevSuiteHome_1binCKPRP61L.DLL
0x077F0000 — 0x077FE000 C:DevSuiteHome_1binuwwiz61l.dll
0x058F0000 — 0x058F6000 C:DevSuiteHome_1bind2scrw32l.dll
0x04950000 — 0x04985000 C:DevSuiteHome_1binOCMAX10.DLL
0x77920000 — 0x77A13000 C:WINDOWSsystem32SETUPAPI.dll
0x049C0000 — 0x049CB000 C:Program FilesCommon FilesLogitechScrollingLgMsgHk.dll
0x76080000 — 0x760E5000 C:WINDOWSsystem32MSVCP60.dll
0x05F90000 — 0x05FB3000 C:DevSuiteHome_1jdkjrebincmm.dll
0x068C0000 — 0x068DE000 C:DevSuiteHome_1jdkjrebinjpeg.dll
0x77B40000 — 0x77B62000 C:WINDOWSsystem32appHelp.dll
0x76FD0000 — 0x7704F000 C:WINDOWSsystem32CLBCATQ.DLL
0x77050000 — 0x77115000 C:WINDOWSsystem32COMRes.dll
0x77A20000 — 0x77A74000 C:WINDOWSSystem32cscui.dll
0x76600000 — 0x7661D000 C:WINDOWSSystem32CSCDLL.dll
0x75F80000 — 0x7607D000 C:WINDOWSsystem32browseui.dll
0x5AD70000 — 0x5ADA8000 C:WINDOWSsystem32UxTheme.dll
0x769C0000 — 0x76A73000 C:WINDOWSsystem32USERENV.dll
0x76980000 — 0x76988000 C:WINDOWSsystem32LINKINFO.dll
0x76990000 — 0x769B5000 C:WINDOWSsystem32ntshrui.dll
0x76B20000 — 0x76B31000 C:WINDOWSsystem32ATL.DLL
0x71B20000 — 0x71B32000 C:WINDOWSsystem32MPR.dll
0x75F60000 — 0x75F67000 C:WINDOWSSystem32drprov.dll
0x71C10000 — 0x71C1E000 C:WINDOWSSystem32ntlanman.dll
0x71CD0000 — 0x71CE7000 C:WINDOWSSystem32NETUI0.dll
0x71C90000 — 0x71CD0000 C:WINDOWSSystem32NETUI1.dll
0x71C80000 — 0x71C87000 C:WINDOWSSystem32NETRAP.dll
0x71BF0000 — 0x71C03000 C:WINDOWSSystem32SAMLIB.dll
0x75F70000 — 0x75F79000 C:WINDOWSSystem32davclnt.dll
0x0B140000 — 0x0B709000 C:WINDOWSsystem32ieframe.dll
0x5DCA0000 — 0x5DCE5000 C:WINDOWSsystem32iertutil.dll
0x61410000 — 0x61534000 C:WINDOWSsystem32urlmon.dll
0x7E290000 — 0x7E401000 C:WINDOWSsystem32SHDOCVW.dll
0x77A80000 — 0x77B14000 C:WINDOWSsystem32CRYPT32.dll
0x77B20000 — 0x77B32000 C:WINDOWSsystem32MSASN1.dll
0x754D0000 — 0x75550000 C:WINDOWSsystem32CRYPTUI.dll
0x76C30000 — 0x76C5E000 C:WINDOWSsystem32WINTRUST.dll
0x76C90000 — 0x76CB8000 C:WINDOWSsystem32IMAGEHLP.dll
0x771B0000 — 0x7727E000 C:WINDOWSsystem32WININET.dll
0x07F90000 — 0x07F99000 C:WINDOWSsystem32Normaliz.dll
0x75CF0000 — 0x75D81000 C:WINDOWSsystem32MLANG.dll
0x59A60000 — 0x59B01000 C:WINDOWSsystem32DBGHELP.dll
Heap at VM Abort:
Heap
def new generation total 1152K, used 1023K [0x10010000, 0x10140000, 0x113c0000)
eden space 1088K, 93% used [0x10010000, 0x1010eae8, 0x10120000)
from space 64K, 7% used [0x10130000, 0x10131370, 0x10140000)
to space 64K, 0% used [0x10120000, 0x10120000, 0x10130000)
tenured generation total 13972K, used 8382K [0x113c0000, 0x12165000, 0x20010000)
the space 13972K, 59% used [0x113c0000, 0x11bef988, 0x11befa00, 0x12165000)
compacting perm gen total 22016K, used 21908K [0x20010000, 0x21590000, 0x24010000)
the space 22016K, 99% used [0x20010000, 0x215753f8, 0x21575400, 0x21590000)
Local Time = Mon Aug 18 14:37:27 2008
Elapsed Time = 4253
#
# HotSpot Virtual Machine Error : EXCEPTION_ACCESS_VIOLATION
# Error ID : 4F530E43505002EF
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
#
# Java VM: Java HotSpot(TM) Client VM (1.4.2_06-b03 mixed mode)
#
sqlnet.log file looks like this:
***********************************************************************
Fatal NI connect error 12560, connecting to:
(DESCRIPTION=(ADDRESS=(PROTOCOL=BEQ)(PROGRAM=oracle)(ARGV0=oracleORCL)(ARGS='(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))’))(CONNECT_DATA=(SID=ORCL)(CID=(PROGRAM=C:DevSuiteHome_1binrwbuilder.exe)(HOST=LAB013727)(USER=mmullown))))
VERSION INFORMATION:
TNS for 32-bit Windows: Version 10.1.0.4.0 — Production
Oracle Bequeath NT Protocol Adapter for 32-bit Windows: Version 10.1.0.4.0 — Production
Time: 18-AUG-2008 13:28:07
Tracing not turned on.
Tns error struct:
ns main err code: 12560
TNS-12560: TNS:protocol adapter error
ns secondary err code: 0
nt main err code: 530
TNS-00530: Protocol adapter error
nt secondary err code: 126
nt OS err code: 0
***********************************************************************
Fatal NI connect error 12560, connecting to:
(DESCRIPTION=(ADDRESS=(PROTOCOL=BEQ)(PROGRAM=oracle)(ARGV0=oracleORCL)(ARGS='(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))’))(CONNECT_DATA=(SID=ORCL)(CID=(PROGRAM=C:DevSuiteHome_1binrwbuilder.exe)(HOST=LAB013727)(USER=mmullown))))
VERSION INFORMATION:
TNS for 32-bit Windows: Version 10.1.0.4.0 — Production
Oracle Bequeath NT Protocol Adapter for 32-bit Windows: Version 10.1.0.4.0 — Production
Time: 18-AUG-2008 13:28:07
Tracing not turned on.
Tns error struct:
ns main err code: 12560
TNS-12560: TNS:protocol adapter error
ns secondary err code: 0
nt main err code: 530
TNS-00530: Protocol adapter error
nt secondary err code: 126
nt OS err code: 0
THIS ERROR DOESN’T HAPPEN TO EVERY REPORT, JUST ABOUT 20% of them. I’m hoping i can figure out what is causing this problem and so i dont have to rewrite every report that runs into this issue.
Thanks guru’s for your help in advance!!
Источник
In my previous articles i have given the explanation of different types of errors like ORA-01000 error,ORA-03113 error,ORA-01722 error with examples and its probable solutions.In this article i will try to explain another most common error which will be searched 22 K times on google per month.As there are multiple type of errors like syntax errors,semantic errors,database connectivity error,Server Error.ORA-12560 error lies in connectivity error of oracle.To resolve this error user needs to check the connectivity of database with servers.There are some possible steps to resolve this error.
“ORA-12560 will be searched approximately 22000 times on google per month.”
Why ORA-12560 error will come?
There are lot of types of errors like syntax errors,server errors,connectivity error.ORA-12560 is server connectivity error when user tries to connect the database.Most of the times when user installs oracle first time this error will occur.
Situation :
First time installation
This error will occur mostly when user installs oracle first time and tries to connect it.When user tries to insert the username and password the following error come :
Enter password: ERROR: ORA-12560: TNS:protocol adapter error
This error will come if Listener is not up or problem in tnsnames or database is not up.After installation of oracle user needs to up all the services including listener.
NO TIME TO READ CLICK HERE TO GET THIS ARTICLE
Resolution of the Error :
As i explained you this error pure connectivity error.When database tries to connect but it will not be able to get listener or services are not up then this error will come.To resolve this errors user needs to do some checkpoints and take corrective actions to resolve this error. Following are some checkpoint to resolve this error :
Solution 1:
Check listener status
User needs to check the listener status.The listener should be up and running.For checking the listener status kindly execute lsnrctl status.
Solution 2:
Check Oracle variables
User needs to check $ORACLE_HOME and $PATH variables.
Solution 3 :
Check updated patches
While connecting with SQL PLUS check that patches are updated one and if that are not updated then get the latest patch.
Solution 4 :
Services are up and running.
Check all services are up and running.
Solution 5 :
Check permissions and network firewall
Check all permissions as well as firewall settings
Solution 6:
Check TNSNAMES entry
User needs to check TNSNAMES entry.
Solution 7:
ORACLE_SID parameters
User needs to check the ORACLE_SID parameters set properly in registry.
These are above some possible solutions of this most common error.Hope everyone likes this article.Don’t forget to share this article by clicking the share button below.












