MySQL Firewall Ports

-

Port Requirements for MySQL


3306-3326 TCP/UDP Database Engine

Comments

Post a Comment

Popular posts from this blog

SQL Server on Nutanix - Best pratices

-
The following taken from : Microsoft SQL Server 2016 Nutanix Best Practices Drive configuration: For optimal performance several virtual disks should be used.   Nutanix suggest eight disks per SQL Server virtual machine spread across   4 SCSI controllers as laid out below:   Drive Controller Type Controller # OS LSI SAS 0 SQL Sever installation LSI SAS 0 Backup LSI SAS 0 SQL Datafiles 1 PVSCSI 1 SQL Datafiles 2 PVSCSI 1 TempDB Datafiles 1 PVSCSI 2 TempDB Datafiles 2 PVSCSI 2 TempDB Log Files PVSCSI 3 Database Log Files PVSCSI 3 Cluster size formatting of all drives as below: SQL Data and log files   - 64KB NTFS OS and SQL Server installation - 4KB NTFS - Server Team ?? ...
Read more

ASM Proxy: New Instance Type in Oracle 12c

-
Image
Prior Oracle Database 12c, an ASM instance ran on every node in the cluster and ASM Cluster File System (ACFS) Service on a node connected to the local ASM instance running on the same host to fetch the required metadata. If the ASM instance on a node were to fail, then ACFS file systems could no longer be accessed on that node. With introduction of Flex ASM in Oracle 12c, hard dependency between ASM and its clients has been relaxed and only a smaller number of ASM instances need run on a subset of servers in a cluster. In such a scenario, in order to make ACFS services available on nodes without an ASM instance, a new instance type has been introduced by Flex ASM: the ASM-proxy instance which works on behalf of a real ASM instance. ASM Proxy instance fetches the metadata about ACFS volumes and file systems from an ASM instance and caches it. If ASM instance is not available locally, ASM proxy instance connects to other ASM instances over the network to fetch the me...
Read more

ORA-19698 File is from different database

-
I came across this error during point in time recovery of  500G database . Steps followed to resolve the issue  If the error "ORA-19698: %s is from different database" is seen during an Oracle disaster recovery operation, perform the following: 1. Bring the database to nomount state (Steps mentioned below): At a command prompt, type the following command: SQLplus / as SYSDBA shutdown immediate; startup nomount; 2. Empty the contents of the directory (under the oradata directory) containing the data files and online redo logs of the newly created database. 3. Re-try the control file restore operation.
Read more