Ingres II 2.5\0011 and MS Terminal Services
Leandro Pinto Fava
Yes I had the same problem here.
I have information from CA's Support that Ingres 2.5 doesn't support Microsoft Terminal Services.
Maybe Ingres 2.6 does support Terminal Services.
Regards,
Leandro Fava
DBA
Universidade de Santa Cruz do Sul-UNISC
www.unisc.br
Fone: +55 51 3717 7424
-----Original Message-----
From: Willem Meertens [mailto:ing...@wpmproductions.org]
Sent: sábado, 31 de agosto de 2002 16:21
To: info-...@ams.org
Subject: Ingres II 2.5\0011 and MS Terminal Services
Hello,
Does anyone now if there is some problem with running an Ingres II 2.5
DBMS on a Win2000 - server with Terminal Services installed on it.
It looks like it that a problem occurs when you start up a terminal
client session, but I am not sure of that.
Is it a configuration problem?
Has anyone had this problem also?
How can I prevent to server from "hanging" (become out of locks)?
Regards,
Willem Meertens
Below a piece from the errlog.log
VIETNAM ::[CD\COMSVR\7b0 , 00000002]: Fri Aug 30 17:45:07 2002
E_GC220E_AL_FSM_STATE AL internal error: Invalid state transition in
AL FSM. Input = 12, state = 3
VIETNAM ::[CD\COMSVR\7b0 , 00000002]: Fri Aug 30 17:45:07 2002
E_GC2210_LCL_ABORT Session failure: Local ABORT condition.
007e4d00 Fri Aug 30 18:16:02 2002
E_DMA412_LGBEGIN_BAD_ID An invalid logging system handle was passed to
LGbegin(). The handle specifies item 126, and there are 0 total
objects in the logging system.
007e4d00 Fri Aug 30 18:16:02 2002
E_CL0F04_LG_BADPARAM Bad input parameter passed to LG routine
007e4d00 Fri Aug 30 18:16:02 2002
E_DM900C_BAD_LOG_BEGIN Error trying to begin a transaction on the
database 007E0002.
007e4d00 Fri Aug 30 18:16:02 2002
E_DM9500_DMXE_BEGIN Error occurred beginning a transaction.
VIETNAM ::[CD\INGRES\8cc , 007e4d00]: Fri Aug 30 18:16:02 2002
E_QE0025_USER_ERROR A user error has occurred.
VIETNAM ::[CD\RMCMD\7d0 , ffffffff]: Fri Aug 30 18:16:02 2002
E_RE000A_DAEMON_UPDATE_FAIL Cannot update the remotecmd table. The SQL
error code was -39100.
VIETNAM ::[CD\RMCMD\7d0 , ffffffff]: Fri Aug 30 18:16:02 2002
E_RE0002_RMCMD_DOWN Visual DBA RMCMD Server Normal Shutdown.
007e4d00 Fri Aug 30 18:16:02 2002
E_CL1036_LK_RELEASE_BAD_PARAM LKrelease() failed due to a lock list id
bad parameter; the input lock list id = 7; the number of lock lists in
the system = 0.
007e4d00 Fri Aug 30 18:16:02 2002
E_CL1003_LK_BADPARAM Bad parameter(s) passed to routine
007e4d00 Fri Aug 30 18:16:02 2002
E_DM901B_BAD_LOCK_RELEASE Error releasing the lock list: 00000007.
~~~~
007e4d00 Fri Aug 30 18:16:02 2002
E_DM901B_BAD_LOCK_RELEASE Error releasing the lock list: 00000007.
007e4d00 Fri Aug 30 18:16:02 2002
E_DM926F_TBL_CACHE_CHANGE Error occurred updating table cache lock.
007e4d00 Fri Aug 30 18:16:02 2002
E_DM9270_RELEASE_TCB Error occurred releasing a TCB.
007e4d00 Fri Aug 30 18:16:02 2002
E_DM9C76_DM2D_CLOSE_TCBERR Error closing Table Control Block at
database close time. The TCB for table (iiindexes, $ingres) of
database iidbdb could not be released : tcb_ref_count 0,
tcb_valid_count 0, tcb_status 0x00000009.
007e4d00 Fri Aug 30 18:16:02 2002
E_DM9270_RELEASE_TCB Error occurred releasing a TCB.
007e4d00 Fri Aug 30 18:16:02 2002
E_DM9267_CLOSE_DB Error occurred closing a database.
VIETNAM ::[CD\INGRES\8cc , 007e4d00]: Fri Aug 30 18:16:02 2002
E_SC010E_DB_DELETE Error deleting database. Name: iidbdb Owner:
$ingres Added Id 013CBF20
VIETNAM ::[CD\INGRES\8cc , 007e4d00]: Fri Aug 30 18:16:02 2002
E_DM003F_DB_OPEN Database is open.
VIETNAM ::[CD\INGRES\8cc , 007e4d00]: Fri Aug 30 18:16:02 2002
E_DM003F_DB_OPEN Database is open.
VIETNAM ::[CD\INGRES\8cc , 007e4d00]: Fri Aug 30 18:16:02 2002
E_SC0122_DB_CLOSE Error closing database. Name: iidbdb Owner: $ingres
VIETNAM ::[CD\INGRES\8cc , 007e4d00]: Fri Aug 30 18:16:02 2002
E_SC010D_DB_LOCATION Database Location Name: $default Physical
Specification: E:\srv\data\ingres\data\default\iidbdb Flags: 00000003
VIETNAM ::[CD\INGRES\8cc , 007e4d00]: Fri Aug 30 18:16:02 2002
E_DM003F_DB_OPEN Database is open.
007e4d00 Fri Aug 30 18:16:02 2002
E_CL1036_LK_RELEASE_BAD_PARAM LKrelease() failed due to a lock list id
bad parameter; the input lock list id = 39; the number of lock lists
in the system = 0.
007e4d00 Fri Aug 30 18:16:02 2002
E_SX1008_BAD_LOCK_RELEASE Error releasing a lock list.
007e4d00 Fri Aug 30 18:16:02 2002
E_SX1007_BAD_SCB_DESTROY Error destroying a SXF session control block.
VIETNAM ::[CD\INGRES\8cc , 007e4d00]: Fri Aug 30 18:16:02 2002
E_SX000E_BAD_SESSION_END Error ending a SXF session.
VIETNAM ::[CD\INGRES\8cc , 007e4d00]: Fri Aug 30 18:16:02 2002
E_DM003F_DB_OPEN Database is open.
007e4d00 Fri Aug 30 18:16:02 2002
E_CL1036_LK_RELEASE_BAD_PARAM LKrelease() failed due to a lock list id
bad parameter; the input lock list id = 7; the number of lock lists in
the system = 0.
007e4d00 Fri Aug 30 18:16:02 2002
E_CL1003_LK_BADPARAM Bad parameter(s) passed to routine
007e4d00 Fri Aug 30 18:16:02 2002
E_CL1036_LK_RELEASE_BAD_PARAM LKrelease() failed due to a lock list id
bad parameter; the input lock list id = 7; the number of lock lists in
the system = 0.
007e4d00 Fri Aug 30 18:16:02 2002
E_CL1003_LK_BADPARAM Bad parameter(s) passed to routine
007e4d00 Fri Aug 30 18:16:02 2002
E_CL1003_LK_BADPARAM Bad parameter(s) passed to routine
007e4d00 Fri Aug 30 18:16:02 2002
E_DM901B_BAD_LOCK_RELEASE Error releasing the lock list: 00000007.
007e4d00 Fri Aug 30 18:16:02 2002
E_DM9266_UNLOCK_CLOSE_DB Error occurred unlocking a database during a
close.
007e4d00 Fri Aug 30 18:16:02 2002
E_DM9267_CLOSE_DB Error occurred closing a database.
VIETNAM ::[CD\INGRES\8cc , 007e4d00]: Fri Aug 30 18:16:02 2002
E_DM0106_ERROR_ENDING_SESSION An error occurred trying to end a
session.
01ccb100 Fri Aug 30 18:23:54 2002
E_CL1030_LK_EXPAND_LIST_FAILED LK failed while trying to allocate more
locks lock lists. There are 0 locks lists, allocated at system startup
time, of which 0 are used.
01ccb100 Fri Aug 30 18:23:54 2002
E_DMA011_LK_NO_LLBS No more lock list blocks are available. It could
be that locking system shared memory has been exhausted, or that the
configured limit (ii.*.rcp.lock.list_limit) has been exceeded.
01ccb100 Fri Aug 30 18:23:54 2002
E_CL1005_LK_NOLOCKS Out of lock resources
01ccb100 Fri Aug 30 18:23:54 2002
E_DM901A_BAD_LOCK_CREATE Error creating a lock list.
01ccb100 Fri Aug 30 18:23:54 2002
E_DM9C07_OUT_OF_LOCKLISTS You have exceeded the maximum number of lock
lists allocated for this installation. Either reduce the number of
sessions in the installation or increase the number of lock lists in
the locking system. Use the lockstat utility to show the current quota
settings in the locking system
VIETNAM ::[CD\INGRES\8cc , 01ccb100]: Fri Aug 30 18:23:54 2002
E_DM004B_LOCK_QUOTA_EXCEEDED Lock quota exceeded.
VIETNAM ::[CD\INGRES\8cc , 01ccb100]: Fri Aug 30 18:23:54 2002
E_SC0123_SESSION_INITIATE Error initiating session.
01ccb100 Fri Aug 30 18:23:55 2002
E_CL1030_LK_EXPAND_LIST_FAILED LK failed while trying to allocate more
locks lock lists. There are 0 locks lists, allocated at system startup
time, of which 0 are used.
01ccb100 Fri Aug 30 18:23:55 2002
E_DMA011_LK_NO_LLBS No more lock list blocks are available. It could
be that locking system shared memory has been exhausted, or that the
configured limit (ii.*.rcp.lock.list_limit) has been exceeded.
01ccb100 Fri Aug 30 18:23:55 2002
E_CL1005_LK_NOLOCKS Out of lock resources
Saurabh Bhatnagar
Microsoft Terminal Services (henceforth referred to as MSTC) replaces
tokens of processes to impersonate any user. This does not work very
well in Ingres' case (and a few other softwares) since dmfrcp assumes
that the owner of the process is the one who is running it (not always
true with MSTC). Hence LGbegin() is not able to grab the logging space
required to operate properly (since it is not the right user
anymore,i.e. not authorized by Windows).
Usually running logstat/lockstat in an MSTC environment would induce
this (ran also by IVM).
Ingres has worked around this MS bug in II 2.6. It works like a charm
but if you have any questions on this, please feel free to email me
directly.
- Saurabh.
David Beeler
It sounds like your saying that this happens when ingres jobs are run
with MTSC.
When I connect to the server with MTSC I am not connecting as the ingres
user or trying to run ingres processes.
I'm connecting as the Administrator. Before the admin account does
anything ingres crashes.
Is this what you would expect to happen with Ingres 2.5 on Win2000 when
MTSC is used?
Thanks
- David
Saurabh Bhatnagar
Please disable ivm and then give it a shot. Basically the problem
shows up when you do a lockstat/logstat. By the time the administrator
does anything, it is too late, the memory is already corrupt/not
allocated.
Let me know how it goes. Please make sure that no one is running IVM..
You can rename the binary to ensure that. Also please let them know
not to run logstat/lockstat unless explicitly asked.
In general, it is not a good idea to run Ingres in an unsupported
environment like this one.
Take care,
Saurabh.
David Beeler <dabe...@21stcentury.net> wrote in message news:<3D7D7616...@21stcentury.net>...