Speakers Dan Foreman Tom Bascom Congrats said the boss Youre now the DBA After a congratulatory handshake he stops as he heads out of your office Oh by the way since youre the DBA make sure that system stuff doesnt bother me any more Great But n ID: 477197
Download Presentation The PPT/PDF document "1 Title: Congratulations! You're a Pro..." is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
1
Title: Congratulations! You're a Progress DBA! Now What?
Speakers: Dan Foreman, Tom Bascom
“Congrats!” said the boss. “You’re now the DBA.” After a congratulatory handshake, he stops as he heads out of your office. “Oh, by the way… since you’re the DBA, make sure that system stuff doesn’t bother me any more.” Great…. But now what? You know a thing or two about databases, but do you know enough? What do you need to pay attention to? What can you ignore? What should you lose sleep over, and what should make you update your resume? In this session, Dan Foreman and Tom Bascom, two of the nicest people you will ever meet, with more than half a century of Progress experience between them, will show you the way through the challenges that lie in front of you and help bring peace to your weekends and evenings.
Highlights:
• How do I
make
a backup?
•
Starting
and
stopping
a
database
.
•
None
of my SQL
knowledge
works
...
•
After-imaging
, the
dba's
best
friend
!
• About killing users...
• Where are my startup parameters and how do I change them?
o What definitely needs to be changed?
o What should I never touch?
• What can I (safely) ignore? For how long?
• When should I raise the 4-alarm fire alarm?
• Where are the log files?
• Monitoring your database.
• Where can I learn more or get help?
• It's not just a database -- there is code too!Slide2
Congratulations!
You’re Our
New Progress DBA!
Now What?!?
Dan
Foreman,
Bravepoint
danf@bravepoint.com
Tom
Bascom, White Star Software
tom@wss.comSlide3
A Few Words about the Speaker
Dan Foreman – Progress User since 1984
Author of Progress Books: Progress Performance Tuning GuideProgress Database Admin
Guide Progress System Tables GuidePromon
–
debghb
Soon to be released!And Database Admin Tools:ProMonitor/ProCheck/LockMonPro Dump&Load
3Slide4
Audience Survey
How many do at least some Progress DBA work?
How many have been doing that work for less than a year?Is anyone on a version of Progress that is a single digit number…i.e. V9, V8, etc.Who has their cell phone in noisemaking mode?
4Slide5
5
The DocumentationSlide6
The Documentation
Online Manuals:
http://communities.progress.com/pcom/docs/DOC-16074Knowledgebase
: http://knowledgebase.progress.com/
6Slide7
Other Publications
BravePoint
has severalwww.bravepoint.com/products-publications.shtmlWhite Star toowss.com/publications/default.html
7Slide8
8
Starting a DatabaseSlide9
Starting a Database
PROSERVE
DBMANExploder9Slide10
PROSERVE
Pro
Command LineEasy to ScriptLots of Control
RepeatableSequence is guaranteed guaranteedCon
Command Line
Must Provide Details like “
dbname”Dinosaur stigma10$ proserve dbname –n 500 –spin 3149 –B 1000000 –L 50000$
probiw
dbname
$
proaiw
dbname
$
prowdog
dbname
$
proapw
dbnameSlide11
DBMAN
Pro
Command LineWorks with conmgr.properties
Easy to ScriptStarts Writers & WatchdogCon
Command Line
Uses
conmgr.propertiesAdmin Server must be running.Uses Java11$ dbman dbName -startSlide12
Exploder
Pro
Graphical Interface?
ConGraphical InterfaceRequires Admin Server
Requires
conmgr.properties
UglyConfusingIncompleteCan be Unreliable (Java)But if you like that sort of thing…12Slide13
13
Stopping a DatabaseSlide14
Stopping a Database
PROSHUT
DBMANExploder14Slide15
Stopping a Database
PROSHUT
DBMANExploder15
Delete the .
lk
file…
Kill -9
Reboot server…
Trip over plug…Slide16
PROSHUT
Pro
Command LineEasy to ScriptLots of Control
FastCon
What’s a Command Line?
16
$ proshut –by dbnameSlide17
DBMAN
Pro
Command LineWorks with conmgr.properties
Easy to ScriptCon
Command Line
Uses
conmgr.propertiesAdmin Server must be running17$ dbman dbName -stopSlide18
Exploder
Pro
Con
Graphical Interface
Requires Admin Server
Requires
conmgr.propertiesUglyConfusingIncompleteUnreliableEasy to shutdown wrong DB18Slide19
19
How Do I Make a
Backup?Slide20
How Do I Make a Backup?
PROBKUP
OS Backup3rd Party ToolsVM or SAN “snapshots”
20Slide21
PROBKUP
Knows where
all of the parts of the database are (even the parts in memory)Can be executed with the database onlineCan eliminate some empty
space in the dbCan be used to change parts of the DB StructureCan turn on after-imaging online if you forget…
21
$
probkup online dbname dbname.pbk -comSlide22
“All The Parts of the DB”
22
# sports.st#
b /bi/sports.b1#d "Schema Area":6,32;1 /db/sports.d1
d "Info Area":
7,32;1 /db/sports_7.d1
d "Customer/Order Area":8,32;8 /db/sports_8.d1d "Primary Index Area":9,1;8 /db/sports_9.d1d "Customer Index Area":10,1;64 /db2/sports_10.d1d "Order Index Area":11,32;64 /db/sports_11.d1#a /ai/sports.a1a /ai/sports.a2a /ai/
sports.a3
a
/ai/
sports.a4Slide23
OS Backup & 3rd Party Tools
The database must be offline or in a “quiescent state
”You are responsible for making certain of the aboveYou must also ensure that
all parts of the database are included in the backup
23Slide24
VM or SAN “Snapshots”
The snapshot must be a consistent, point in time image of the entire
databaseThe database will be in a crashed state when recoveredNot all snapshot products are created equally!
Progress has tested and certified EMC’s SRDFUsers report success with VMWare’s Vmotion (but beware of possible performance issues
)
24Slide25
Other Stuff to Backup
$DLC/properties
DB Log FilesAdmin Server, AppServer, WebSpeed LogsStructure (.st
) FilesParameter (.pf) Files$DLC/startup.pf
repl.properties
etc.
25Slide26
26
None of My
SQL
Knowledge WorksSlide27
None of My SQL Works!?!
Progress is NOT
SQLPeriod. Full Stop. End of Story.Thinking about Progress like SQL will only lead to pain and agony
27Slide28
SQL-92 Interface
SQLEXP
ODBC/JDBCDBTOOLUPDATE STATISTICSSQLDUMP28Slide29
ODBC/JDBC
29Slide30
DBTOOL
30
$
dbtool
sports
DATABASE TOOLS MENU - 10.2B
------------------------------------------- 1. SQL Width & Date Scan w/Report Option 2. SQL Width Scan w/Fix Option 3. Record Validation 4. Record Version Validation 5. Read or Validate Database Block(s) 6. Record Fixup 7. Schema Validation 9. Enable/Disable File Logging Q. Quit
Choice:
http
://
knowledgebase.progress.com
/articles/Article/P24496Slide31
SQLEXP
Run SQL scripts
GRANT and REVOKE perms (save the scripts because the permissions are not included in a dump & load!)31
$DLC/bin/sqlexp -user userName
-password
passWord
\ -db dnName -S servicePort \ –infile script.sql –outfile
sqlexp.logSlide32
UPDATE STATISTICS
32
/* genUpdateSQL.p
* * mpro
dbName
–p genUpdateSQL.p -param "tmp/updSQLstats.sql" * * sqlexp
-user
userName
-password
passWord
\
* -
db
dnName
-S
servicePort
\
* -
infile
tmp
/
updSQLstats.sql
-
outfile
tmp
/
updSQLtats.log
*/
output to value
("
updSQLstats.sql
"
).
for each _file no-lock where _hidden = no:
put unformatted
"UPDATE TABLE STATISTICS AND INDEX STATISTICS
AND ”
“ALL
COLUMN STATISTICS FOR PUB."
'"' _
file._file
-name '"' ";"
skip
.
put unformatted "commit work;" skip.
e
nd.
output close
.Slide33
33
A
Few Words About “killing”
UsersSlide34
About “killing” Users…
If you are on UNIX:
“kill -9” is dangerous!“kill -9” does not “always work”.“kill -1” should be safe and it should work.proshut
dbname –C disconnect usr#
34Slide35
About “killing” Users…
If you are on UNIX:
“kill -9” is dangerous!“kill -9” does not “always work”.“kill -1” should be safe and it should work.proshut
dbname –C disconnect usr#Windows:We’re sorry.
35Slide36
36
After-Imaging
–
The DBA’s Best FriendSlide37
After-Imaging
Roll-forward
recoveryA journal of transaction “notes” that can be replayed against a baseline backup to restore a database to the last completed transaction or a point in time or a specific transaction numberThis is the same concept that some other databases refer to as the “redo log”
37Slide38
Why do I need after-imaging?
Protection from media loss -- such as bad tapes, a crashed disk, a destroyed data center or stolen servers…Slide39
Why else do I need after-imaging?
Protection from human errors:
Human error is
at least as big a risk as hardware problems
for each customer:
delete customer.
end.$ cd
/db
$
rm
*
for each order:
delivered = yes.
end.
$ vi
dbname.db
…
:xSlide40
After-Imaging Best
Practices #1
Enable after-imaging on all updateable databasesPlace after-image extents on separate disks from data extents
Use 8 to 16 variable extents with “large files” enabledRun an
After Image Writer (AIW)
Switch extents as often as the business needs you
toUse the Internal AI Sequence number when naming archived AI filesUse the AIM (AI Manager)Slide41
After-Imaging Best Practices
#2
Copy archived logs to an external location ASAPVerify your process by continuously rolling forwardMonitor both your “empty” and “full” extents
Keep at least 30+ days of archived after-image logsEstablish a dedicated backup and recovery directory
41Slide42
42
Startup
ParametersSlide43
Startup Parameters
Where to
Find Them?Which ones should be changed?Which ones should be left alone!
43Slide44
Where to Find Them?
On the command
lineIn a scriptIn “.pf” filesIn $DLC/properties/
conmgr.properties Verify by examining the “dbname.lg
” file.
Search for “(333)” and examine the next 50-75 lines…
44Slide45
Tune in Yesterday Morning!
Which ones should be changed?
Which ones should be left alone!Which ones are crucial?Before Image Size Th
reshold (-bithold)
45Slide46
46
Important Configuration OptionsSlide47
Important Configuration Options
BI Cluster Size
Block SizesStorage AreasRows Per Block (RPB)
47Slide48
BI Cluster Size
The Default varies with release, 512KB is
currentFor “Workgroup” Licenses smaller is betterMore, but smaller, delaysFor “Enterprise”
Licenses bigger is betterMay increase crash recovery time a bit
But reduces the risk of painful delays during heavy
processing
32768 KB is “a good start”proutil dbname –C truncate bi –bi 3276848Slide49
Block Sizes
DB Block (Must Dump & Load to Change)
4KB or 8KBNOT 1KB or 2KB BI Block16KBp
routil dbname –C truncate bi –biblocksize 16AI Block
16KB
r
futil dbname –C aimage truncate –ai 16AI must be disabled so do it ‘early’49Slide50
Storage Areas
Type 2
Storage Areas are the foundation for all advanced features of the OpenEdge database
Type 2 areas have Data Cluster Sizes (DCS) of 8, 64 or 512Data blocks in Type 2 areas contain data from just one table
Use
Many
(Type 2) Storage AreasDo NOT assign tables to areas based on “function”Instead group objects by common “technical attributes” (Rows Per Block, size, activity level)Put Large Objects (LOBs) in separate AreasDo NOT
store data, indexes or LOBs in the “Schema Area
”
50Slide51
51Slide52
52
Where Are the Log Files?Slide53
Where are the log files?
dbname.lg
Admin Server: $WRK/admserv.logApp Servers: $WRK/appsrv.broker.log
$WRK/appsrv.server.logLocation of $WRK can be found $DLC/bin/proenvOS Logs
/
var
/log, /usr/adm53Slide54
54
MonitoringSlide55
Monitoring
What to
ignoreWhat to pay attention toWhat to panic over…What not to miss!
55Slide56
What to Ignore
56
(452) Login by root on /dev/pts/6.
(453) Logout by root on /dev/pts/6.(708) Userid is now tom.
(8873) Login
usernum
2547, remote SQL client.(14658) Previous message sent on behalf of user 2542, server pid 22516, broker pid 5778.(12699) Database xyz Options:And a few squillion more “noise” messages… Msg Type Client Type | | Date Time Process
-Id v v Usr#
Msg
# Message
Text
------------------------------------------------------------------------------------------------
[
2012/08/23@09:34:36.572-0400] P-336
T
-1240798976
I
ABL
5: (452)
Login
by tom on /
dev
/
pts
/1.
[
2012/10/24@13:07:54.129-0400] P-11073
T
-1226471168
I
ABL
: (334)
Single
-user session end.Slide57
What to Pay Attention To
57
(2248) Begin normal shutdown (2249) Begin ABNORMAL shutdown(542) Server shutdown started by root on /
dev/pts/6.(5292) SYSTEM ERROR: The broker is exiting unexpectedly, beginning Abnormal Shutdown.(1384) The database is being shutdown.(915) Lock table overflow, increase -L on server
(1081) Too many users requested semaphore undo, increase SEMMNU.
SYSTEM
ERROR: Too many subprocesses, cannot fork. Errno=12.Note: not a comprehensive list or errors but you get the ideaNote2: not all SYSTEM ERRORs are worth getting out of bed forSlide58
What to Pay Attention To
Buffer Cache Hit (or Miss) Ratio
Insanely high DB RequestsBuffers FlushedAI & BI Empty Buffer WaitsSemaphore WaitsLatch TimeoutsRecord Lock Waits
All of these can be found in promon & VSTs
58Slide59
What to Pay Attention To #2
Before Image Size
Long Running Transactions (30-60 minutes)Record Fragmentation (proutil dbanalys or proutil
tabanalys)
59Slide60
What to Panic Over!
60
(37) Your
database was damaged. Dump its data and reload it.(43) Cannot find or open file <filename>, errno = <number>.
(
1124) SYSTEM ERROR: Wrong
dbkey in block. Found 5512, should be 1458 in area 15.(886) The database was last used <date/time>.(887) The before-image file expected <date/time>.(888) Those dates don't match, so you have the wrong copy of one of them.SYSTEM
ERROR
: …Slide61
What Not To Miss
The
lack of these messages means that backups are not executingOr that after-imaging is not functioning
61
(
1362) Full backup started.
(1364) Full backup successfully completed. (7129) Usr 61 set name to Aimage full. (3778) This is after-image file number 270 since the last AIMAGE BEGIN (3777) Switched to ai extent /ai/sports.a4. Slide62
Tools
PROMON
OE ManagementProMonitorProTopBravepoint Managed DBADBAppraise
Roll your own with Virtual System Tables (VSTs)
62Slide63
63
It’s Not “just” a DatabaseSlide64
It’s Not “Just” a Database
Any Amount of Tuning can always be defeated by lousy
code64Slide65
Storage
RAID 5 is EVIL!
So are the variants spawned from it:RAID 6RAID DP (Double Parity or Definitely Putrid)Et al – Parity based RAID provides a Parody of PerformanceNAS <> SANIf possible avoid
NetApp65Slide66
66
Where Can
I Find Help?Slide67
Where Can I Find Help?
PUG Meetings
LocalPUG Challenge:EMEA – November 7 & 8, Brussels, BelgiumAmericas – Westford, MA 2014!!
Progress Software:Documentation: http://communities.progress.com/pcom/docs/DOC-16074
Knowledgebase:
http
://knowledgebase.progress.com“Communities”: http://communities.progress.com/pcom/index.jspaPEG, Progress E-Mail Grouphttp://peg.comProgressTalkhttp://progresstalk.comRefrigerator magnet with
Dan’s
contact info on it
67Slide68
Best Practices
See
Progress DBA Best Practices document on the BravePoint Web Site68Slide69
Thank You
!
69Slide70
Questions?
70
Dan Foreman
danf@prodb.com
dforeman@bravepoint.com
+1 541 908 3437 – not now please