Dbd Error Ociserverattach 11g
Contents |
CommunityOracle User Group CommunityTopliners CommunityOTN Speaker BureauJava CommunityError: You don't have JavaScript enabled. This tool uses JavaScript and much of it will not work correctly without it enabled. Please turn JavaScript back on ora-12537 tns connection closed error and reload this page. Please enter a title. You can not
Failed To Connect To Database Instance: Ora-12541: Tns:no Listener (dbd Error: Ociserverattach).
post a blank message. Please type your message and try again. More discussions in General Database ora-12537: tns:connection closed (dbd error: ociserverattach) Discussions All PlacesDatabaseGeneral Database Discussions This discussion is archived 5 Replies Latest reply on Apr 22, 2013 12:37 PM by 985149 ORA-12537: TNS:connection closed (DBD ERROR: OCIServerAttach). ora-12537 tns connection closed oracle 10g MR139 Jan 31, 2012 3:28 PM We have OEM Grid Control 11g installed on Linux server. And we have Oracle 11gR2 RAC database on HP-UX server. I installed and configured OEM Agent on both RAC servers and it was working with out any issue, I was able to monitor from Grid Control. We have 3
Ns Main Err Code: 12537
RAC databases on the RAC server and I was able to monitor all 3. Since yesterday I am getting the following error for on Grid Control for first node of the RAC for one database, other 2 databases are fine. Status: Failed Details: Failed to connect to database instance: ORA-12537: TNS:connection closed (DBD ERROR: OCIServerAttach).But I am able to connect the database (both the instances) using TOAD or some other SQL Client. I stopped and restarted the agent but no changes. I am not sure where to look into it, can some one help me to understand the issue. I have the same question Show 0 Likes(0) 20529Views Tags: none (add) 11gContent tagged with 11g, controlContent tagged with control, gridContent tagged with grid, oracleContent tagged with oracle This content has been marked as final. Show 5 replies 1. Re: ORA-12537: TNS:connection closed (DBD ERROR: OCIServerAttach). 864403 Jan 31, 2012 7:09 PM (in response to MR139) Not sure if you have already referenced this
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Failed to connect to database instance: ORA-12637: Packet receive failed (DBD ERROR: OCIServerAttach) Want to Advertise Here? Solved Failed to connect to database instance: ORA-12637: Packet receive failed (DBD ERROR: OCIServerAttach) Posted on 2015-01-28 Oracle Database 1 Verified Solution 25 Comments 1,097 Views Last Modified: 2015-02-14 When ever I connect to the OEM I get the following https://community.oracle.com/thread/2342176 error: Failed to connect to database instance: ORA-12637: Packet receive failed (DBD ERROR: OCIServerAttach). However the other tabs in the OEM work fine in fact I can still administer the DB just fine. But I truly believe this isn't really a false positive there is something else going on and was wondering if anyone can help 0 Question by:jjmekkattil Facebook Twitter LinkedIn Google Best Solution byjjmekkattil OK so we got it to work....the problem was I had https://www.experts-exchange.com/questions/28605845/Failed-to-connect-to-database-instance-ORA-12637-Packet-receive-failed-DBD-ERROR-OCIServerAttach.html to up the Process number I had it at 150 and apparently it was too low upped it to 300 and its working like a champ. Go to Solution 24 Comments LVL 75 Overall: Level 75 Oracle Database 74 Message Active today Expert Comment by:slightwv (䄆 Netminder)2015-01-28 Never seen that error. I assume you have looked it up for possible actions? http://ora-12637.ora-code.com/ My guess would be a communications issue. When do you get that error? What versions are you dealing with (OEM and database)? 0 Message Author Comment by:jjmekkattil2015-01-28 Since Monday...Oracle 11g OEM 11g 0 LVL 75 Overall: Level 75 Oracle Database 74 Message Active today Expert Comment by:slightwv (䄆 Netminder)2015-01-28 >>Since Monday.. I mean: What exactly are you doing when that error message is generated? You also need to investigate: What changed? Don't say "nothing". Stuff just doesn't stop working for no reason. 0 Message Author Comment by:jjmekkattil2015-02-03 Ok well let me try to go with this, I do some administrative tasks in oracle and when I tried to log into SYS apparently the password expired as well as a few other users. So I ran the following SQL statement: set pagesize 99 set head off set linesize 132 set echo off set feedback off set newpage none set serveroutput on size 1000000 SPOOL D:\Repair_Users.sql DECLARE cursor USER_CRSR IS select d.USERNAME, u.P
you get the following errors: Enterprise Manager is not able to connect to the database instance. And in the “Agent connection to instance” section: Status: http://dbtricks.com/?p=34 Failed Details: ORA-28001: the password has expired (DBD ERROR: OCISessionBegin) One of the reasons could be that the password for the SYSMAN user is expired. However, changing the password alone will not http://www.nntp.perl.org/group/perl.dbi.users/2008/07/msg33103.html solve this issue. Several additional steps are required in order to make Oracle Enterprise Manager connect: Before you start: Verify that ORACLE_HOME, ORACLE_SID environment variables are set. – If not, set them dbd error using as environment variables or open a command line and type SET ORACLE_SID=
& oracle 11G Message ID: 225C945D-5726-4B04-A207-7B9C56197FBB@pharmacy.arizona.edu On Jul 29, 2008, at 8:55 PM, Jeffrey Seger wrote: > Standard troubleshooting applies: > 1. Are you running the script as the same user? and with the same > environment? (If you are running it in a webserver probably not). Yes. Moreover, setting them explicitly in the script (via the ENV statements) did not fix the issue. The same script runs just fine on our older system. > > 2. Is this running under apache? If so, are the same environment > variables > being set in httpd.conf? Or are the old 8.1.6 variables there maybe? We tried setting the env vars in apache, also no go. > > 3. Try running the script with the following code inserted near the > beginning: > foreach my $key (sort keys %ENV){ print "$key=$ENV{$key}\n"} (add > in a >
if running through a webserver) > Compare the output to `env|sort` when run by the user you are using > tnsping as. After cutting irrelevant env vars, this is what prints: oracle@tonic2:~/perl/frs> env |sort LD_LIBRARY_PATH=/home/oracle/product/11.1.0/db_1/lib ORACLE_BASE=/home/oracle ORACLE_HOME=/home/oracle/product/11.1.0/db_1 ORACLE_SID=phmweb TNS_ADMIN=/home/oracle/product/11.1.0/db_1/network/admin oracle@tonic2:~/perl/frs> ./testdbi.pl LD_LIBRARY_PATH=/home/oracle/product/11.1.0/db_1/lib ORACLE_BASE=/home/oracle ORACLE_HOME=/home/oracle/product/11.1.0/db_1 ORACLE_SID=phmweb TNS_ADMIN=/home/oracle/product/11.1.0/db_1/network/admin DBI connect('phmweb.pharmacy.arizona.edu','people',...) failed: ORA-12505: TNS:listener does not currently know of SID given in connect descriptor (DBD ERROR: OCIServerAttach) at ./testdbi.pl line 11 Database connection not made: ORA-12505: TNS:listener does not currently know of SID given in connect descriptor (DBD ERROR: OCIServerAttach) at ./testdbi.pl line 11. This is why it's driving me nuts. This is identical to the environment where tnsping works. Fortunately I can get around it by bypassing TNS and specifying the 'host=host:port;sid=sid' directly in the connection string, but I'd like to know what's wrong. The question may be academic anyway, I've been told