[Info-ingres] Ingres R3 Win Shutdown via command line

Hi
I've got a couple of items in this one. Been meaning to ask them for
some time.

The -service option doesn't seem to be in my manuals or in the
commandline help.
However ingstop and ingstart seem to work fine with -service.
I'm running II 3.0.2 (int.w32/105)

What does ingstop -check do? It reports: !Ingres instance successfully
shut down.
but doesn't seem to change anything. The same message appears whether
there are sessions or not.

Can someone talk about what happens when the shutdown fails? In a manual
shutdown scenario, the dba can retry the shutdown after kicking out the
pesky users, or use ingstop -force. In unix I have a script in
/etc/rc.d which tests if the shutdown was successful. Below is an
example DOS shutdown script using %errorlevel% to test the status.

I'd like to know what happens when someone starts a system shutdown
command and there are still sessions connected to Ingres.

Here is an example:
!
!Stopping Remote Command Server process rmcmd...
!
!Closing DBMS Server II\INGRES\c84 to new
connections............................
!
! *******************
! *** FATAL ERROR ***
! *******************
!The iimonitor connection to the DBMS Server process II\INGRES\c84
failed.
!You may reissue the ingstop command with an additional "-kill"
parameter.
! This is a last-resort measure.
!
!DBMS Server II\INGRES\c84 still has active sessions.
!
!Net Server II\COMSVR\758 still has active sessions.
!
!Data Access Server II\DASVR\a18 still has active sessions.
!
!Shutdown of active Ingres DBMS and Star servers has been aborted.
!All active DBMS and Star servers have been re-opened for connections.
!
!Active Net servers which have been closed to new connections cannot be
!re-opened. To enable new network connections to or from this
installation,
!you must start another Net server.
!
!Active Data Access servers which have been closed to new connections
cannot be
!re-opened. To enable new Data Access Server connections to or from
this installation,
!you must start another Data Access Server.
!

After this, the DBMS server is still active and, despite the message,
net server is still accepting connections. What does the operating
system shutdown do with this situation?

Finally, is there a command which allows me to shut down and prevent
user connections but allow ingres or $ingres to access the installation
for maintenance purposes like verifydb. I can start up the services
manually to prevent remote connections to all databases and I can modify
local scripts and cron jobs jobs to stop local applications. However
I'm looking for something a bit simpler. Perhaps through grant / revoke?

Paul

Myshutdown.bat
================================================== =====
Echo Stopping ingres
Ingstop -service
If %errorlevel% = 1 goto error1
Echo shutdown complete
goto end

:error1
Echo ingres did not stop. Check user sessions before continue.
pause
Ingstop -force -service
If %errorlevel% = 1 goto error2
....
================================================== =====




-----Original Message-----
From: info-ingres-admin-at-cariboulake.com
[mailto:info-ingres-admin-at-cariboulake.com] On Behalf Of
denjo02-at-hotmail.com
Sent: Tuesday, 3 January 2006 6:02 PM
To: info-ingres-at-cariboulake.com
Subject: [Info-ingres] Re: Ingres R3 Win Shutdown via command line


Emiliano wrote:
> denjo02-at-hotmail.com wrote:
> > Assuming that the DBMS is started as a service, this command should
> > shut it down for you:
> >
> > ingstop -service
>
> That'll work, but it'll confuse the windows service manager, which
> maintains its own state information. You can instead so
>
> net stop Ingres_Database_II

The "-service" parameter will start or stop the Windows service, as well
as Ingres. Works very well - you can start the service from Windows or
with the "net start ..." command, and stop it from the command line with
the "-service" parameter, or vice-versa. Seems to work a treat...

Note also that on my machine the service is named "Ingres Intelligent
Database [II]" with spaces, not underscores, but the name is easily
checked from the Windows Services screen.

John Dennis

_______________________________________________
Info-ingres mailing list
Info-ingres-at-cariboulake.com
http://mailman.cariboulake.com/mailm...py/info-ingres

Paul White wrote:

>
> Finally, is there a command which allows me to shut down and prevent
> user connections but allow ingres or $ingres to access the installation
> for maintenance purposes like verifydb. I can start up the services
> manually to prevent remote connections to all databases and I can modify
> local scripts and cron jobs jobs to stop local applications. However
> I'm looking for something a bit simpler. Perhaps through grant / revoke?
>

Hiya Paul,

I am taking it most of the people would be connecting via IngresNet ?
If so issue the command:- echo stop | netutil -file -

This will stop all IngresNet access but still leave the DBMS servers
running...

You should also issue a DAS / JDBC stop as well to be sure you've got
the lot out...

Is that a cunning plan ??

Cheers

Gary

ghingres-at-yahoo.co.uk wrote:
> Paul White wrote:
>
>
>> Finally, is there a command which allows me to shut down and prevent
>> user connections but allow ingres or $ingres to access the installation
>> for maintenance purposes like verifydb. I can start up the services
>> manually to prevent remote connections to all databases and I can modify
>> local scripts and cron jobs jobs to stop local applications. However
>> I'm looking for something a bit simpler. Perhaps through grant / revoke?
>>
>>
>
> Hiya Paul,
>
> I am taking it most of the people would be connecting via IngresNet ?
> If so issue the command:- echo stop | netutil -file -
>
> This will stop all IngresNet access but still leave the DBMS servers
> running...
>
> You should also issue a DAS / JDBC stop as well to be sure you've got
> the lot out...
using iigcstop with the port/pipe will stop NET/JDBC/DAS servers. Get
the port/pipe/socket address via iimonitor.

regards

grant