[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference orarep::nomahs::dbms

Title:VAX DBMS
Notice:THIS NOTESFILE IS NOT A FORMAL SUPPORT CHANNEL
Moderator:SCARY::CHARLAND
Created:Thu Feb 20 1986
Last Modified:Tue Jun 03 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2642
Total number of notes:11044

2592.0. "inadvertent unbind hangs DBQ" by M5::LSMITH () Wed Jan 29 1997 15:58

Hi,

DBMS V6.1-11, OpenVMS Alpha V6.2

A bind is done from DBQ.  The database is not open, so the 
"DBM-F-DBNOTOPEN, database is not open for access" error is returned.  When 
an inadvertent unbind command is done, the command hangs.  I have duplicated 
the same behavior.  

I did not find anything about this in STARS or BUG.  

On a VAX running DBMS V6.1-1, things behave as expected.  I do not have an
Alpha running V6.1-1 or a VAX running V6.1-11 to test on.  Any ideas?

Please see below.

Thanks,
Lisa

LONGS>show process

29-JAN-1997 10:34:02.42   User: LSMITH           Process ID:   2E0010C1
                          Node: LONGS            Process name: "_TNA424:"

LONGS>dbo/show version
Executing DBO for DEC DBMS V6.1-11
LONGS>dbq
dbq> bind parts
%DBM-F-DBNOTOPEN, database is not open for access
dbq> unbind
LONGS::_TNA424: 10:45:33 DBQ       CPU=00:00:08.36 PF=5640 IO=8553 MEM=312
LONGS::_TNA424: 10:45:34 DBQ       CPU=00:00:08.36 PF=5640 IO=8554 MEM=312
LONGS::_TNA424: 10:45:36 DBQ       CPU=00:00:08.36 PF=5640 IO=8555 MEM=312

LONGS>show system/output=t.t
LONGS>search t.t 2e0010c1
2E0010C1 _TNA424:        LEF      5     8559   0 00:00:08.37      5640    312

Interrupt 

LONGS>

LONGS>show system
OpenVMS V6.2  on node LONGS  29-JAN-1997 10:47:57.89  Uptime  50 10:08:45

LONGS, a AlphaServer 2100 4/200


BLANCA, a VAX 4000-705A
BLANCA>show system
OpenVMS V6.2  on node BLANCA  29-JAN-1997 10:45:07.52  Uptime  122 11:25:06

BLANCA>dbo/show version
Executing DBO for DEC DBMS V6.1-1
BLANCA>dbq
dbq> bind parts
%DBM-F-DBNOTOPEN, database is not open for access
dbq> unbind
%DBM-F-NOSTREAM, no active stream or invalid stream address
dbq> 

T.RTitleUserPersonal
Name
DateLines
2592.1DUCATI::LASTOVICAIs it possible to be totally partial?Wed Jan 29 1997 16:088
>I have duplicated the same behavior.  

	I'd BUG it.

>I do not have an
>Alpha running V6.1-1 or a VAX running V6.1-11 to test on.  Any ideas?

	um, install it?
2592.2Ideas in regards to why the hang occurs?M5::LSMITHWed Jan 29 1997 17:1311
    
    Any ideas in regards to why the hang might occur?  
    
    Although I did not find any hits in the bug db, is it possible that 
    this issue has been worked already?  I didn't find anything in the V7 
    Beta Release Notes from Oct 96 either.
    
    The customer found a VAX running DBMS V6.1-11 to test on.
    
    Thanks,
    Lisa
2592.3VAX DBMS V6.1-11 ACCVIO on unbindM5::LSMITHWed Jan 29 1997 18:47214
    
    
    
    

    The unbind on the VAX gets an accvio.  I have not reproduced this
    in-house.  Please see below.
    
    Thanks,
    Lisa
    
    
    
VAX-11/785
OpenVMS v6.2
DEC DBMS V6.1-11

================================================================================

$ DBO /SHOW SYSTEM

DEC DBMS V6.1-11 on node MHLFSB 29-JAN-1997 10:46:07.12
    - monitor log filename is "SYS$SYSROOT:[SYSEXE]DBMMON.LOG;199"
    - no databases are accessed by this node

================================================================================

$ MC DBQ

dbq> SET NOPIC
dbq> BIND INC$DBS:INCYTE ON STREAM 1
%DBM-F-DBNOTOPEN, database is not open for access
dbq> SET NOVERIFY
dbq> UNBIND
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=0000001F,
PC=0006E57D, PSL=03C00000
-RMS-I-NOMSG, Message number 0001690B
-ECWP-W-NORMAL, normal successful completion

  Improperly handled condition, image exit forced.

	Signal arguments	      Stack contents

	Number = 00000007		 0001788E
	Name   = 0000000C		 00000001
		 00000000		 00000000
		 0000001F		 0020B428
		 0006E57D		 00006828
		 03C00000		 7FFE5E0C
		 0001690B		 001358F1
		 03C00000		 23FC0000
					 7FDEB2DC
					 7FDEB2C0

	Register dump

	R0 = 7FDEB340  R1 = 7FDEB208  R2 = 7FDEB340  R3 = 0020B400
	R4 = 0020B420  R5 = 7FFE5EBC  R6 = 7FFECC62  R7 = 7FFED188
	R8 = 7FFECA48  R9 = 7FFECC50  R10= 7FFED7D4  R11= 7FFE2BDC
	AP = 7FDEB20C  FP = 7FDEB1CC  SP = 7FDEB250  PC = 0001690B
	PSL= 03C00000

================================================================================

$ DBO /DUMP /HEADER  INC$DBS:INCYTE

*------------------------------------------------------------------------------
* DEC DBMS V6.1-11                                      29-JAN-1997 10:46:28.28
*
* Dump of database header 
*     Database: IDEV2:[TEST.P21]INCYTE.ROO;1
*
*------------------------------------------------------------------------------

Database Parameters:
    Root filename is "IDEV2:[TEST.P21]INCYTE.ROO;1"
    Created at 14-FEB-1992 09:12:21.85
    DEC DBMS structure level is 61.0
    Maximum user count is 50
    Maximum node count is 9
    Database open mode is MANUAL
    Database close mode is MANUAL (stored as AUTOMATIC)
    Snapshot mode is DEFERRED
    Statistics are enabled
    Buffers...
      - Default user buffer count is 25
      - Default recovery buffer count is 25 (stored as 10)
      - Global buffers are disabled
          Global buffer count is 500
          Maximum global buffer count per user is 30
      - Buffer size is 12 blocks
      - Asynchronous pre-fetch is enabled
          Maximum pre-fetch depth is 7 buffers
      - Asynchronous batch-write is enabled
          Clean buffer count is 5
          Maximum batch size is 5 buffers
      - Optimized page transfer is disabled
    Locking...
      - Adjustable record locking is enabled
          Fanout factor 1 is 10 (10 pages)
          Fanout factor 2 is 10 (100 pages)
          Fanout factor 3 is 10 (1000 pages)
      - Carry-over lock optimization is enabled
      - Lock tree partitioning is disabled
    RUJ Journaling...
      - No default recovery-unit journal filename
    AIJ Journaling...
      - After-image journaling is disabled
      - Database is configured for 2 journals
      - Reserved journal count is 2
      - Available journal count is 0
      - 2 journals can be created while database is active
      - Shutdown time is 60 minutes
      - Backup server (spooler) is disabled
      - Log server startup is MANUAL
      - Operator notification is disabled
      - Journal overwrite is disabled
      - AIJ cache on "electronic disk" is disabled
      - Default journal allocation is 512 blocks
      - Default journal extension is 512 blocks
      - Default journal initialization is 512 blocks
      - Current roll-forward sequence number is 10
      - Current backup sequence number is 10
    Fast Commit...
      - Fast commit is disabled
      - No checkpointing AIJ interval is specified
      - No checkpointing time interval is specified
      - Commit to AIJ optimization is disabled
      - Transaction interval is 256
    Security Auditing...
      - Security auditing is disabled
      - Security alarm is disabled
      - No audit journal filename is specified
      - No alarm name is specified
      - Synchronous audit record flushing is disabled
      - Audit every access
    Database Backup...
      - Fast incremental backup is enabled
    Derived Data...
      - Global section size
          With global buffers disabled is 113554 bytes
          With global buffers enabled is 3639720 bytes
    Database Recovery...
      - Database is consistent but has been modified
      - Full AIJ roll-forward is no longer possible
          By-Area and By-Page AIJ roll-forward is permitted
      - Next AIJ sequence number expected is 10
      - Last commit transaction TSN is 111108
    Release retrieval locks when no longer needed
    Wait on record lock conflicts
    Latest full backup file is dated 14-OCT-1996 16:47:57.54
    Latest full backup transaction sequence number is 84880
    Latest incremental backup transaction sequence number is 106768
    Database has never been incrementally restored
    Latest full restore occurred at 21-AUG-1996 11:07:49.57
    Latest full verify occurred at 14-JUN-1995 15:10:09.40
    Database has been altered 2 times
    Most recent alteration occurred at 27-MAY-1994 14:24:31.89
    Database has never been restructured
    Database was converted on 13-JUN-1995 14:26:19.02
    Database conversion has been commited

                   .
                   . Area and snapshot declarations removed
                   .

No active users

Dump of Corrupt Page Table:

Corrupt page table is empty.


Schema name is INCYTE
    CDD path name is SYS$COMMON:[CDDPLUS]P21
    Version number is  3-DEC-1985 12:46:33.80 (8)
    Object size is 230 blocks

Storage schema name is INCSTOR
    Version number is  3-DEC-1985 13:36:41.35 (8)
    Object size is 221 blocks

Security schema name is SNAP_ONLY
    Version number is 30-MAR-1988 08:46:39.83 (8)
    Object size is 169 blocks

Security schema name is DEFAULT_SECURITY_SCHEMA
    Version number is  3-DEC-1985 13:19:03.93 (8)
    Object size is 169 blocks

Subschema name is MENU_SUBSCHEMA
    Version number is 27-APR-1994 10:04:30.97
    Object size is 16 blocks

Subschema name is TRACKX_SUBSCHEMA
    Version number is 16-MAY-1994 11:12:49.33
    Object size is 136 blocks

Subschema name is DEFAULT_SUBSCHEMA
    Version number is 16-MAY-1994 10:17:06.78
    Object size is 200 blocks

Subschema name is MAIL_SUBSCHEMA
    Version number is  4-DEC-1985 09:35:34.58
    Object size is 6 blocks

Subschema name is FORT_SUBSCHEMA
    Version number is  8-NOV-1988 22:07:45.97
    Object size is 77 blocks

Subschema name is EVENT_SUBSCHEMA
    Version number is  4-DEC-1985 09:32:32.40
    Object size is 7 blocks
    
2592.4Same behavior on DBMS T7.0-08 - AlphaM5::LSMITHWed Jan 29 1997 18:5424
    
Hi,
    
Same behavior on DBMS T7.0-08 on OpenVMS Alpha V6.2  Please see below.
Thanks,
    Lisa
    
    
ELBERT, a AlphaStation 200 4/233
OpenVMS V6.2  on node ELBERT  28-JAN-1997 22:52:32.69  Uptime  49 22:19:20

ELBERT>dbo/show version
Executing DBO for Oracle CODASYL DBMS T7.0-08

ELBERT>dbq
dbq> bind DISK$USR1:[LSMITH.PARTS70]parts
%DBM-F-DBNOTOPEN, database is not open for access
dbq> unbind
ELBERT::LSMITH 22:53:46 DBQ70     CPU=00:00:26.00 PF=19039 IO=10378 MEM=334
ELBERT::LSMITH 22:53:54 DBQ70     CPU=00:00:26.00 PF=19039 IO=10379 MEM=334
ELBERT::LSMITH 22:53:59 DBQ70     CPU=00:00:26.00 PF=19039 IO=10380 MEM=334
ELBERT::LSMITH 22:54:22 DBQ70     CPU=00:00:26.00 PF=19039 IO=10381 MEM=334

    
2592.5hotrdb.us.oracle.com::LASTOVICAIs it possible to be totally partial?Wed Jan 29 1997 19:182
    it's a bug.  BUG it please!
    
2592.6BUG# 445601M5::LSMITHWed Jan 29 1997 21:575
    
    BUG# 445601 filed.
    
    Thanks