error 1062 (23000) at line duplicate entry for key ‘primary’

2015-11-23 KENNETH 1

error 1062 (23000) at line XX duplicate entry for key ’primary’ 에 대한 고찰   데이터 마이그레이션 작업을 하면서 자꾸만 오류가 발생.. ERROR 1062 (23000) at line 23: Duplicate entry ‘4’ for key ‘PRIMARY’   운영중인 데이터베이스의 레코드와 해당 레코드를 DUMP한 내용을 아무리 살펴봐도 잘못된점을 찾을 수 없는 상황이었는데….   알고보니.. 동일한 테이블명이 존재하고 있었던것!!!!! ?????? 이런식으로.. -rw-rw—- 1 mysql mysql 462 Nov 23 17:57 abc.frm -rw-rw—- 1 mysql mysql 462 Nov 23 17:57 Abc.frm -rw-rw—- 1 mysql mysql 8192 Nov 23 17:57 abc.MAD -rw-rw—- 1 mysql mysql 8192 Nov 23 17:57 Abc.MAD -rw-rw—- 1 mysql mysql 8192 Nov 23 17:57 abc.MAI -rw-rw—- 1 mysql mysql 8192 Nov 23 17:57 Abc.MAI   물론 여기에 기재한것은 내가 테스트를 해본것이고.. 실제 이름은 다른거;;; ㅋ   만들어 보니까 정말로 저렇게 되더라고.. mysql (test)>create table abc (kk int(3), kk2 text); Query OK, 0 rows [ more… ]

mariadb supported engines

2015-11-18 KENNETH 0

출처 : https://mariadb.com/kb/en/mariadb/choosing-the-right-storage-engine/ 출처2 : https://mariadb.com/kb/en/mariadb/storage-engines/   MariaDB supported engines   The Archive storage engine is, unsurprisingly, best used for archiving. Aria, MariaDB’s more modern improvement on MyISAM, has a small footprint and allows for easy copy between systems. The BLACKHOLE storage engine accepts data but does not store it and always returns an empty result, useful, for example, if you want to run complex filtering rules on a slave without incurring any overhead on a master. Cassandra is a NoSQL engine. CONNECT allows access to different kinds of text files and remote resources as if they were regular MariaDB tables. The CSV storage engine can read and append to files stored in CSV (comma-separated-values) format. However, since MariaDB 10.0, CONNECT is a better storage engine is able to read and write such files. FederatedX uses libmysql to talk to the data [ more… ]

MySQL 5.7 Supported Storage Engines

2015-11-18 KENNETH 0

출처 : https://dev.mysql.com/doc/refman/5.7/en/storage-engines.html   MySQL 5.7 Supported Storage Engines InnoDB: The default storage engine in MySQL 5.7. InnoDB is a transaction-safe (ACID compliant) storage engine for MySQL that has commit, rollback, and crash-recovery capabilities to protect user data. InnoDB row-level locking (without escalation to coarser granularity locks) and Oracle-style consistent nonlocking reads increase multi-user concurrency and performance. InnoDB stores user data in clustered indexes to reduce I/O for common queries based on primary keys. To maintain data integrity, InnoDB also supports FOREIGN KEY referential-integrity constraints. For more information about InnoDB, see Chapter 14, The InnoDB Storage Engine. MyISAM: These tables have a small footprint. Table-level locking limits the performance in read/write workloads, so it is often used in read-only or read-mostly workloads in Web and data warehousing configurations. Memory: Stores all data in RAM, for fast access in environments that require [ more… ]

No Image

NL-00303: syntax error in NV string

2015-07-07 KENNETH 0

오라클 리스너 구동시 다음과 같은 에러가 발생하면서 리스너 시작이 안될때 TNS-01155: Incorrectly specified SID_LIST_LISTENER parameter in LISTENER.ORA NL-00303: syntax error in NV string 뭐 결론은 구문 에러이다… 하지만 아무리 봐도 뭐가 잘못됐는지 알 수 없었는데… 아래 기본 생성되는 listener.ora 파일중… SID_LIST_LISTENER = (SID_LIST = (SID_DESC = (SID_NAME = CLRExtProc) (ORACLE_HOME = D:\oracle\product\12.1.0) (PROGRAM = extproc) (ENVS = <span style=”line-height: 1.5;”>”EXTPROC_DLLS=ONLY:D:\oracle\product\12.1.0\bin\oraclr12.dll”)</span> ) ) LISTENER = (DESCRIPTION_LIST = (DESCRIPTION = (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521)) (ADDRESS = (PROTOCOL = TCP)(HOST = WIN-JIRAKHOME) (PORT = 1521)) ) ) ”LISTENER =” 라고 시작되는 부분의 앞에 공백한칸이 있었던 것이다.. 세상에나… -_-;;;; 리눅스에서도 저런 문제가 있었는지 기억도 안나고 테스트를 해보기도 귀찮지만… 공백정도야… 생각했는데 그게 아니네;;; 또한 옆에 다른분은 똑같은 내용인데 윈도우에 기본 설치된 notepad(메모장)으로 파일을 열고 저장해도 문제가 되는 경우가 있었다고 한다.

No Image

ORA-65096: invalid common user or role name on oracle12c

2015-07-06 KENNETH 0

ORA-65096: invalid common user or role name on oracle12c 오라클12c 를 설치하고 계정을 생성하다 보니 이런 에러가 발생하면서 실패;;;;;; 구문이 맞는지 확인했으나.. 너무 간단하기도 하고 틀린것 같지도 않아서 찾아보니.. http://docs.oracle.com/database/121/ERRMG/e60000.htm   ORA-65096: invalid common user or role name Cause: An attempt was made to create a common user or role with a name that was not valid for common users or roles. In addition to the usual rules for user and role names, common user and role names must start with C## or c## and consist only of ASCII characters.   Action: Specify a valid common user or role name. 이렇댄다.. 아무리 공식적인 거라도 그렇지.. 그럼 세상에 뭔 ”C##”을 계정을 생성할때마다 써줘야 하는건가… 했더니만..   세상 어디에든 젖과 꿀은 있게 마련인갑다… http://www.dba-oracle.com/t_ora_65096_create_user_12c_without_c_prefix.htm   connect system/manager as sysdba alter session set “_ORACLE_SCRIPT”=true; create user fred identified by flintstone; grant dba to [ more… ]