R
Rob Fitzpatrick
Guest
Just an FYI for people out there running 11.6.3, I found a bug that TS says is new in 11.6.3 and is also in 11.7.0. I found it when running a promon script but I am also able to reproduce it running interactively. It causes promon to crash with error 49 (memory violation). The promon session holds a lock on the MTX latch when it crashes, so the database shuts down abnormally. I haven't narrowed down exactly the minimum steps for recreating the crash but I have a script that does it reliably. The content of the script (with annotations) is below. m Modify defaults 1 page size 9999 q 1 User control 1 all users q 4 Record locking table 1 all users q 5 Activity q 6 Shared resources q 7 Database status q R&D debghb 5 Adjust monitor options 1 Display page length 9999 6 Number of auto repeats 3 t Main menu 1 Status displays 4 Processes/clients 2 Blocked clients p 3 Active transactions p p 9 BI log p 10 AI log p 12 Startup parameters p 13 Shared resources p 14 Shared memory segments p 17 Servers by broker t Main menu 2 Activity displays 3 Buffer cache p 5 BI log p 6 AI log p 10 Space allocation p 13 Other t Main menu 3 Other displays 1 Performance indicators p 4 Checkpoints t Main menu 6 Hidden menu 8 Resource queues p 11 Latch counts x Exit You would have to remove the annotations to have a functioning script for promon stdin. I showed them here for clarity. Workaround: if "debghb" is moved from its location above to the latest point possible, i.e. between "t" and "6", six lines from the bottom, then promon does not crash and the DB does not shut down. I hope that makes sense. For those who are interested, I will post an update here when the 11.6.3 hotfix is available.
Continue reading...
Continue reading...