Re: Multiple instances on Oracle 8i and NT 2000 Server

From: Rauf Sarwar <rsarwar_at_ifsna.com>
Date: 4 Jul 2002 09:44:50 -0700
Message-ID: <c2d690f2.0207040844.64ea70e4@posting.google.com>

"Henk Hultink" <hhu_at_stopspam.stoas.nl> wrote in message news:<3d2401f6$1_at_news.wau.nl>...
> Is there anyone who knows of a problem with this combination?
> I had a server Win 2000 NT Server, with an Oracle 8i database up and
> running.
> I created a second instance and a database, took all the necessary steps,
> and brought it up and running. So far so good. Everything seemed to be fine.
> Then I had to bring the instance down, which I did in Server Manager, and
> then it refused to mount and open again. No errors, it just didn't respond.
> I tried to stop and restart the service, even reboot the server: nothing
> worked. I could find no problems in LISTENER.ORA, TNSNAMES.ORA, SQLNET.ORA
> or INIT.ORA.
> The Event Logger of NT only showed a warning that the service didn't start,
> but without specification.
> In fact, I even deleted the database and the instance and created it again
> from scratch: same problem.
>
> On another server there have been problems with some sort of automatic
> timeout. I connect remote to the database, but after some time of inactivity
> the connection is lost. This causes an Internet application (that works with
> ODBC) to fail. Even on the server that holds the Internet server and the
> database I cannot start the Internet application. Except when I reboot the
> server: then everything works fine for a short time.
>
> What could be the possible causes for these problems? Any suggestions are
> welcome.
>
> TIA, Henk Hultink
>
> --
> H. Hultink
> Software Engineer
> Stoas, Division OBOI
> Wageningen, The Netherlands
> "Activating Knowledge"
> http://www.stoas.nl
>
> e-mail: hhu_at_stopspam.stoas.nl

For the first part...
It is hard to tell what is wrong without looking at the Oracle alert log. You can find it in Background dump destination of your second instance. Please include it with your post.

For second part...
There is a parameter called IDLE_TIME defined under your user defined profile or DEFAULT profile. If the profile IDLE_TIME value is set to e.g. 60 (Minutes) and user has been assigned that profile, then user will get automatically disconnected from the database after 60 minutes of inactivity...Resolution: increase the IDLE_TIME value. To do..Connect as SYS@<YourDB>

SQL> select p.profile, p.resource_name, p.limit

     from dba_profiles p, dba_users u
     where p.profile = u.profile
     and p.resource_name = 'IDLE_TIME'
     and u.username = '&UserName';

SQL> ALTER PROFILE <profile name> LIMIT IDLE_TIME <New limit in minutes>;

HTH
//Rauf Sarwar Received on Thu Jul 04 2002 - 11:44:50 CDT