RE: Oracle... one DB connects, one does not...

  • From: "Robert Freeman" <robertgfreeman@xxxxxxxxx>
  • To: "Steve Perry" <sperry@xxxxxxxxxxx>
  • Date: Wed, 19 Jul 2006 20:56:36 -0600

We have tried different JDBC clients, no joy there.
The listener seems to be working fine, though I might just try switching
ports.
We are connecting to the two databases from the same environment, so all the
application components are the same.

We are using thin JDBC, so its like a direct connect... no service names.

RF

-----Original Message-----
From: Steve Perry [mailto:sperry@xxxxxxxxxxx]
Sent: Wednesday, July 19, 2006 8:54 PM
To: robertgfreeman@xxxxxxxxx
Cc: oracle-l@xxxxxxxxxxxxx Freelists
Subject: Re: Oracle... one DB connects, one does not...


are you connecting as "/ as sysdba" or using a service name? Is the
application on the same server or different server?
if different server, can you use tcpdump to get any information or
strace?
Are you saying it connects fine, but can't issue sql or can't connect?
I got called from a developer yesterday that couldn't get the
database. the app was working the day before and nothing had been
changed. at the end of the day, he said it was a corrupt jdbc driver.
he said he switched it to the thin client driver and it "magically"
started working.  It doesn't sound like that's the case since you can
connect to the 2nd db and things are fine.

Have you tried changing the port of the first database and see the
app works?
I've also seen where the database doesn't register to the listener
and had to issue "alter system register" or put the database in the
listener.ora. probably only applicable if you can't connect though



On Jul 19, 2006, at 09:21 PM, Robert Freeman wrote:

> Don't think so... remember that both of the databases (one working
> and one
> not working) are on the same machine, though they are using a
> different
> port. What is also odd is that if the database is left up
> overnight, then it
> starts working.... if it's shutdown overnight it doesn't start
> working. We
> killed all the jobs (thinking it was the job scheduler) and that
> did not
> make a difference. We killed all CRON jobs, still nothing. No
> remote jobs
> are scheduled.
>
> It's the darndest thing I've ever seen. Still a few more things to
> test here
> and there though.
>
> RF
>
>
> -----Original Message-----
> From: Mladen Gogala [mailto:gogala@xxxxxxxxxxxxx]
> Sent: Wednesday, July 19, 2006 6:32 PM
> To: robertgfreeman@xxxxxxxxx
> Cc: oracle-l@xxxxxxxxxxxxx
> Subject: Re: Oracle... one DB connects, one does not...
>
>
> On 07/19/2006 01:08:22 PM, Robert Freeman wrote:
>> All,
>>
>> I have a rather stange problem. I have a database on
>> LINUX that we created. We then exported data from a
>> VMS database and imported it to the Linux database. I
>> can connect just fine in SQL*Plus... but our JDBC
>> application is freezing up when trying to issue a
>> query.
>>
>> What is *really* odd is:
>>
>> 1. After about 12 hours of inactivity, it starts
>> working ok again. So something is getting reset. We
>> have been trying to figure out what it might be, but
>> we have yet to be able to do so.
>>
>> 2. We created another database, on the same box, with
>> the same configuration, and imported the data again
>> from the same dump file and we don't have the same
>> problem.
>>
>> Any ideas???
>
> Rob, it looks like some stupid SELinux or IP_Tables trick.
> Is something blocking you and enforcing some kind of idiotic
> security policy? Turn that off.
>
>
> --
> Mladen Gogala
> http://www.mgogala.com
>
> --
> //www.freelists.org/webpage/oracle-l
>
>

--
//www.freelists.org/webpage/oracle-l

Other related posts:

  1. Home
  2. oracle-l
  3. Archive
  4. 07-2006