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

Conference orarep::nomahs::rdb_60

Title:Oracle Rdb - Still a strategic database for DEC on Alpha AXP!
Notice:RDB_60 is archived, please use RDB_70..
Moderator:NOVA::SMITHISON
Created:Fri Mar 18 1994
Last Modified:Thu May 29 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:5118
Total number of notes:28246

5063.0. "a empty bugchkdump" by ORAREP::TKOV60::OOKUBO () Sat Feb 22 1997 03:06

   I have a problem that my customer's application sometimes fail 
   with a RDSBUGCHK.DMP. ( Rdb V6.0A and some ECO )

   But the dump is empty. There is just the first line (====).

   Whenever a empty dump is created , the process on the customer's 
   application terminat with ACCVIO. 

   Of course, Diskquota is enough. Write access is OK.

   I tried to get a process dump. I entered the command 
   "$ set process/dump " on their application.
   But a process dump wasn't created. 

   Does anyone know anything about this ? 
   Are there any way to trace this problem ? 

   Regards. 

   - ookubo
T.RTitleUserPersonal
Name		DateLines
5063.1M5::LWILCOXChocolate in January!!Mon Feb 24 1997 09:148
                  <<< Note 5063.0 by ORAREP::TKOV60::OOKUBO >>>
                            -< a empty bugchkdump >-

