| file list installing by package | rpm -ql [package] | dpkg -L [package] | |
| show package which is owner of file | rpm -qf [file] | yum provides [file] | dpkg -S [file] |
| package info | rpm -qi [package] | yum info [package] | dpkg -s [package] |
| package version | rpm -q [package] | dpkg-query -W [package] | |
| packages list | rpm -qa | yum list installed | dpkg –list |
| list available packages (about 15 tys.) | yum list | ||
| dependencies | yum deplist [pakiet] | ||
| file dependencies | rpm -qR [package] | ||
| check packages actualizations | yum check-update yum list updates |
||
| using cache | yum -C | ||
| content check | rpm -qlp [package].rpm | ||
| get rpm package | yumdownloader [package] | ||
| get source package | yumdownloader –source [package] | ||
| unpack | rpm2cpio [package].rpm | cpio -idv | ||
| download only | yum –downloadonly update | ||
| inside package | rpm -qpl [package].rpm |
describe database creation:
rrdtool create base.rrd -s 240 \
DS:DS-NAME:GAUGE | COUNTER | DERIVE | ABSOLUTE:HEARTBEAT:0:U \
RRA:CF:XFF:3:840
-s # step default is 300 sec
DS # DATA SOURCE
DS-NAME # variable name
RRA # ROUND ROBIN ARCHIVE – one archive in database
CF # CONSOLIDATION FUNCTION – MAX | MIN | AVERAGE | LAST
PDP # PRIMARY DATA POINT
XFF # XFILES FACTOR – factor, from 0 to 1 describe how many PDP can be UNKNOWN before record will be write to database as UNKNOWN
example:
rrdtool create base.rrd -s 240 \
DS:input:COUNTER:600:0:U \
RRA:AVERAGE:0.5:3:840
base.rrd #database file
-s 240 #record step in database are set to 240 sec
input #data chain name
COUNTER #counter type
(COUNTER – best for increasing values as network interfaces counters, you take into account that interface network counters is roll back when achieve top value 232 or 2 64 and start from zero value
GAUGE – best for non increasing values)
example of counting data:
value of first probe = 100
value of second probe = 150
value of third probe = 180
for counter type – COUNTER
will be calculate difference 150-100=50 and 180-150=30
then depends on RRA ( AVERAGE, MAX, MIN or LAST),
values will be:
for AVERAGE=(50+30)/2=40,
for MAX=50,
for MIN=30,
for LAST=30
for counter type – GAUGE
will not be calculate difference
then depends on RRA
for AVERAGE= (100+150+180)/3=143,
for MAX=180,
for MIN=100,
for LAST=180
600 #600 sec, between each probe before probe will be marked as UNKNOWN,
0 #minimal value
U #maximal value “U” is UNKNOWN
0.5 #ratio of UNKNOWN probes 0-1, 0.5 means 50%
3 #result of CF function will be get from 3 probes but 50% from them can be UNKNOWN
840 #maximal amount of probes which can be store in database (amount of records), you can not resize database file so it must be set at startup.
let’s calculate how many probes should be store in our database during week:
from previous settings we assume that value is generated from 3 probes which are collected every 240 sec
3*240=720 sec.
so final value will be store in database every 720 sec
720/60=12 min.
means that every value in our html chart will be refresh every 12 min.
3600/720=5 probes per hour
24*3600/720=120 probes per day,
7*24*3600/720=840 probes per week
other:
rrdtool dump [baza.rrd] [plik.xml] #export database to xml file
rrdtool fetch [baza.rrd] AVERAGE -s -6[min | h] #get records from last 6 min | hour.
How to copy binaries to other server:
1. turn off database and all services
2. make backup ORACLE_HOME
in new server:
3. make dir ORACLE_HOME
4. set other system variables
5. put ORACLE_HOME from previous backup
6. set user and group ORACLE_HOME dir
7. remove .ora files from ORACLE_HOME/network/admin
8. run command:
ORACLE_HOME/oui/bin/runInstaller -clone -silent ORACLE_HOME=$ORACLE_HOME ORACLE_HOME_NAME=new_Oracle_home_name
9. run script root.sh
10. try run dbca
podane za Oracle® Database Reference 10g Release 2 (10.2) Part Number B14237-04
Table B-1 Creating the Data Dictionary Scripts
| Script Name | Needed For | Description |
|---|---|---|
|
All databases |
Creates the data dictionary and public synonyms for many of its views Grants |
|
|
All databases |
Runs all scripts required for, or used with PL/SQL |
|
|
Real Application Clusters |
Creates Real Application Clusters data dictionary views |
Table B-2 Creating Additional Data Dictionary Structures
| Script Name | Needed For | Run By | Description |
|---|---|---|---|
|
Performance management |
|
Creates views that can dynamically display lock dependency graphs |
|
|
Exporting data to Oracle7 |
|
Creates the dictionary views needed for the Oracle7 Export utility to export data from the Oracle Database in Oracle7 Export file format |
|
|
Heterogeneous Services |
|
Installs packages for administering heterogeneous services |
|
|
Performance management |
|
Allows I/O to be traced on a table-by-table basis |
|
|
Security |
|
Creates the Oracle Cryptographic Toolkit package |
|
|
Advanced Queuing |
Creates the dictionary objects required for Advanced Queuing |
||
|
Oracle Replication |
|
Runs all SQL scripts for enabling database replication |
|
|
Recovery Manager |
|
Creates recovery manager tables and views (schema) to establish an external recovery catalog for the backup, restore, and recovery functionality provided by the Recovery Manager (RMAN) utility |
|
|
Storage management |
Any user |
Analyzes chained rows in index-organized tables |
|
|
Performance management |
|
Enables DBA to lock PL/SQL packages, SQL statements, and triggers into the shared pool |
|
|
Concurrency control |
|
align="left"> | |
|
Performance monitoring |
|
Respectively start and stop collecting performance tuning statistics |
|
|
Storage management |
Any user |
For use with the Oracle Database. Creates tables for storing the output of the |
|
|
Year 2000 compliance |
Any user |
Provides functions to validate that |
|
|
Metadata management |
Any user |
Creates tables and views that show dependencies between objects |
|
|
Constraints |
Any user |
For use with the Oracle Database. Creates the default table ( |
|
|
PL/SQL |
|
Used primarily for upgrade and downgrade operations. It invalidates all existing PL/SQL modules by altering certain dictionary tables so that subsequent recompilations will occur in the format required by the database. It also reloads the packages |
|
|
PL/SQL |
|
Used to change from 32-bit to 64-bit word size or vice versa. This script recompiles existing PL/SQL modules in the format required by the new database. It first alters some data dictionary tables. Then it reloads the packages |
|
|
Performance monitoring |
|
Displays a lock wait-for graph, in tree structure format |
|
|
Security |
|
Creates PL/SQL functions for default password complexity verification. Sets the default password profile parameters and enables password management features. |
|
|
PL/SQL |
|
Recompiles all existing PL/SQL modules that were previously in an |
|
|
Examples |
|
Creates sample tables, such as |
|
|
Oracle Replication |
Any user |
Copies a snapshot schema from another snapshot site |
|
|
Performance management |
|
Creates the TKPROFER role to allow the TKPROF profiling utility to be run by non-DBA users |
|
|
Partitioned tables |
Any user |
Creates tables required for storing output of |
|
| "r1c1-t6" align="left"> |
Performance management |
Any user |
Creates the table |
Table B-4 Upgrade and Downgrade Scripts
| Script Name | Needed For | Description |
|---|---|---|
|
Downgrading |
Provides a direct downgrade path from the new Oracle Database 10g release |
|
|
Upgrading |
Provides a direct upgrade path to the new Oracle Database 10g release |
|
|
Pre-Upgrade Information |
Analyzes the database to be upgraded, detailing requirements and issues for the upgrade to release 10.2 |
|
|
Post-Upgrade Status |
Displays the component upgrade status after an upgrade to release 10.2 |
Table B-5 Java Scripts
| Script Name | Description |
|---|---|
|
Initializes JServer by installing core Java class libraries and Oracle-specific Java classes |
|
|
Removes all elements of the JServer |
|
|
Installs Java-related packages and classes |
Ostatnie komentarze