"Title: Online Training in IBM DB2 LUW/UDB DBA in Hyderabad (www.etraining.guru)
Dear Students,
Greetings from www.etraining.guru
We provide BEST online training for IBM DB2 LUW/UDB DBA in Hyderabad by a database architect. Our DB2 Trainer comes with a working experience of 11+ years, 9+ years in DB2 and a DB2 certified professional.
DB2 LUW DBA Course Content: http://www.etraining.guru/course/dba/online-training-db2-luw-udb-dba
Course Cost: USD 300 (or) INR 18000
Number of Hours: 30 hours
If there is any opportunity, we will be very happy to serve you. Appreciate if you can explore other training opportunities in our website as well.
We can be reachable at info@etraining.guru (or) 91-996-669-2446 for any further info/details.
Regards,
Karthik
www.etraining.guru"
6. Operating system:
- Red Hat Enterprise Linux (RHEL) 5 Update 2.0.4
- SUSE Linux Enterprise Server (SLES) 10 Service Pack 2
- SUSE Linux Enterprise Server (SLES) 11
- Ubuntu 8.0.4.1
Installation Pre-requisites (Linux!)
Disk space requirements: 500 to 1GB
Memory requirements: Minimum of 512 MB of RAM
Root (vs) Non-root installation
Users/Groups
11. Removes a DB2 instance that was created by db2icrt.
db2idrop - Drop Instance
Syntax:
You can only drop instances that are listed by db2ilist command
Example: db2idrop db2inst1
12. Lists all the instances that are created using the db2icrt command
db2ilist - List Instances
Syntax:
$ db2ilist -h
$ db2ilist
db2inst1
db2inst2
Gets data from /var/db2/global.reg
db2greg -dump
13. Login as the DB2 instance owner
db2start - Start Instance
. $DB2_HOME/db2profile
db2start
14. Login as the DB2 instance owner
db2stop - Stop Instance
Make sure you have all applications disconnected (db2 list applications)
$ db2stop
$ db2stop force (= db2 force application all + db2stop)
$ db2_kill
15. $ db2 get instance
$ db2 ? get dbm cfg
GET DATABASE MANAGER CONFIGURATION [SHOW DETAIL]
$ db2 get dbm cfg
$ db2 get dbm cfg | grep NUMDB
$ db2 update dbm cfg using NUMDB 10
$ db2 attach to db2inst1
$ db2 get dbm cfg show detail
$ db2 reset dbm cfg
DBM CONFIGURATION
18. Priority of DB2 Env/registry variables:
- OS environment set with set/export
- Node instance
- Instance
- Global
To read global profile: db2greg -dump
Detecting DB2 products installed: /usr/local/bin/db2ls *This internally checks global.reg file
SYSIBMADM.REG_VARIABLES admin view:
select substr(REG_VAR_NAME,1,35) NAME, substr(REG_VAR_VALUE,1,35) VALUE,
LEVEL from SYSIBMADM.REG_VARIABLES
REG_LIST_VARIABLES Table function:
SELECT CHAR(REG_VAR_NAME,35) AS REGVAR, CHAR(REG_VAR_VALUE,35) AS
VALUE,LEVEL FROM TABLE(REG_LIST_VARIABLES()) AS REG ORDER BY 3,1
Instance IDs should not be root or have password expired.
DB2DIR: DB2 installed location. You can find this using db2ls command
http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.qb.server.doc/doc/c0050566.html
The instance directory stores all information that pertains to a database instance. You cannot change the location of the instance directory once it is created. The directory contains:
The database manager configuration file (db2systm)
The system database directory
The node directory
The node configuration file (db2nodes.cfg)
Any other files that contain debugging information, such as the exception or register dump or the call stack for the DB2 database processes.
The installation process creates a default DB2 instance, which is defined by the DB2INSTANCE environment variable. However, instances can be created/dropped after installation.
Auto starting Instances: db2iauto -on instance_name
On LUW, an instance created by using db2icrt is set as a manual start.
ps -ef | grep ^db2inst1 | egrep -v "bash|sshd|grep“
reset dbm cfg: Resets the DBM configuration file to its default values
Location of DBM CFG file: ./sqllib/db2systm
Link: https://www.columbia.edu/sec/acis/db2/db2d0/db2d0160.htm
Instance node level profile registry: For partitioned databases
****
To display help information for the command, use:
db2set ?
To list the complete set of all supported registry variables, use:
db2set -lr
To list all currently defined registry variables for this session, use:
db2set
To show the current session value of a registry variable, use:
db2set registry_variable_name
To delete the current session value of a registry variable, use:
db2set registry_variable_name=
To change a registry variable for this session only, use:
db2set registry_variable_name=new_value
To change a registry variable default for all databases in the instance, use:
db2set registry_variable_name=new_value -I instance_name
To change a registry variable default for all instances in the system, use:
db2set registry_variable_name=new_value -g
Note:The two parameters "-I" and "-G" cannot be used at the same time in the same command.
To change a registry variable default for a particular node in an instance, use:
db2set registry_variable_name=new_value -i instance_name node_number
To reset all registry variables for an instance back to the defaults found in the Global Profile Registry, use:
db2set -r registry_variable_name
To reset all registry variables for a node in an instance back to the defaults found in the Global Profile Registry, use:
db2set -r registry_variable_name node_number
***
Instance node level profile registry: For partitioned databases
****
To display help information for the command, use:
db2set ?
To list the complete set of all supported registry variables, use:
db2set -lr
To list all currently defined registry variables for this session, use:
db2set
To show the current session value of a registry variable, use:
db2set registry_variable_name
To delete the current session value of a registry variable, use:
db2set registry_variable_name=
To change a registry variable for this session only, use:
db2set registry_variable_name=new_value
To change a registry variable default for all databases in the instance, use:
db2set registry_variable_name=new_value -I instance_name
To change a registry variable default for all instances in the system, use:
db2set registry_variable_name=new_value -g
Note:The two parameters "-I" and "-G" cannot be used at the same time in the same command.
To change a registry variable default for a particular node in an instance, use:
db2set registry_variable_name=new_value -i instance_name node_number
To reset all registry variables for an instance back to the defaults found in the Global Profile Registry, use:
db2set -r registry_variable_name
To reset all registry variables for a node in an instance back to the defaults found in the Global Profile Registry, use:
db2set -r registry_variable_name node_number
***
%ia: If instance attachment exists, the authid of the current instance attachment; otherwise a null string
%i: Local alias of instance
%da: If database connection exists, the authid. Else, null string
%d: Database aliase
%n: New line character
