http://kaspyx.tistory.com/25

http://blog.naver.com/PostView.nhn?blogId=intelo&logNo=20067835891

http://markov.tistory.com/40


뭔가 여러차원에 있던 점 들을 euclidean distance를 통해 유사도를 구하게 되면, 그 차원이 직접적으로 유사도에 관련이 없을 때, 정확하지 못한 한계가 생기게 된다.

 이를 극복하기 위해서 새로운 평면에 점을 찍고, 이 평면에서의 euclidean distance와 실제 차이가 같게 되도록 하는 새로운 평면을 찾아내는 작업을 하는 것이 manifold learning(일종의 Dimension Reduction)이고 이것을 학습하기 위한 알고리즘은 래 등이 있음

Isomap은 그래프 상에서 두 노드 간의 최단 경로(shortest path)의 길이를 d(xi,xj)로 사용합니다. 경로의 길이 = [경로상의 링크들의 길이의 합]이고, 각 링크의 길이는 일반적으로 유클리디안 거리를 씁니다. 충분히 가까운 두 점 사이에만 링크가 존재하도록 인접 그래프를 만들었고, 매니폴드의 정의상 충분히 가까운 점들간에는 유클리디안 거리와 실제 거리가 거의 일치하니, 유클리디안 거리를 써도 되는 거죠.

LLE는 우선 각 노드 xi를 이웃한(= xi로의 링크가 존재하는) 다른 노드들의 선형 결합(linear combination)으로 표현하는 것부터 시작합니다. xi와 이웃한 노드들의 집합을 Ni라고 하면, 아래와 같은 등식(wij는 실수값, xj는 벡터)을 가장 잘 만족하는wij들을 구하는 거죠(Ni에 속하지 않은 xj들에 대한 wij는 모두 0).

'COMPUTER > Machine Learning' 카테고리의 다른 글

추천 공부 할 링크  (0) 2022.06.20
TensorFlow Mnist Beginner Code  (0) 2015.12.03
머신 러닝 관련 용어  (0) 2015.07.17
Likelihood Function  (0) 2013.05.06
loss function  (0) 2013.05.06

http://jmnote.com/wiki/%EB%A6%AC%EB%88%85%EC%8A%A4_CPU_%EA%B0%9C%EC%88%98_%ED%99%95%EC%9D%B8


http://jmnote.com/wiki/%EC%9C%88%EB%8F%84%EC%9A%B0_CPU_%EC%BD%94%EC%96%B4_%EC%88%98_%ED%99%95%EC%9D%B8

500 TB Or More Of Data Under Management, According To New InformationWeek Reports Research

Yet just 22% say data analysis is core to how they do business.

Published: Thursday, Nov. 29, 2012 - 9:09 am

/PRNewswire/ -- UBM Tech's InformationWeek Reports, a service provider for peer-based IT research and analysis, announced the release of its latest research report. 6 Big Data Lies encompasses analysis of results from InformationWeek's recent Big Data Survey shares with readers best practices and pitfalls when collecting and analyzing data.  Two-hundred and fifty-seven respondents participated in the survey.

