Thursday, September 12, 2024

Generate SSH key to setup Git Repo

Generate SSH key to setup Git Repo 


C:\Users\>ssh-keygen -t rsa -b 4096 -C "anurag.pandey@demo.com"

Generating public/private rsa key pair.

Enter file in which to save the key (C:\Users\/.ssh/id_rsa):

Enter passphrase (empty for no passphrase):

Enter same passphrase again:

Your identification has been saved in C:\Users\/.ssh/id_rsa

Your public key has been saved in C:\Users\/.ssh/id_rsa.pub

The key fingerprint is:

SHA256:sqJ1iaDi3R0VmwiFwKDOriahqrBfrRYMpvNERmO0jO4 anurag.pandey@demo.com

The key's randomart image is:

+---[RSA 4096]----+

| o+.. ..         |

|.o+o ..          |

|ooo. .   .       |

|+ =   . . +      |

| O.o  ..S+       |

|*...oo +.        |

|=E  =.=.         |

|Boo+o+. .        |

|Xooo.. .         |

+----[SHA256]-----+


C:\Users\>




copy and add id_rsa.pub to git setting -  Authentication keys



 

Monday, September 9, 2024

Source database providers for DMS Schema Conversion - DMS SCT

Source database  providers for DMS Schema Conversion - DMS SCT



=> DMS Schema Conversion supports the following data providers as sources for your migration projects.


  • Microsoft SQL Server version 2008 R2, 2012, 2014, 2016, 2017, and 2019
  • Oracle version 10.2 and higher, 11g and up to 12.2, 18c, and 19c, and Oracle Data Warehouse
  • PostgreSQL version 9.2 and higher
  • MySQL version 5.5 and higher

Friday, August 16, 2024

How to create oracle database in silent mode using dbca ?

Create oracle database in silent mode using dbca


export ORACLE_SID=POC1


dbca -silent -createDatabase \

 -templateName General_Purpose.dbc \

 -gdbname POC1 -sid POC1 -responseFile NO_VALUE \

 -characterSet AL32UTF8 \

 -enableArchive true -archiveLogMode auto \

 -recoveryAreaDestination /u02/fast_recovery_area \

 -initParams db_unique_name=POC1, db_recovery_file_dest_size=10G, db_create_file_dest='/u02/oradata/', db_create_online_log_de

st_1='/u02/oradata/', db_create_online_log_dest_2='/u02/fast_recovery_area/', dg_broker_start=false \

 -sysPassword Welcome2 \

 -systemPassword Welcome2 \

 -createAsContainerDatabase true \

 -numberOfPDBs 1 \

 -pdbName PDB1 \

 -pdbAdminPassword Welcome2 \

 -databaseType MULTIPURPOSE \

 -memoryMgmtType auto_sga \

 -totalMemory 1000 \

 -storageType FS \

 -datafileDestination "/u02/oradata/" \

 -useOMF true \

 -redoLogFileSize 50 \

 -emConfiguration NONE \

 -sampleSchema true \

 -ignorePreReqs


Monday, August 5, 2024

How to check Postgres Schema size using psql query ?

 


Check Postgres Schema size using psql query



Query1 :


SELECT     pg_catalog.pg_namespace.nspname,

           pg_size_pretty(SUM(pg_relation_size(pg_catalog.pg_class.oid))::BIGINT)

FROM       pg_catalog.pg_class

           INNER JOIN pg_catalog.pg_namespace

           ON         relnamespace = pg_catalog.pg_namespace.oid

GROUP BY   pg_catalog.pg_namespace.nspname;





Query 2 : 



with SchemaSize as

(

select ps.nspname as schema_name,

sum(pg_relation_size(pc.oid)) as total_size

from pg_class pc

join pg_catalog.pg_namespace ps

on ps.oid = pc.relnamespace

group by ps.nspname

)

select ss.schema_name,

pg_size_pretty(ss.total_size)

from SchemaSize ss

order by ss.total_size desc

limit 20;