You might want to try using the RDM$BUGCHECK_DIR logical to redirect the
bugcheck dump file (or is it RDMS? I've forgotten).  You might also want
to look in the monitor log file for the bugcheck dump, and you might
look for a KOD$TT. file that might tell you where it really placed the
bugcheck dump.  These might help you get more info, or they might not.
5063.2Works great from 6.0 and up...BOUVS::OAKEYI&#039;ll take Clueless for $500, AlexMon Feb 24 1997 11:4112
~~           <<< Note 5063.1 by M5::LWILCOX "Chocolate in January!!" >>>

~~You might want to try using the RDM$BUGCHECK_DIR logical to redirect the
~~bugcheck dump file (or is it RDMS? I've forgotten).  You might also want

An easy trick when you've forgotten is to 

	RMU/SHOW STATISTICS your_favorite_database

and check Process Information|Defined Logicals|F(ull) which will show you 
all logicals, defined or not.
5063.3a dump is created, but..ORAREP::TKOV60::OOKUBOTue Feb 25 1997 11:0421
>                  <<< Note 5063.0 by ORAREP::TKOV60::OOKUBO >>>
>                            -< a empty bugchkdump >-
>
>You might want to try using the RDM$BUGCHECK_DIR logical to redirect the
>bugcheck dump file (or is it RDMS? I've forgotten).  You might also want

  I used RDM$BUGCHECK_DIR.  A dump file was created on that 
  directory. But that dump file had only one line , the row of "=".


  The process created RDSBUGCHK.DMP. After 2 seconds,  that process
  was terminated by ACCVIO.
  Does it mean that the process terminated before it write dump information
  on the dump file ?  So the proces only  can create a file ?

  I have no idea why bug check dump is created and the process terminate, 
  where it happen in customer's application program.

  How can I find the cause ?

/ookubo
5063.4HOTRDB::PMEADPaul, [email protected], 719-577-8032Tue Feb 25 1997 12:006
    If the dumper fails that soon that it is likely that your process has
    suffered massive memory corruption and none of Rdb's subsystems will be
    able to operate enough to even write the bugcheck.  
    
    You will probably need to come up with a reproducible case that we can
    try on our test systems.
5063.5NOVA::BRYDENTue Feb 25 1997 15:455
        IIs there any information in the monitor log to explain why the
        original process abnormally terminated? Are any other processes
        affected by this failure? Is the monitor ok?
        
        Dave
5063.6some information abount this problemORAREP::TKOV60::OOKUBOThu Mar 06 1997 06:56301
  I collected some information about this problem.
  Can I get useful information from these ?
  Are ther any other log I should check ? 

  Especially, I wonder why process dump is not created. 
  If it's created , I can trace where this problem happen. 
  This is a serious problem.
  
  Please give some advice. 

							ookubo

(1) accounting information of the terminated process. 

SUBPROCESS Process Termination
------------------------------

Username:          CTM_OPRRUN        UIC:               [CTOM,CTM_OPRRUN]
Account:           CTOM              Finish time:        3-FEB-1997 11:25:02.31
Process ID:        2045FC6A          Start time:         3-FEB-1997 11:24:35.93
Owner ID:          20460468          Elapsed time:                0 00:00:26.38
Terminal name:                       Processor time:              0 00:00:04.75
Remote node addr:                    Priority:          4
Remote node name:                    Privilege <31-00>: 1014C108
Remote ID:                           Privilege <63-32>: 00000008
Queue entry:                         Final status code: 0000000C
Queue name:
Job name:
Final status text: %SYSTEM-F-ACCVIO, access violation, reason mask=!XB, virtual

Page faults:             3849        Direct IO:               1303
Page fault reads:         250        Buffered IO:              961
Peak working set:       14560        Volumes mounted:            0
Peak page file:         77968        Images executed:           19

(2) error message  from the terminated process

%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=0000000C,
 						 PC=00000012, PS=00000003

(3) dump file 

Directory $1$DUA62:[RDBLOG]

RDSBUGCHK.DMP;3       3-FEB-1997 11:25:00.84


Contents of this dump file are 1 line like this.
    "==================================================================="


(4) rdmmon.log   


 3-FEB-1997 11:25:00.01 - received user image termination from 2045FC6A:27

 3-FEB-1997 11:25:00.05 - received user attach request from 2045FC6A:28
  - process name CTM_OPRRUN_2, user CTM_OPRRUN  
  - for database "DSA4:[CTM_01.DATABASE.MASTER]CTM1$DBF_MASTER.RDB;1" [_DSA4] (32,3,0)
  - 20 global buffers allocated to user, 3100 free out of 3500
  - sending normal user attach reply to 2045FC6A:28

 3-FEB-1997 11:25:00.24 - received user attach request from 2045FC6A:29
  - process name CTM_OPRRUN_2, user CTM_OPRRUN  
  - for database "DSA4:[CTM_01.DATABASE.FLIST]CTM1$DBF_FLIST.RDB;260" [_DSA4] (48,28,0)
  - sending normal user attach reply to 2045FC6A:29

 3-FEB-1997 11:25:00.41 - received user attach request from 2045FC6A:30
  - process name CTM_OPRRUN_2, user CTM_OPRRUN  
  - for database "DSA4:[CTM_01.DATABASE.CLIST]CTM1$DBF_CLIST.RDB;1" [_DSA4] (22,5,0)
  - sending normal user attach reply to 2045FC6A:30

 3-FEB-1997 11:25:00.60 - received user attach request from 2045FC6A:31
  - process name CTM_OPRRUN_2, user CTM_OPRRUN  
  - for database "DSA4:[CTM_01.DATABASE.SYSTEM]CTM1$DBF_SYSTEM.RDB;1" [_DSA4] (25,4,0)
  - sending normal user attach reply to 2045FC6A:31

 3-FEB-1997 11:25:00.65 - received user attach request from 2045E426:2763
  - process name CTM1$DBS_2072_R, user CTM_OPRRUN  
  - for database "DSA4:[CTM_01.DATABASE.FLIST]CTM1$DBF_FLIST.RDB;260" [_DSA4] (48,28,0)
  - sending normal user attach reply to 2045E426:2763

 3-FEB-1997 11:25:00.77 - received user attach request from 2045E426:2764
  - process name CTM1$DBS_2072_R, user CTM_OPRRUN  
  - for database "DSA4:[CTM_01.DATABASE.CLIST]CTM1$DBF_CLIST.RDB;1" [_DSA4] (22,5,0)
  - sending normal user attach reply to 2045E426:2764

 3-FEB-1997 11:25:00.87 - received user attach request from 2045E426:2765
  - process name CTM1$DBS_2072_R, user CTM_OPRRUN  
  - for database "DSA4:[CTM_01.DATABASE.MASTER]CTM1$DBF_MASTER.RDB;1" [_DSA4] (32,3,0)
  - 20 global buffers allocated to user, 3080 free out of 3500
  - sending normal user attach reply to 2045E426:2765

 3-FEB-1997 11:25:00.96 - received user image termination from 2045FC6A:31
  - abnormal user termination detected
  - database monitor created recovery process RDM_RB_1 (20461C6B)
  - user termination suspended until recovery ready

 3-FEB-1997 11:25:00.96 - received user image termination from 2045FC6A:30
  - abnormal user termination detected
  - database monitor created recovery process RDM_RB_2 (20460C6C)
  - user termination suspended until recovery ready

 3-FEB-1997 11:25:00.97 - received user image termination from 2045FC6A:29
  - abnormal user termination detected
  - database monitor created recovery process RDM_RB_3 (20461C6D)
  - user termination suspended until recovery ready

 3-FEB-1997 11:25:00.97 - received user image termination from 2045FC6A:28
  - abnormal user termination detected
  - database monitor created recovery process RDM_RB_4 (20461C6E)
  - user termination suspended until recovery ready

 3-FEB-1997 11:25:01.82 - received recovery attach from 20461C6D:1
  - process name RDM_RB_3, user SYSTEM      
  - sending normal recovery attach reply to 20461C6D:1

 3-FEB-1997 11:25:01.83 - received recovery attach from 20460C6C:1
  - process name RDM_RB_2, user SYSTEM      
  - sending normal recovery attach reply to 20460C6C:1

 3-FEB-1997 11:25:01.84 - received recovery attach from 20461C6E:1
  - process name RDM_RB_4, user SYSTEM      
  - user freed 20 global buffers, 3100 free out of 3500
  - 20 global buffers allocated to recovery process, 3080 free out of 3500
  - sending normal recovery attach reply to 20461C6E:1

 3-FEB-1997 11:25:01.85 - received recovery attach from 20461C6B:1
  - process name RDM_RB_1, user SYSTEM      
  - sending normal recovery attach reply to 20461C6B:1

 3-FEB-1997 11:25:01.90 - received recovery ready from 20461C6D:1
  - process name RDM_RB_3, user SYSTEM      
  - sending normal recovery ready reply to 20461C6D:1

 3-FEB-1997 11:25:01.91 - received recovery ready from 20460C6C:1
  - process name RDM_RB_2, user SYSTEM      
  - sending normal recovery ready reply to 20460C6C:1

 3-FEB-1997 11:25:01.91 - received recovery ready from 20461C6E:1
  - process name RDM_RB_4, user SYSTEM      
  - sending normal recovery ready reply to 20461C6E:1

 3-FEB-1997 11:25:01.92 - received recovery ready from 20461C6B:1
  - process name RDM_RB_1, user SYSTEM      
  - sending normal recovery ready reply to 20461C6B:1

 3-FEB-1997 11:25:02.09 - received recovery status from 20461C6D:1
  - process name RDM_RB_3, user SYSTEM      
  - Dead process transaction 0 was not active

 3-FEB-1997 11:25:02.11 - received recovery status from 20461C6B:1
  - process name RDM_RB_1, user SYSTEM      
  - Dead process transaction 0 was not active

 3-FEB-1997 11:25:02.12 - received recovery status from 20461C6E:1
  - process name RDM_RB_4, user SYSTEM      
  - Dead process transaction 0 was not active

 3-FEB-1997 11:25:02.12 - received recovery status from 20460C6C:1
  - process name RDM_RB_2, user SYSTEM      
  - Dead process transaction 0 was not active

 3-FEB-1997 11:25:02.20 - received recovery image termination from 20461C6D:1
  - recovery was successful

 3-FEB-1997 11:25:02.22 - received recovery image termination from 20460C6C:1
  - recovery was successful

 3-FEB-1997 11:25:02.22 - received recovery image termination from 20461C6B:1
  - recovery was successful

 3-FEB-1997 11:25:02.24 - received recovery image termination from 20461C6E:1
  - user freed 20 global buffers, 3100 free out of 3500
  - recovery was successful

 3-FEB-1997 11:25:02.24 - received recovery process termination from 20461C6D:1
  - recovery was successful

 3-FEB-1997 11:25:02.26 - received recovery process termination from 20460C6C:1
  - recovery was successful

 3-FEB-1997 11:25:02.27 - received recovery process termination from 20461C6B:1
  - recovery was successful

 3-FEB-1997 11:25:02.28 - received recovery process termination from 20461C6E:1
  - recovery was successful

 3-FEB-1997 11:25:02.37 - received user attach request from 2045E426:2766
  - process name CTM1$DBS_2072_R, user CTM_OPRRUN  
  - for database "DSA5:[CTM_01.DATABASE.SHUUYOU]CTM1$DBF_SHUUYOU.RDB;259" [_DSA5] (26157,1,0)
  - sending normal user attach reply to 2045E426:2766

 3-FEB-1997 11:25:02.60 - received user attach request from 2045E426:2767
  - process name CTM1$DBS_2072_R, user CTM_OPRRUN  
  - for database "DSA4:[CTM_01.DATABASE.KOSHOU]CTM1$DBF_KOSHOU.RDB;1" [_DSA4] (28,4,0)
  - sending normal user attach reply to 2045E426:2767

 3-FEB-1997 11:25:20.54 - received user image termination from 2045E028:5773

 3-FEB-1997 11:25:20.57 - received user image termination from 2045E028:5774

 3-FEB-1997 11:25:20.62 - received user image termination from 2045E028:5775
  - user freed 20 global buffers, 3120 free out of 3500

 3-FEB-1997 11:25:21.01 - received user image termination from 2045E028:5776

 3-FEB-1997 11:25:21.17 - received user image termination from 2045E028:5777

 3-FEB-1997 11:25:21.22 - received user image termination from 2045E028:5778

 3-FEB-1997 11:25:21.31 - received user attach request from 2045E028:5779
  - process name CTM1$DBS_2056_R, user CTM_OPRRUN  
  - for database "DSA4:[CTM_01.DATABASE.FLIST]CTM1$DBF_FLIST.RDB;260" [_DSA4] (48,28,0)
  - sending normal user attach reply to 2045E028:5779

 3-FEB-1997 11:25:21.50 - received user attach request from 2045E028:5780
  - process name CTM1$DBS_2056_R, user CTM_OPRRUN  
  - for database "DSA4:[CTM_01.DATABASE.CLIST]CTM1$DBF_CLIST.RDB;1" [_DSA4] (22,5,0)
  - sending normal user attach reply to 2045E028:5780

 3-FEB-1997 11:25:21.72 - received user attach request from 2045E028:5781
  - process name CTM1$DBS_2056_R, user CTM_OPRRUN  
  - for database "DSA4:[CTM_01.DATABASE.MASTER]CTM1$DBF_MASTER.RDB;1" [_DSA4] (32,3,0)
  - 20 global buffers allocated to user, 3100 free out of 3500
  - sending normal user attach reply to 2045E028:5781

 3-FEB-1997 11:25:21.85 - received user attach request from 2045E028:5782
  - process name CTM1$DBS_2056_R, user CTM_OPRRUN  
  - for database "DSA4:[CTM_01.DATABASE.KOSHOU]CTM1$DBF_KOSHOU.RDB;1" [_DSA4] (28,4,0)
  - sending normal user attach reply to 2045E028:5782

 3-FEB-1997 11:25:22.12 - received user attach request from 2045E028:5783
  - process name CTM1$DBS_2056_R, user CTM_OPRRUN  
  - for database "DSA4:[CTM_01.DATABASE.SYSTEM]CTM1$DBF_SYSTEM.RDB;1" [_DSA4] (25,4,0)
  - sending normal user attach reply to 2045E028:5783

 3-FEB-1997 11:25:22.34 - received user attach request from 2045E028:5784
  - process name CTM1$DBS_2056_R, user CTM_OPRRUN  
  - for database "DSA5:[CTM_01.DATABASE.SHUUYOU]CTM1$DBF_SHUUYOU.RDB;259" [_DSA5] (26157,1,0)
  - sending normal user attach reply to 2045E028:5784

 3-FEB-1997 11:25:22.68 - received user image termination from 2045E028:5779

 3-FEB-1997 11:25:22.71 - received user image termination from 2045E028:5780

 3-FEB-1997 11:25:22.76 - received user image termination from 2045E028:5781
  - user freed 20 global buffers, 3120 free out of 3500

 3-FEB-1997 11:25:22.79 - received user image termination from 2045E028:5782

 3-FEB-1997 11:25:22.82 - received user image termination from 2045E028:5783

 3-FEB-1997 11:25:22.88 - received user image termination from 2045E028:5784

 3-FEB-1997 11:25:23.05 - received user attach request from 2045E028:5785
  - process name CTM1$DBS_2056_R, user CTM_OPRRUN  
  - for database "DSA4:[CTM_01.DATABASE.FLIST]CTM1$DBF_FLIST.RDB;260" [_DSA4] (48,28,0)
  - sending normal user attach reply to 2045E028:5785

 3-FEB-1997 11:25:23.19 - received user attach request from 2045E028:5786
  - process name CTM1$DBS_2056_R, user CTM_OPRRUN  
  - for database "DSA4:[CTM_01.DATABASE.CLIST]CTM1$DBF_CLIST.RDB;1" [_DSA4] (22,5,0)
  - sending normal user attach reply to 2045E028:5786

 3-FEB-1997 11:25:23.29 - received user attach request from 2045E028:5787
  - process name CTM1$DBS_2056_R, user CTM_OPRRUN  
  - for database "DSA4:[CTM_01.DATABASE.MASTER]CTM1$DBF_MASTER.RDB;1" [_DSA4] (32,3,0)
  - 20 global buffers allocated to user, 3100 free out of 3500
  - sending normal user attach reply to 2045E028:5787

 3-FEB-1997 11:25:23.41 - received user attach request from 2045E028:5788
  - process name CTM1$DBS_2056_R, user CTM_OPRRUN  
  - for database "DSA4:[CTM_01.DATABASE.KOSHOU]CTM1$DBF_KOSHOU.RDB;1" [_DSA4] (28,4,0)
  - sending normal user attach reply to 2045E028:5788

 3-FEB-1997 11:25:23.50 - received user attach request from 2045E028:5789
  - process name CTM1$DBS_2056_R, user CTM_OPRRUN  
  - for database "DSA4:[CTM_01.DATABASE.SYSTEM]CTM1$DBF_SYSTEM.RDB;1" [_DSA4] (25,4,0)
  - sending normal user attach reply to 2045E028:5789

 3-FEB-1997 11:25:23.59 - received user attach request from 2045E028:5790
  - process name CTM1$DBS_2056_R, user CTM_OPRRUN  
  - for database "DSA5:[CTM_01.DATABASE.SHUUYOU]CTM1$DBF_SHUUYOU.RDB;259" [_DSA5] (26157,1,0)
  - sending normal user attach reply to 2045E028:5790

 3-FEB-1997 11:25:23.77 - received user image termination from 2045E028:5785

 3-FEB-1997 11:25:23.80 - received user image termination from 2045E028:5786

 3-FEB-1997 11:25:23.85 - received user image termination from 2045E028:5787
  - user freed 20 global buffers, 3120 free out of 3500

 3-FEB-1997 11:25:23.88 - received user image termination from 2045E028:5788

 3-FEB-1997 11:25:23.91 - received user image termination from 2045E028:5789

 3-FEB-1997 11:25:23.97 - received user image termination from 2045E028:5790

 3-FEB-1997 11:25:40.63 - received user image termination from 2045E426:2763
5063.7HOTRDB::PMEADPaul, [email protected], 719-577-8032Thu Mar 06 1997 09:254
    I can't really help you much with the problem, but after looking at
    that monitor log I can't help but be curious about one thing.  Why is
    this application continually detaching and re-attaching to the
    database.  Why don't they just stay attached?
5063.8ORAREP::TKOV60::OOKUBOFri Mar 07 1997 00:438
>    that monitor log I can't help but be curious about one thing.  Why is
>    this application continually detaching and re-attaching to the
>    database.  Why don't they just stay attached?

This application process execute some image. Each image attach and 
detach the database. 

/ookubo