(Photo: http://photos.prnewswire.com/prnh/20121129/SF20332-INFO)

Research Summary:

The ability to collect and analyze data is a core IT value proposition and there's no question there's more data available than ever, especially information from the Web and the new wave of smart mobile devices.  The issue, though, is that most businesses aren't good at using the data they have now.  What are the odds companies will get better with more being piled on? More data doesn't fix bad analysis.

Findings: 

  • 45% of respondents plan to grow analytics tools capabilities over the next 12 months.
  • 35% include CRM in their integrated data analysis and reporting programs, but only 29% include email and just 22% include Web analytics.
  • Only 20% plan to increase their dedicated analytics staff over the next year.
  • Just 9% say their organizations are very effective at identifying critical data and using it to make decisions.

The report author, Michael Healey, is the president of Yeoman Technology Group, an engineering and research firm focusing on maximizing technology investments for organizations, and an award-winning InformationWeek Reports contributor.

For full access to the research data, members can download now:http://reports.informationweek.com/abstract/81/9081/Business-Intelligence-and-Information-Management/research-big-data-smart-data.html?cid=rpt_press_rls

"Companies have been doing an adequate job in building the infrastructure needed for data analysis," says Lorna Garey, content director of InformationWeek Reports. "However, our research shows there are major gaps in data analysis, even for the most common pieces of information that have been in use for years, such as transactional data, system logs, email, CRM, even Web analytics."

For more information: Art Wittmann     VP & Managing Director, InformationWeek Reports 415-947-6361 art.wittmann@ubm.com

About UBM Tech

UBM Tech is a global media business that provides information, events, training, data services, and marketing solutions for the technology industry.  Its media brands and information services inform and inspire decision makers across the entire technology market— engineers and design professionals, software and game developers, solutions providers and integrators, networking and communications executives, and business technology professionals.  UBM Tech's industry-leading media brands include EE TimesInteropBlack HatInformationWeekGame Developer ConferenceCRN, and DesignCon. The company's information products include research, education, training, and data services that accelerate decision making for technology buyers.  UBM Tech also offers a full range of marketing services based on its content and technology market expertise, including custom events, content marketing solutions, community development and demand generation programs. UBM Tech is a part of UBM (UBM.L), a global provider of media and information services with a market capitalization of more than $2.5 billion.

SOURCE UBM Tech



출처 :http://www.sacbee.com/2012/11/29/5018763/45-of-companies-have-500-tb-or.html


Read more here: http://www.sacbee.com/2012/11/29/5018763/45-of-companies-have-500-tb-or.html#storylink=cpy

/**
* Class: TestMemory
* @author: Viral Patel
* @description: Prints JVM memory utilization statistics
*/
public class TestMemory {
     
    public static void main(String [] args) {
         
        int mb = 1024*1024;
         
        //Getting the runtime reference from system
        Runtime runtime = Runtime.getRuntime();
         
        System.out.println("##### Heap utilization statistics [MB] #####");
         
        //Print used memory
        System.out.println("Used Memory:"
            + (runtime.totalMemory() - runtime.freeMemory()) / mb);
 
        //Print free memory
        System.out.println("Free Memory:"
            + runtime.freeMemory() / mb);
         
        //Print total available memory
        System.out.println("Total Memory:" + runtime.totalMemory() / mb);
 
        //Print Maximum available memory
        System.out.println("Max Memory:" + runtime.maxMemory() / mb);
  

WHAT WG(Web Hypertext Applications Technology Working Group)

ㅇHTML의 새로운 명세를 연구하여 표준화 단체에 제안하는 목적으로  2004년 말에 만들어짐

ㅇW3C가 HTML의 개발을 중단하고 XHTML의 개발에 집중하면서 이와는 다르게 HTML을 계속 발전시키길 원했던 대표적인 브라우저 개발사인 Apple, Mozilla, Opeara가 공동으로 성립했음

iSQL에서 내용을 보기좋게 
set linesize 200; 
set colsize 30 ; 

알티베이스에서 좀더 보기 쉽도록 포퍼먼스 뷰를 만든다.
출처 : 알티베이스 튜닝 교육

/**

--테이블크기 정보 조회 


TABLESPACE_NAME : 테이블스페이스명
TABLE_NAME      : 테이블명
ALLOC           : 테이블 ALLOC 크기(MB)
USED            : 테이블 사용량 크기(MB)

**/
CREATE OR REPLACE view  ADM_TBL_INFO AS   
SELECT A.NAME TABLESPACE_NAME,
            B.TABLE_NAME TABLE_NAME,
            TRUNC((C.FIXED_ALLOC_MEM+C.VAR_ALLOC_MEM)/1024/1024,2) "ALLOC(MB)",
            TRUNC((C.FIXED_USED_MEM+C.VAR_USED_MEM)/1024/1024,2) "USED(MB)"
       FROM V$TABLESPACES A,
            SYSTEM_.SYS_TABLES_ B,
            V$MEMTBL_INFO C
      WHERE A.ID = C.TABLESPACE_ID
        AND B.TABLE_OID = C.TABLE_OID
        AND B.USER_ID != 1 AND B.TABLE_TYPE = 'T'
      UNION ALL
     SELECT A.NAME TABLESPACE_NAME,
            B.TABLE_NAME,
            TRUNC(C.DISK_TOTAL_PAGE_CNT*8/1024,2) ALLOC,
            TRUNC(C.DISK_PAGE_CNT*8/1024,2) USED
       FROM V$TABLESPACES A,
            V$DISKTBL_INFO C,
            SYSTEM_.SYS_TABLES_ B
      WHERE C.TABLE_OID = B.TABLE_OID
        AND A.ID = C.TABLESPACE_ID
      ORDER BY 1,2;
/**

--테이블스페이스 정보 조회 


TBS_NAME      : 테이블스페이스명
MAXSIZE(MB)   : 테이블스페이스 최대크기
USEDSIZE(MB)  : 테이블스페이스 사용량
CURRSIZE(MB)  : 테이블스페이스 현재크기


**/
CREATE OR REPLACE view  ADM_TBS AS
SELECT RTRIM(NAME) AS TBS_NAME,
            MAXSIZE/1024/1024 AS 'MAXSIZE(MB)',
            USEDSIZE/1024/1024 AS 'USEDSIZE(MB)',
            CURRSIZE/1024/1024 AS 'CURRSIZE(MB)'
       FROM (
            SELECT B.SPACEID,
                   B.MAXSIZE,
                   A.USEDSIZE,
                   CURRSIZE
              FROM (
                   SELECT A.SPACE_ID,
                          NVL(sum(B.ALLOC), 0) ALLOCSIZE,
                          NVL(sum(B.USED), 0) USEDSIZE
                     FROM V$MEM_TABLESPACES A
                     LEFT JOIN
                          (
                          SELECT A.TABLESPACE_ID,
                                 B.TABLE_NAME,
                                 SUM(A.FIXED_ALLOC_MEM+A.VAR_ALLOC_MEM) ALLOC,
                                 SUM(A.FIXED_USED_MEM+A.VAR_USED_MEM) USED
                            FROM V$MEMTBL_INFO A,
                                 SYSTEM_.SYS_TABLES_ B
                           WHERE A.TABLE_OID=B.TABLE_OID
                           GROUP BY A.TABLESPACE_ID, B.TABLE_NAME
                          ) B
                       ON A.SPACE_ID=B.TABLESPACE_ID
                    WHERE A.SPACE_ID != 0
                    group by a.space_id
                   ) A,
                   (
                   SELECT 1 SPACEID,
                               MEM_MAX_DB_SIZE MAXSIZE,
                               MEM_ALLOC_PAGE_COUNT * 32 * 1024 ALLOCSIZE,
                               MEM_ALLOC_PAGE_COUNT * 32 * 1024 CURRSIZE
                          FROM V$DATABASE
                  ) B
                    UNION ALL
                    SELECT DF.SPACEID SPACEID,
                               df.MAXSIZE,
                               NVL(UF.USEDSIZE,'N/A') USEDSIZE,
                               df.CURRSIZE
                          FROM (
                                SELECT SPACEID, 
                                       SUM(MAXSIZE) * 8 * 1024 MAXSIZE,
                                       SUM(CURRSIZE) * 8 * 1024 CURRSIZE
                                  FROM X$DATAFILES
                                 GROUP BY SPACEID
                               ) DF,
                               (
                                SELECT ID SPACEID,
                                       to_char(ALLOCATED_PAGE_COUNT * 8 * 1024) as USEDSIZE
                                  FROM v$TABLESPACES 
                                 WHERE ID NOT IN
                                       (
                                       SELECT SPACE_ID
                                         FROM V$MEM_TABLESPACES
                                       )
                                ) UF
                   WHERE DF.SPACEID = UF.SPACEID
                 ) TBS_SZ
        LEFT OUTER JOIN
             V$TABLESPACES TBS_INFO
          ON TBS_SZ.SPACEID = TBS_INFO.ID
       ORDER BY TBS_SZ.SPACEID;
/**

--USER 별 모든 OBJECT


USER_NAME            : USER 명 
TABLE_NAME           : 
OBJECT_TYPE          : OBJECT 종류


**/
CREATE OR REPLACE view  ADM_OBJECT AS
SELECT  Y.USER_NAME,
        X.TABLE_NAME,
        DECODE(X.TABLE_TYPE, 'T', 'TABLE', 'V', 'VIEW', 'S', 'SEQUENCE') OBJECT_TYPE
  FROM  SYSTEM_.SYS_TABLES_ X INNER JOIN
        SYSTEM_.SYS_USERS_ Y ON X.USER_ID = Y.USER_ID
 WHERE  Y.USER_ID > 1
UNION ALL
SELECT  Y.USER_NAME,
        X.PROC_NAME ,
        'PSM'
  FROM  SYSTEM_.SYS_PROCEDURES_ X INNER JOIN
        SYSTEM_.SYS_USERS_ Y ON X.USER_ID = Y.USER_ID
 WHERE  Y.USER_ID > 1
UNION ALL
SELECT  NVL(B.USER_NAME,'PUBLIC') USER_NAME,
        A.OBJECT_OWNER_NAME||'.'||OBJECT_NAME,'SYNONYMS'
  FROM  SYSTEM_.SYS_SYNONYMS_ A
   LEFT OUTER JOIN SYSTEM_.SYS_USERS_ B
     ON A.SYNONYM_OWNER_ID = B.USER_ID
  WHERE OBJECT_OWNER_NAME NOT IN ('SYSTEM_')
  ORDER BY 1;
/**

--시노님 정보 조회

USER_NAME            : 유저이름(PUBLIC, 유저)
SYSNONYM_NAME        : 시노님이름
OBJ_NAME             : OBJECT 이름


**/
CREATE OR REPLACE view  ADM_SYNONYM AS
SELECT  NVL(B.USER_NAME,'PUBLIC') AS USER_NAME,
        SYNONYM_NAME,
        A.OBJECT_OWNER_NAME||'.'||OBJECT_NAME AS OBJ_NAME
  FROM  SYSTEM_.SYS_SYNONYMS_ A
   LEFT OUTER JOIN SYSTEM_.SYS_USERS_ B
     ON A.SYNONYM_OWNER_ID = B.USER_ID
  WHERE OBJECT_OWNER_NAME NOT IN ('SYSTEM_')
  ORDER BY 1;
/**

--리플리케이션 정보 조회 


REPLICATION_NAME : 리플리케이션 명 
XSN	         : Replication Sequence No 
REPGAP		 : Replication Gap 
REMOTE_REPL	 : Replication 대상 정보 
RECEIVER_STAT	 : Reciever 상태 


**/
CREATE OR REPLACE view  ADM_REPLICATION AS
SELECT 
    A.REPLICATION_NAME, 
    A.XSN, 
    NVL(TO_CHAR(E.REP_GAP), 'N/A') AS REPGAP, 
    D.HOST_IP || ' (' || D.PORT_NO || '):' || CASE2(TO_CHAR(B.PEER_PORT) = '', 'OFF', 'ON') AS REMOTE_REPL,   
    CASE2(TO_CHAR(C.PEER_PORT) = '', 'OFF', 'ON') AS RECEIVER_STAT 
FROM 
    ( SELECT    REP_NAME, 
		MAX(REP_GAP) AS REP_GAP 
      FROM 
		V$REPGAP 
      GROUP BY REP_NAME 
    ) E,
    SYSTEM_.SYS_REPL_HOSTS_ D , SYSTEM_.SYS_REPLICATIONS_ A
    LEFT OUTER JOIN V$REPSENDER B ON A.REPLICATION_NAME = B.REP_NAME 
    LEFT OUTER JOIN V$REPRECEIVER C ON A.REPLICATION_NAME = C.REP_NAME 
WHERE D.REPLICATION_NAME = A.REPLICATION_NAME  
AND A.REPLICATION_NAME = E.REP_NAME
ORDER BY A.REPLICATION_NAME;
/**

--시퀀스의 정보를 나타냄  

SEQ_NAME : SEQUENCE 명 
CURRENT_SEQ : 현재 SEQUENCE 번호 
START_SEQ   : SEQUENCE 시작 번호 
INCREMENT_SEQ : 증가 번호 
CACHE_SIZE : 캐시 
MAX_SEQ : 최대 값 
MIN_SEQ : 최소 값 
IS_CYCLE : 순환 여부 

**/
CREATE OR REPLACE view  ADM_SEQUENCE AS
SELECT C.USER_NAME||'.'||B.TABLE_NAME SEQ_NAME,
       A.CURRENT_SEQ,
       A.START_SEQ, 
       A.INCREMENT_SEQ,
       A.CACHE_SIZE, 
       A.MAX_SEQ, 
       A.MIN_SEQ, 
       A.IS_CYCLE
  FROM V$SEQ A, SYSTEM_.SYS_TABLES_ B, SYSTEM_.SYS_USERS_ C
 WHERE A.SEQ_OID = B.TABLE_OID 
   AND B.USER_ID = C.USER_ID 
   AND B.USER_ID != 1
 ORDER BY SEQ_NAME;    
 /**
--전체 뷰에 대한 정보를 조회 
	
VIEW_NAME : 뷰 명 
VIEW_ID   : View Object ID 
STATUS	  : View 의 상태 

**/
CREATE OR REPLACE view  ADM_VIEW AS
SELECT C.USER_NAME||'.'||B.TABLE_NAME VIEW_NAME,
       A.VIEW_ID,
       DECODE(A.STATUS,0,'VALID','INVALID') STATUS
  FROM SYSTEM_.SYS_VIEWS_ A, SYSTEM_.SYS_TABLES_ B,
       SYSTEM_.SYS_USERS_ C
 WHERE A.VIEW_ID = B.TABLE_ID AND A.USER_ID=C.USER_ID
 ORDER BY VIEW_NAME;
/**

--인덱스에 속한 전체 컬럼명을 출력 

TABLE_NAME : 테이블명 
INDEX_NAME : 인덱스명 
COLUMN_NAME : 컬럼명 
COLUMN_ORDER : 해당 컬럼 Ordering 된 순서 
**/
CREATE OR REPLACE view  ADM_COL_INDEX AS
SELECT D.USER_NAME||'.'||C.TABLE_NAME TABLE_NAME,
       B.INDEX_NAME, 
       E.COLUMN_NAME,
       DECODE(SORT_ORDER,'A','ASC','D','DESC') COLUMN_ORDER
  FROM SYSTEM_.SYS_INDEX_COLUMNS_ A, SYSTEM_.SYS_INDICES_ B,
       SYSTEM_.SYS_TABLES_ C, SYSTEM_.SYS_USERS_ D,
	   SYSTEM_.SYS_COLUMNS_ E
 WHERE A.INDEX_ID = B.INDEX_ID 
   AND A.TABLE_ID = C.TABLE_ID 
   AND A.USER_ID = D.USER_ID 
   AND A.COLUMN_ID = E.COLUMN_ID 
   AND D.USER_ID != 1
 ORDER BY TABLE_NAME, INDEX_NAME, INDEX_COL_ORDER;
/**

-- 모든 인덱스들의 대한 정보

INDEX_ID : Index ID 
TABLE_NAME : 해당 인덱스가 있는 테이블 명 
TBS : Index의 Tablespace 명 
UNIQUENESS : Unique Index 여부 
COLUMN_COUNT  : Column 갯수 

**/
CREATE OR REPLACE view  ADM_INDEX AS
SELECT A.INDEX_ID, 
       C.USER_NAME||'.'||B.TABLE_NAME TABLE_NAME,
       A.INDEX_NAME INDEX_NAME,
       NVL(D.NAME,'MEMORY') TBS,
       DECODE(IS_UNIQUE,'T','UNIQUE','NONUIQUE') UNIQUENESS,
       A.COLUMN_CNT COLUMN_COUNT 
  FROM SYSTEM_.SYS_INDICES_ A LEFT OUTER JOIN V$TABLESPACES D
       ON A.TBS_ID = D.ID, 
       SYSTEM_.SYS_TABLES_ B, SYSTEM_.SYS_USERS_ C
 WHERE A.TABLE_ID = B.TABLE_ID
   AND A.USER_ID = C.USER_ID
   AND C.USER_ID != 1
 ORDER BY TABLE_NAME, INDEX_NAME ;
/**

-- Constraint 에 대한 조회 

TABLE_NAME : Contraint 가 설정된 테이블 명 
CONSTRAINT_NAME : Constraint 명 
CON_TYPE : Contraint 종류 
INDEX_NAME : 해당 Constraint 가 index 존재를 필요로 할 경우 해당 Index 명 
REFERENCE_TABLE : Constraint 가 FK 일 경우 참조하는 테이블 명 
REFERENCE_INDEX : Constraint 가 FK 일 경우 참조하는 인덱스 명 

**/
CREATE OR REPLACE view  ADM_CONSTRAINT AS     
SELECT C.USER_NAME||'.'||B.TABLE_NAME TABLE_NAME,
        A.CONSTRAINT_NAME,
	    DECODE(A.CONSTRAINT_TYPE,0,'FOREIGNKEY',
    		1,'NOTNULL',
	    	2,'UNIQUE',
    		3,'PRIMARYKEY',
		    4,'NULL',
		    5,'TIMESTAMP','UNKNOWN') CON_TYPE,
	    D.INDEX_NAME,
	    (SELECT TABLE_NAME FROM SYSTEM_.SYS_TABLES_ IT WHERE IT.TABLE_ID = A.REFERENCED_TABLE_ID) REFERENCE_TABLE,
	    (SELECT INDEX_NAME FROM SYSTEM_.SYS_INDICES_ II WHERE II.INDEX_ID = A.REFERENCED_INDEX_ID) REFERENCE_INDEX
   FROM SYSTEM_.SYS_CONSTRAINTS_ A LEFT OUTER JOIN SYSTEM_.SYS_INDICES_ D
        ON A.INDEX_ID = D.INDEX_ID ,
	    SYSTEM_.SYS_TABLES_ B, SYSTEM_.SYS_USERS_ C
  WHERE A.TABLE_ID = B.TABLE_ID 
    AND A.USER_ID = C.USER_ID
  ORDER BY TABLE_NAME ,CON_TYPE;      
/**

-- 현재 Altibase 에 접속된 세션의 정보를 출력합니다. 

ID        :  Session ID 
CONN_INFO :  접속된 세션의 정보  
ACTIVE    :  Action 여부를 판단합니다. 
OPEN_STMT :  해당 세션이 연 모든 Statment 갯수 
CURRENT_STMT : 현재 수행 중인 Statement ID 
COMMIT_MODE  : Commit 모드 

**/
CREATE OR REPLACE view  ADM_SESSION AS
SELECT ID,
       REPLACE2(REPLACE2(COMM_NAME,'SOCKET-',NULL),'-SERVER',NULL) CONN_INFO,
       DECODE(ACTIVE_FLAG,1,'ACTIVE','INACTIVE') ACTIVE,
       OPENED_STMT_COUNT OPEN_STMT,
       CURRENT_STMT_ID CURRENT_STMT,
       CLIENT_PID,
       DECODE(AUTOCOMMIT_FLAG,0,'Non AutoCommit','AutoCommit') COMMIT_MODE
  FROM V$SESSION;  
/**

-- LOCK 정보 조회

SESSION_ID     : 세션 ID
TX_ID          : 트렌젝션 ID
TBL_INFO       : 테이블 정보
LOCK_ITEM_TYPE : LOCK 상태
STATE          : 쿼리 상태
QUERY          : 쿼리 내역
**/
CREATE OR REPLACE view  ADM_LOCK AS
SELECT  A.SESSION_ID AS SESSION_ID,
        A.TX_ID AS TX_ID,
        DECODE(LOCK_ITEM_TYPE,'TBS',B.NAME,'TBL',C.TABLE_NAME,DBF_ID) TBL_INFO ,
        LOCK_DESC AS LOCK_ITEM_TYPE,
        DECODE(A.STATE,0,'ALLOC',1,'PREPARED',2,'FETCH-READY',4,'FETCHING','UNKNOWN') AS STATE,
        RPAD(QUERY,120) AS QUERY
FROM    V$LOCK_STATEMENT A LEFT OUTER JOIN V$TABLESPACES B
        ON A.TBS_ID=B.ID
        LEFT OUTER JOIN SYSTEM_.SYS_TABLES_ C
        ON A.TABLE_OID=C.TABLE_OID
ORDER BY SESSION_ID;
/**

-- PROCEDURE 정보 조회 
USER_NAME   : 유저이름
PROC_NAME   : procedure 이름
OBJECT_TYPE : 타입(PROCEDURE,FUNCTION,TYPE_SET)
STATUS      : 상태


**/
CREATE OR REPLACE view  ADM_PROC AS
SELECT  B.USER_NAME, A.PROC_NAME, 
        DECODE(A.OBJECT_TYPE,0,'PROCEDURE',1,'FUNCTION','TYPE_SET') AS TYPE,
        DECODE(A.STATUS,0,'VALID','INVALID') AS STATUS
  FROM  SYSTEM_.SYS_PROCEDURES_ A, SYSTEM_.SYS_USERS_ B
 WHERE  A.USER_ID=B.USER_ID
       AND B.USER_NAME <> 'SYSTEM_'; 
  /**

-- TRIGGER 정보 조회 
USER_NAME      : 유저이름
TRIGGER_NAME   : 트리거 이름
TABLE_NAME     : 테이블 이름
ENABLE         : 상태
EVENT_TIME     : 이벤트 시간
EVENT_TYPE     : 이벤트 타입
GRANULARITY    : 이벤트 조건


**/
CREATE OR REPLACE view  ADM_TRIGGER AS
SELECT  B.USER_NAME, A.TRIGGER_NAME, C.TABLE_NAME, 
        DECODE(A.IS_ENABLE,0,'DISABLE','ENABLE') AS ENABLE,
        DECODE(A.EVENT_TIME,1,'BEFORE','AFTER') AS EVENT_TIME,
        DECODE(A.EVENT_TYPE,1,'INSERT',2,'DELETE',3,'UPDATE') AS EVENT_TYPE,
        DECODE(A.GRANULARITY,1,'FOR EACH ROW',2,'FOR EACH STATEMENT') AS GRANULARITY
  FROM  SYSTEM_.SYS_TRIGGERS_ A, SYSTEM_.SYS_USERS_ B,
        SYSTEM_.SYS_TABLES_ C
 WHERE  A.USER_ID=B.USER_ID
    AND C.TABLE_ID=A.TABLE_ID ;


http://newhyuki.egloos.com/1957158

알티베이스 메모리 사이즈 부분별로 보기 (v$memstat)
->
SELECT * FROM V$MEMSTAT ORDER By 4 DESC;

------------------------------------------------------------------------------------------------------------------

메모리 테이블 별 사이즈 보기.
->
SELECT 
        A.TABLE_OID TABLEOID,
        C.USER_NAME||'.'||B.TABLE_NAME TABLENAME,
        A.MEM_SLOT_SIZE SLOTSIZE,
        FIXED_ALLOC_MEM+VAR_ALLOC_MEM ALLOCBYTE,
        FIXED_USED_MEM+VAR_USED_MEM USEDBYTE,
        ROUND ((FIXED_USED_MEM+VAR_USED_MEM)/(FIXED_ALLOC_MEM+VAR_ALLOC_MEM)*100,2) EFFICIENCY
FROM
        V$MEMTBL_INFO A,
        SYSTEM_.SYS_TABLES_ B,
        SYSTEM_.SYS_USERS_ C
WHERE
        A.TABLE_OID = B.TABLE_OID AND
        B.USER_ID = C.USER_ID AND
        C.USER_ID != 1 AND
        B.TABLE_TYPE != 'V' AND
        B.TABLE_TYPE = 'T'
        ORDER BY TABLENAME;

출처 : http://www.mins01.com/20090118/board/board.php?type=read&b_id=tech&sh=&sw=&cat=DataBase&page=1&b_idx=585

(내가 들고 실행한 절차... WINDOW server에서.. 버전 5.3.3.xx에서 5.3.3.68 패치 설치 )

1. server stop하기

2. 알티베이스 홈 아래에 있는 bin, msg, lib, include 파일 복사하여 백업해두기(안될때 대비해서)

3.다른 머신에서 실행파일 실행 - 윈도우에서는 한번에 하나밖에 설치가 안되어서 다른 머신이 필요하다고 함

4.다른 머신의 HOME경로에 있는bin, msg, lib, include파일로 기존 머신의 bin,msg,lib,include파일을 덮어쓰기

5. 혹시 문제가 생기면 아까 백업해놓은 파일로 다시 덮어 쓰면 됨..

+ Recent posts