docs.infura.io/infura/networks/ipfs
Wednesday, November 2, 2022
Wednesday, April 27, 2022
Postgres 14 MacOS App 2.5.6
https://www.postgresql.org/download/macosx/
https://postgresapp.com/
sudo mkdir -p /etc/paths.d &&
echo /Applications/Postgres.app/Contents/Versions/latest/bin | sudo tee /etc/paths.d/postgresapp
PostgreSQL with these default settings:
| Host | localhost |
| Port | 5432 |
| User | your system user name |
| Database | same as user |
| Password | none |
| Connection URL | postgresql://localhost |
To connect with psql, double click a database. To connect directly from the command line, type psql. If you’d rather
SELECT datname FROM pg_database;
CREATE DATABASE hcyc;
\c hcyc
psql -U myuser -d mydb -a -f data.sql -W mypassword
To connect PostgreSQL to Hazelcast, you can use a middleware or a plugin which acts as a bridge between the two systems. There are several third-party libraries and tools available that can help you connect PostgreSQL and Hazelcast, such as:
Hazelcast IMDG Connectors: Hazelcast provides connectors that allow you to connect to various data sources including PostgreSQL. The connectors can be used to replicate data between PostgreSQL and Hazelcast, or to use Hazelcast as a caching layer for PostgreSQL.
JPA-Hazelcast: This is an open-source library that provides an implementation of the Java Persistence API (JPA) for Hazelcast. You can use it to map PostgreSQL tables to Hazelcast data structures, allowing you to query and manipulate data in both systems using JPA.
HA-JDBC: This is a JDBC driver that provides load balancing and failover for a variety of database systems including PostgreSQL. You can use it in conjunction with Hazelcast to provide high availability for PostgreSQL.
Friday, February 5, 2021
Tuesday, January 5, 2021
Oracle19c LogMiner
ORA-01325 archive log must be enabled
archive log - copy of redo log
delete of data
suspend archive on datapump
CL SCR
automatic log file slecction by specifying time frame timestamps
sqlplus -s
SET LINESIZE 200;
alter session sset nlf_date_format = 'DD-MON-YYYY HH24:MI:SS';
ALTER DATATBASE ADD SUPPLEMENTAL LOG DATA;
select supppliemental)log_data)min from V$DATABASE;
EXECUTE DBMS_LOGMNR.ADD_LOGFILE( -
LOGFILENAME => 'PATH/fast_recovery_area/LGDB/archivelog/DATA/*.arc'. -
options => DBMS_LOGMNR.NEW);>>
EXECUTE DBMS_LOGMNR.ADD_LOGFILE( 'path/redo1.log');
EXECUTE DBMS_LOGMNR.START_LOGMINER( -
OPTIONS=>DBMS_LOGMNR.DICT_FROM_ONLLINE_CATALOG);
STARTTIME => '01-Jan-2021 00:00:00',
ENDTIME =>
CONTINUOUS MINE IS GONE IN 19C
USE
DESC V$LOGMNR_CONTENETS
COLUMN X FORMAT A##;
SELECT OPERATION,USERNAME,OS_USENAME, SQL_REDO, TIMESTAMP FROM VS LOGMNR_CONTENTS;
DATA DICTIONARY USES UTL_FILE_DIR
localhost:1158/em
alter dataabae add suplimental log data(pirmary key) columns
alter system switch logfile; -- to force checkpoint
1. create init param on oracle db pointing to path \
init param can be pfile INIT.ora or spfile (server binary)
SHOW PARAMETERS UTL_FILE_DIR;
alter system set UTL_FILE_DIR = path
then us the DBMS_LOGMNR_D.build in plsql
to build dd
EXECUTE DBMS_LOGMNR_D.BUILD('datadict.ora', -
'utl_file_dir_loc', -
DBMS_LOGMNR_D.store_in-flat_file;>>
EXECUTE DBMS_LOGMNR.START_LOGMNR( -
DICTFILENAME => 'PATH/datadict.ora');>
https://grepora.com/2020/05/13/19c-could-not-execute-dbms_logmnr-start_logmnr-ora-44609-continous_mine-is-desupported-for-use-with-dbms_logmnr-start_logmnr/
LogMiner dictionary provide table/column names
Wednesday, April 22, 2020
Oracle alter version control
versionid number not null
version_date date default systimestamp
create unique index UK on fox_version ('1');
Monday, January 6, 2020
Oracle 19c
install
DISPLAY=localhost:0.0
export DISPLAY
global database name= orcl.cgi.com
SID=CUCSDB
ORACLE_ROOT=/ora/c/root/cdb/19c
https://docs.oracle.com/en/database/oracle/oracle-database/12.2/cncpt/introduction-to-oracle-database.html#GUID-2B1BADE1-C36F-4555-9867-3B15B6CE858C
Container CDB
Pluggable PDB (multi tennant) in CDB
Remote Standby Database with Observer
/etc/oratab mounts db startup
/etc/fstab mount points
adrci > show alert
lsnrctl LISTNER