Posts

OMS 13c Port Requirement

  Recently I was working on OEM13c configuration. I was facing problem with which ports need to be open and that unidirectional or bidirectional. So I thought to write blog post on this. While working on OMS configuration and setup, we will come across many ports.  All the list of ports which used in OMS configuration and monitoring setup can be found in portlist.ini file. [oracle@############ ~]$ cat /u01/app/oracle/oemec2/middleware/install/portlist.ini Enterprise Manager Upload Http Port=4889 Managed Server Http Port=7202 Node Manager Http SSL Port=7403 OHS Http Port=9788 Enterprise Manager Upload Http SSL Port=4903 OHS Http SSL Port=9851 BI Publisher Http SSL Port=9803 Oracle Management Agent Port=3872 Enterprise Manager Central Console Http Port=7788 Admin Server Http SSL Port=7102 Managed Server Http SSL Port=7301 BI Publisher Http Port=9701 Enterprise Manager Central Console Http SSL Port=7803 These ports may vary for different OEM versions. Above port list is

Oracle RAC Database QUIESCE Mode

Image
Oracle RAC database quiesce mode is only privileged user can login to database and perform operation. It is restricted mode for DBA operations only. To put RAC database in quiesce mode, use ALTER SYSTEM QUIESCE RESTRICTED Above statement affect all instances in RAC. Database Resource Manager feature must be activated. After all non-DBA session become inactive then database considered as quiesced. The instance from which you put RAC database in quiesce mode, from same instance you have to unquiesce database, using ALTER SYSTEM UNQUIESCE If you have executed ALTER SYSTEM QUIESCE RESTRICTED statement, and oracle database has not finished processing it, then you cannot open database. WE cannot open database if it is already quiesced. ALTER SYSTEM QUIESCE RESTRICTED and ALTER SYSTEM UNQUIESCE statement affect all instances in RAC database. Cold backup cannot be taken when databas

PostgreSQL Data Types - I

Image
The data type defines what type of data can contain a column. PostgreSQL database is very rich in native data types. It supports all data types specified by SQL and you can add new type using CREATE TYPE command. PostgreSQL support data types to store geometric data, XML data and network address data. We can use arrays, hstore and JSON data types to make things more dynamics. In this post we are going to look at inet and point data types in PostgreSQL. INET Data Type: The INET type is used when you want to store IPv4 or IPv6 addresses. It can also store networks by specifying a netmask. If you try to store something that isn't a valid IP address or network, PostgreSQL will throw an error, so you're basically getting data validation for free. There are a variety of methods you can use in your SQL queries to interrogate IP and network addresses further. postgres=# CREATE TABLE addrs (address INET); CREATE TABLE postgres=# INSERT INT

ORACLE Database ADRCI

ADRCI is Automatic Diagnostic Repository Command Interpreter. Its command line tool to manage diagnostic data. Diagnostic data include alert log, trace file, dump, HM report and more. Automatic Diagnostic Repository ADR is file based repository for Oracle database diagnostic data. It stores alert log, core dump, health monitor reports. The same directory structure is used across multiple products of Oracle database like listener, CRS, ASM. ADRCI provide interactive mode, to launch it use adrci command. Make sure Set ORACLE_HOME and PATH variable properly. The relative location from where adrci launched that define behavior of it. If you launch adrci utility from perticular database diagnostic destination then home path set to that database by default. Using show control purge policy can be found. adrci> show control; ADR Home = /oracle/app/oracle/diag/rdbms/testdb/testdb: ************************************************************************* ADRID  SHO

MySQL Database Backup

Hello guys In this post we are going see how to take MySQL database backup and schedule it for daily backup. 1. Create backup user and grant appropriate permissions. CREATE USER 'backup'@'localhost' IDENTIFIED BY 'backup'; GRANT SELECT, SHOW VIEW, RELOAD, REPLICATION CLIENT, EVENT, TRIGGER ON *.* TO 'backup'@'localhost'; GRANT LOCK TABLES ON *.* TO 'backup'@'localhost'; 2. Create .my.cnf file with below content. Create this file in home directory of database owner. Set 600 permission for this file. [mysqldump] user=mysqluser password=secret 3. Copy below files to desired locations. mysql_database_backup.sh   mysql_backup_schedule.sh 4. Make changes to mysql_backup_schedule.sh file /home/mysql/isdba/mysql_database_backup.sh /home/mysql/mysql/bin /home/mysql/database_dumps/dumps db_name >> /home/mysql/database_dumps/logs/db_name.log first parameter to mysql_database_backup.sh is location of mys

PostgreSQL pg_controldata utility

Image
Hello Guys, In this post we are going see a utility provided by PostgreSQL to find information about database cluster.  If we want know information about PostgreSQL cluster like database block size, catalog information,  checkpoint information, WAL segment size, etc. we will use pg_controdata utility. the location of pg_controldata utility will be same as your postgresql installation then bin directory. to execute this utility we have to provide data directory location as parameter. The sample output is attached here. #############################!!! Happy Learning !!!################################

PostgreSQL Database Major Upgrade

Image
Hello Guys... In this post we are going to see PostgreSQL database major upgrade. The earlier version of PostgreSQL is 9.6.5 and we are going to upgrade it to 10.1 Prerequisite: A server with any flavour of UNIX having PostgreSQL 9.6.5 installed. Binaries of PostgreSQL 10.1 Access to special OS user using database is installed. Here we are using postgres user as special OS user. postgres used for below execution. Configuration Details: Old data directory:  /pg_data/pg_data_9.6.5/ New data directory:  /pg_data/pg_data_10.1/ Old installation directory:  /pghome/postgres_9.6.5/ New Installation directory:  /pghome/postgres_10.1/ Upgrade Procedure: backup database cluster. shutdown database cluster. Rename installation directory. It is good practise to rename installation directory instead of delete, if we have any trouble we can revert the changes. Install PostgreSQL 10.1 using source code. I am going to write post for Standard PostgreSQL Database Installation.