'분류 전체보기'에 해당되는 글 83건

  1. 2012.09.19 의료기관 개인정보보호 가이드라인
  2. 2012.07.26 Compound Triggers in Oracle 11g
  3. 2012.07.25 버림과 비움
  4. 2012.07.25 우리나라에 있는 세계 각국의 문화원
  5. 2012.07.19 Apple Gearing Up for the Coming NFC- iPhone Revolution
  6. 2012.05.15 ORA-20023: Missing start and end values for time model stat
  7. 2012.05.07 Atlanta의 지하철 MARTA와 Breeze Card 1
  8. 2012.02.16 Power Designer와 ERWin의 비교
  9. 2011.08.24 2011년 9월말에 시행되는 개인정보 보호법에 대한 자료 1
  10. 2011.08.11 Bug 5969934: EXPDP CLIENT GETS UDE-00008 ORA-31626 WHILE THE SERVER SIDE EXPORT IS OK 4

의료기관 개인정보보호 가이드라인

Happening 2012. 9. 19. 10:12

의료기관 개인정보보호 가이드라인이 보건복지부에서 발표가 되었습니다.


첨부파일을 참고하시기 바랍니다.

추가정보는 www.mw.go.kr or www.privacy.go.kr 에서 확인 가능합니다.



[9.19.수.조간]행안부·복지부,_의료기관_개인정보보호_가이드라인_발간.pdf


:     

TISTORY에 Login하려면 여기를 누르세요.


Compound Triggers in Oracle 11g

Oracle 2012. 7. 26. 13:19

Oracle 11g에서는 Compound Triggers 기능이 생겨서 각 Event별로 Trigger를 만들 필요가 없어졌네요.

 

In earlier versions of Oracle, triggers were the database objects whose ability to collide with the current database state of an object and session state maintenance, kept the database developers alert while designing triggers.  Oracle11g offers considerable improvements in database triggers. These additions have not only enhanced the language usability but also promise a better performance in a real application environment. 

Oracle 11g fixes major issues by the enhancements as listed below.

  • Trigger firing sequence can be set in Oracle 11g using FOLLOWS keyword
  • Compound Triggers to encapsulate multiple triggering timings in one body
  • Triggers can be created in ENABLED/DISABLED mode
  • The DML triggers in 11g are 25% faster than their earlier versions in terms of compilation, execution and firing

In the tutorial, you will learn how Compound Triggers works and its benefits to the users.

1. Compound Triggers: Introduction

Compound triggers are the database DML triggers which ‘compounds’ or combines all the triggering timings under one trigger body. The triggering timings available for database triggers are BEFORE STATEMENT, AFTER STATEMENT, BEFORE EACH ROW, and AFTER EACH ROW. Trigger level variables can be defined which would be visible and accessible in all the timing blocks.

Compound trigger body does not contain any exception section but recommends each block to contain its own exception handler under exception section.

2. Compound Triggers: Reaping the Benefits

Compound trigger resolves few big issues, which have been the nightmare for the developers in the past.

  1. Mutating table error ORA-04091
  2. Multithread behavior maintains persistent state of session variables till the statement execution finishes. These are defined in the declaration section of the compound trigger.
  3. Enhanced performance in bulk operations
  4. Supports encapsulation of multiple program units; thus enhances code interactivity

3. Compound Triggers: Usage Guidelines

As a new induction to the database family, there are some introductory guidelines which must be followed while working with compound triggers

  • Compound trigger are meant only for DML operations. No support still for DDL and system operations.
  • Exception handling process has to be done for each timing block.
  • Compound trigger remains passive, if the DML does not changes any rows
  • :OLD and :NEW variable identifiers can exist only in ROW level blocks, where :NEW values can only be modified in BEFORE EACH ROW block
  • No support for WHEN clause. Earlier, WHEN clause could be utilized to impose condition on the trigger action.
  • No support for PRAGMA_AUTONOMOUS_TRANSACTION

There are many debates over the above guidelines, which many identify as compound trigger restrictions. But from developer’s perspective, the benefits from compound triggers are much heavier than these restrictions. The assumptions and restrictions can be melted into code practice and as ‘usage guidelines’.

4. Compound Triggers: Syntax

The syntax shows the four timing blocks in a set order.

Example Syntax [1a]: For DML Triggers

Sample Code
  1. CREATE OR REPLACE TRIGGER [TRIGGER NAME]
  2. FOR [DML] ON [TABLE NAME]
  3. COMPOUND TRIGGER
  4. -- Initial section 
  5. -- Declarations 
  6. -- Subprograms
  7. Optional section
  8. BEFORE STATEMENT IS
  9. …;
  10. Optional section
  11. AFTER STATEMENT IS
  12. …;
  13. Optional section
  14. BEFORE EACH ROW IS
  15. …;
  16. Optional section
  17. AFTER EACH ROW IS
  18. …;
  19. END; 
Copyright exforsys.com


In the syntax, note that the compound trigger offers only the declaration section, which are again locally available in the timing blocks.

Example Syntax [1b]: For database views

INSTEAD OF EACH ROW IS 
...; 
END;

Note that none of the timing blocks should be duplicated. Oracle server raises exception PLS-00676 if duplicate timing blocks is found in the compound trigger definition.

5. Compound Triggers: Additional Notes

5.1. USER_TRIGGERS dictionary view structure has been restructured to include the metadata for compound triggers. The new columns specify whether a timing block is available in the compound trigger body.

5.2. The new triggering event has been introduced for compound trigger as ‘COMPOUND’. The figure below shows the TRIGGER_TYPE, TRIGGERING_EVENT and TABLE_NAME of the trigger TRG_COMP_DEMO.

5.3. The columns BEFORE_STATEMENT, BEFORE_ROW, AFTER_ROW, and AFTER_STATEMENT are set as YES/NO based on the timing blocks available in the compound trigger. For example, the trigger TRG_COMP_DEMO contains all the timing blocks in the trigger body, the columns can be queried as below.

6. Applications of Compound Triggers

A compound trigger is best suited to achieve two objectives.

  • Yield better performance while loading a table simultaneous to a running transaction and using its values.
  • Resolve mutating table error (ORA-04091)

I will  illustrate both the accomplishments in below steps

6.1. Demonstrating performance gains during simultaneous loading

1. Two tables were created

Sample Code
  1. SQL> CREATE TABLE ORDERS (ORD_ID NUMBER, 
  2. ITEM_CODE VARCHAR2(100), 
  3. ORD_QTY NUMBER, 
  4. ORD_DATE DATE); 
  5. TABLE created. 
  6. SQL> CREATE TABLE ORDER_ARCHIVE(ORD_ID NUMBER, 
  7. ORD_CODE VARCHAR2(100));
  8.  
  9. TABLE created. 
Copyright exforsys.com


2. To demonstrate the performance difference between the versions, I create a normal FOR EACH ROW trigger on ORDERS table to insert data into ORDER_ARCHIVE table.

Sample Code
  1. SQL> CREATE OR REPLACE TRIGGER TRG_ORDERS
  2. BEFORE INSERT ON ORDERS
  3. FOR EACH ROW 
  4. BEGIN
  5. DBMS_OUTPUT.PUT_LINE('Insert order‘||:NEW.ORD_ID||’ into ORDER_ARCHIVE');
  6. INSERT INTO ORDER_ARCHIVE VALUES (:NEW.ORD_ID,:NEW.ITEM_CODE);
  7. END;
  8. / 
  9. TRIGGER created. 
Copyright exforsys.com


3. Now, I will insert the test data into the ORDERS table using SELECT statement

Sample Code
  1. SQL> INSERT INTO orders(ord_id, item_code, ord_date)
  2. 2 SELECT (rownum+1)*100, 'ITEM_'||rownum, sysdate-rownum
  3. 3 FROM DUAL
  4. 4* CONNECT BY ROWNUM < 15; 
  5. INSERT ORDER 1 INTO ORER_ARCHIVE
  6. INSERT ORDER 2 INTO ORER_ARCHIVE
  7. INSERT ORDER 3 INTO ORER_ARCHIVE
  8. INSERT ORDER 4 INTO ORER_ARCHIVE
  9. INSERT ORDER 5 INTO ORER_ARCHIVE
  10. INSERT ORDER 6 INTO ORER_ARCHIVE
  11. INSERT ORDER 7 INTO ORER_ARCHIVE
  12. INSERT ORDER 8 INTO ORER_ARCHIVE
  13. INSERT ORDER 9 INTO ORER_ARCHIVE
  14. INSERT ORDER 10 INTO ORER_ARCHIVE
  15. INSERT ORDER 11 INTO ORER_ARCHIVE
  16. INSERT ORDER 12 INTO ORER_ARCHIVE
  17. INSERT ORDER 13 INTO ORER_ARCHIVE
  18. INSERT ORDER 14 INTO ORER_ARCHIVE 
  19. 14 rows created. 
Copyright exforsys.com


Note the output of the above INSERT process. For each of the 14 records inserted into the ORDERS table through the trigger, Oracle server makes simultaneous inserts into the ORDER_ARCHIVE table.

4. Compound triggers in Oracle 11g have the ability to perform simultaneous bulk insert process into the table. I will create the compound trigger TRG_COMP_ORDERS to implement the bulk loading process. Note the use of associative arrays, which hold the data to be inserted. It flushes off once the data is replicated into the ORDER_ARCHIVE table when the index count reaches 20 or the statement execution completes.

Sample Code
  1. SQL> CREATE OR REPLACE TRIGGER TRG_COMP_SAL
  2. FOR INSERT ON ORDERS
  3. COMPOUND TRIGGER
  4. TYPE ORDER_T IS TABLE OF ORDER_ARCHIVE%ROWTYPE 
  5. INDEX BY PLS_INTEGER;
  6. L_ORDERS ORDER_T;
  7. I NUMBER := 0;
  8. AFTER EACH ROW IS
  9. BEGIN
  10. I := I+1;
  11. L_ORDERS(I).ORD_ID := :NEW.ORD_ID;
  12. L_ORDERS(I).ORD_CODE := :NEW.ITEM_CODE;
  13. IF I >= 20 THEN
  14. DBMS_OUTPUT.PUT_LINE('Bulk Load for 20 orders'); 
  15. FOR J IN 1..I
  16. LOOP
  17. INSERT INTO ORDER_ARCHIVE VALUES L_ORDERS(J);
  18. END LOOP;
  19. L_ORDERS.DELETE;
  20. I := 0;
  21. END IF;
  22. END AFTER EACH ROW;
  23. AFTER STATEMENT IS
  24. BEGIN
  25. DBMS_OUTPUT.PUT_LINE('Statement level loading');
  26. FORALL J IN 1..L_ORDERS.COUNT
  27. INSERT INTO ORDER_ARCHIVE VALUES L_ORDERS(J);
  28. L_ORDERS.DELETE;
  29. I := 0;
  30. END AFTER STATEMENT;
  31. END;
  32. /
  33.  
  34. TRIGGER created. 
Copyright exforsys.com


5. I will insert 64 rows (instead of just 14) into ORDERS table using SELECT query. The simultaneous inserts into ORDER_ARCHIVE table are achieved only in 3 bulk insert process.

Sample Code
  1. SQL> INSERT INTO orders(ord_id, item_code, ord_date)
  2. 2 SELECT (rownum+1)*100, 'ITEM_'||rownum, sysdate-rownum
  3. 3 FROM DUAL
  4. 4 connect BY rownum < 65
  5. 5 / 
  6. Bulk LOAD FOR 20 orders
  7. Bulk LOAD FOR 20 orders
  8. Bulk LOAD FOR 20 orders
  9. Statement level loading 
  10. 64 rows created. 
Copyright exforsys.com


Above results clearly differentiate the compound trigger from the conventional triggers in terms of performance while simultaneous data loading.

6.2. Demonstration of Mutating table solution using Compound triggers

Now, let us learn about the most accomplished achievement of Compound Triggers, i.e. their ability to tackle with Mutating table error (ORA-04091).

Mutating table occurs when a table is referenced when it is in floating state. A table is in flux or floating state when it is the participant of a running transaction. Earlier, it used to be taken as a precaution during coding or its effects were diluted using workaround solutions. Few of the efficient workarounds are as below.

  • Change in logic implementation and code design
  • Using PRAGMA_AUTONOMOUS_TRANSACTION
  • Conversion of row level trigger to statement level
  • Defining package to hold variables at session level; these variables would hold the values and later would be inserted once the statement execution finishes.

How compound trigger fixes the problem?

Compound trigger contains the timing blocks and variables, which are persistent till the statement completes and are visible in all the timing blocks of the trigger. These variables are of collection type which holds the table data, before it enters the flux mode. Table gets locked once it moves to flux mode, but the backup data in the collection variables remains persistent and can be used for reference within the trigger.

Therefore, the logic used is same as earlier, but being a single compiled unit, it is more convenient and easily maintained.

In the example code below, the compound trigger fires on update of ORDERS table. It queries the ORDERS table to fetch and display the old quantity. For a conventional DML trigger, the situation is the best candidate for ORA-04091 Mutating table error.

A user updates the order quantity for order id 600. Now before the UPDATE statement executes, the BEFORE STATEMENT block fetches the old ‘order quantity’ value (90) and stores in a collection type variable. Now when the statement executes, it updates the ‘order quantity’ to 150. AFTER STATEMENT block in the trigger displays the ‘old quantity’ value.

Sample Code
  1. CREATE OR REPLACE TRIGGER TRG_ORDERS
  2. FOR UPDATE ON ORDERS
  3. COMPOUND TRIGGER
  4. TYPE ORD_QTY_T IS TABLE OF ORDERS.ORD_QTY%TYPE;
  5. L_ORD_QTY ORD_QTY_T; 
  6. BEFORE STATEMENT IS
  7. BEGIN 
  8. SELECT ORD_QTY 
  9. BULK COLLECT INTO L_ORD_QTY 
  10. FROM ORDERS WHERE ORD_ID=600; 
  11. END BEFORE STATEMENT; 
  12. AFTER EACH ROW IS
  13. BEGIN
  14. DBMS_OUTPUT.PUT_LINE('Old Quantity Value:'||L_ORD_QTY(L_ORD_QTY.FIRST));
  15. END AFTER EACH ROW; 
  16. END;
  17. / 
  18. SQL> UPDATE ORDERS
  19. 2 SET ORD_QTY = 150
  20. 3 WHERE ORD_ID = 600;
  21. Old Quantity Value:90 
  22. 1 row updated. 
Copyright exforsys.com


7. Conclusion

Compound trigger combines the properties of both statement and row level triggers. The logic which was earlier maintained at row and statement level can now be placed into one single body, with state and persistency in data across the timings.

 

출처 : http://www.exforsys.com/tutorials/oracle-11g/compound-triggers-in-oracle-11g.html

:     

TISTORY에 Login하려면 여기를 누르세요.


버림과 비움

Happening 2012. 7. 25. 10:11

 

 

   그룻의 쓰림은 비워짐에 있다.

 

  그릇이 가득 차면 더 이상 그릇이 아니다. 

 

 

모래를 세게 쥘수록 손가락 사이로 더 빠르게 빠져나간다.

 

손에 힘을 빼고 느슨하게 쥐어 보라.

 

손에 빈 공간이 있으면 더욱 많은 모래를 쥘 수 있다.

 

 

나는 지금 무엇을 버리고 비울 수 있을까?

:     

TISTORY에 Login하려면 여기를 누르세요.


우리나라에 있는 세계 각국의 문화원

Happening 2012. 7. 25. 09:45

1. 일본 문화원 (http://www.kr.emb-japan.go.jp/cult/cul_guide_hist.htm) - 안국역 근처

 

2. 중국 문화원 (http://www.cccseoul.org/main/main.php) - 광화문역 근처

 

3. 영국 문화원 (http://www.britishcouncil.org/kr/korea.htm) - 광화문역 근처

 

4. 독일 문화원 (http://www.goethe.de/ins/kr/seo/koindex.htm?wt_sc=seoul_) - 남대문 근처

 

5. 프랑스 문화원 (http://www.france.or.kr/ccf/accessmap.html) - 서울역 근처

 

6. 이탈리아 문화원 (http://www.iicseoul.esteri.it/IIC_Seoul) - 한남역 근처

 

7. 이스라엘 문화원 (http://www.iscc.co.kr/) - 강남역 근처

 

8. 이스탄불 문화원 (http://www.turkey.or.kr/) - 역삼역 근처

 

9. 인도 문화원 (http://www.indembassy.or.kr/) - 한남동 근처

 

10. 러시아 문화원 (http://www.russiacenter.or.kr/) - 논현동 근처 (2012년 6월 이전 중)

 

11. 아제르바이잔 문화원 (http://www.azerbaijan.or.kr/) - 강남역 근처

 

12. 다문화 박물관 (http://www.multiculturemuseum.com) - 독바위역 근처(불광동)

 

'Happening' 카테고리의 다른 글

의료기관 개인정보보호 가이드라인  (0) 2012.09.19
버림과 비움  (0) 2012.07.25
Atlanta의 지하철 MARTA와 Breeze Card  (1) 2012.05.07
수동식 문서 분쇄기  (0) 2010.11.05
정보 습득에 여과 Filter를 달자  (0) 2010.10.11
:     

TISTORY에 Login하려면 여기를 누르세요.


Apple Gearing Up for the Coming NFC- iPhone Revolution

IT News 2012. 7. 19. 17:26

애플의 NFC 관련 특허를 아래와 같이 출원했었군여...

1 - COVER - POINT OF PURCHAS SYSTEM - NFC INTERFACE, CAM, SCAN - 
Later this morning Apple will be providing us with a "sneak peek of the next generation of iPhone OS software." While I have no idea whether Apple will reveal their intention to add NFC (Near Field Communications) technology or not to OS 4 today – I'm fairly certain that it's on Apple's future roadmap. How do I know that? I know that because Apple has delivered a barrage of NFC related patents in the last month that could warp anyone's brains trying to get their head around the enormity of Apple's efforts. There have been over a thousand illustrations to review and today you're going to see one of these massive filings in detail. Today's patent relates to an unbelievable Point of Purchase (POP) application that will eventually be adding very sophisticated new functionality to an iPhone: Functionality that will go far beyond just using it for a single POP application. Apple introduces us to an NFC-iPhone that will include a built-in scanner, biometric sensor, added camera functionality and a secondary fingerprint scanner for verifying a user's identity to retailers. This report even provides you with two videos illustrating how it will technically work with a future MacBook and/or Apple-TV as well.


Patent Background and Overview


Merchants often use point-of-sale or point-of-purchase (POP) systems to complete sales transactions. Typical POP systems may include several independent devices, each performing a different function. For example, a scanner may ring up articles of merchandise and transmit the amount to a cash register to calculate the amount due. The cash register may then transmit the amount due to a credit card reader to receive payment.


The use of multiple devices often results in an immobile POP system due to device sizes and communication requirements. The fixed location of a POP system also may decrease operational flexibility and create time-consuming sales transactions. Today's fast-paced consumers may be unwilling or unable to wait to purchase merchandise, resulting in lost sales and profits for the merchant.


In todays patent report you'll see that Apple's patent introduces us to techniques for performing sales transactions using an iPhone. The iPhone could be made capable of completing an entire sales transaction including ringing up articles of merchandise, receiving payment information, and communicating with an external server to receive authorization for payment. The iPhone could include input devices, such as a near field communication (NFC) interface, camera, and scanner, for retrieving article information and payment information. The electronic device also may use a device identification networking protocol to establish a communication link with another device in order to receive payment information. A software application of the device may calculate the amount due and may retrieve inventory and price information from the merchant's server.


The iPhone may also include one or more communication interfaces for communicating with the merchant's server over a wireless network, personal area network, near field communication channel, or the like. In certain embodiments, the iPhone may use a smart selection method to determine the most suitable communication interface based on data transmission speed, security features, and other user preferences. The iPhone may also include applications for performing various sales related transactions such as exchanging information for a merchant rewards program, establishing customer financing, and performing returns and exchanges.


Apple's iPhone Point-of-Purchase System


Apple's patent FIG. 1 shown below illustrates an iPhone that may make use of the techniques for conducting a sales transaction described above. As illustrated in FIG. 1, the iPhone (noted as patent point #10 throughout the patent) may scan articles of merchandise. The iPhone may also communicate with other devices using short-range connections, such as Bluetooth and near field communication.


For example, a NFC device may be used to scan an article of merchandise and a camera may be used to receive credit card information. The handheld electronic device may communicate with an internal memory and/or an external server to acquire price information and payment authorization through a selected communication channel, such as a wide area network (WAN), local area network (LAN), personal area network (PAN), or near field communication channel. The electronic device may display a notification authorizing the sales transaction. The electronic device also may provide additional functionalities, such as exchanging information for a merchant rewards program, transmitting receipts, and obtaining financing.


The POP Application Icon: when the Point of Purchase (POP) icon 32 is selected on the iPhone (see yellow marked icon in FIG.1) an application for conducting a sales transaction is opened. The application may facilitate sales based transactions such as scanning an article of merchandise, receiving payment information, and retrieving customer information etc.


2 GRAPHIC - POP NFC APP + BIOMETRIC SENSOR & SCANNER 
The NFC Device: The iPhone may include a near field communication (NFC) device (noted as patent point # 44) The NFC device may be located within the iPhone's enclosure and have an exterior symbol to identify its location therein. The NFC device may allow for close range communication at relatively low data rates (424 kb/s), and may comply with standards such as ISO 18092 or ISO 21481, or it may allow for close range communication at relatively high data rates (560 Mbps), and may comply with the TransferJet protocol. In certain embodiments, the communication may occur within a range of approximately 2 to 4 cm or 1 to 1.5 inches.

 

The close range communication with NFC may take place via magnetic field induction, allowing the NFC device to communicate with other NFC devices or to retrieve information from tags having radio frequency identification (RFID) circuitry.

 

The Biometric Sensor: Information also may be acquired through a biometric sensor (Patent Point # 45 of FIG.1), as for example:


  • The biometric sensor may be located within the iPhone's enclosure and may be used to verify or identify a user.
  • The biometric sensor may be used in conjunction with a smartcard to verify the identity of a consumer.
  • The biometric sensor may be used to identify a customer and obtain payment information for that customer by accessing a database of stored customer information.
  • The biometric sensor may include a fingerprint reader or other feature recognition device and may operate in conjunction with a feature-processing program stored on the iPhone (see "Biometric Fingerprint Scanner" below for details).

 

The database may be maintained by the merchant or by a third party service provider.


In Apple's patent FIG. 2 noted above we see that the back of the iPhone has two additional input devices that may be accessed, namely a camera (#46) and a scanner (#48). The location of these inputs may change on any final product.


The Scanner & Decoder: The scanner may be used to obtain merchandise information and/or payment information. For example, the scanner may be used to read a stock-keeping unit (SKU) number of an article for purchase. In another example, the scanner may be used to read bank account information from a check. The scanner may be a laser scanner, LED scanner, or other suitable scanning device and may operate in conjunction with a decoder stored within the iPhone.


Added Camera Functionality: Beyond being able to use the iPhone's camera for capturing images and/or video, the camera in context with this POP application, may also be used to obtain merchandise information or payment information. The camera may be used to capture an image of a credit card to obtain payment information and/or take a picture of an item for purchase to identify the item.


The Biometric Fingerprint Scanner


While we're on the topic of sensors and scanners, we'll now temporarily jump ahead to Apple's patent FIG. 16 where we see a series of screens for acquiring payment information using biometric features. From the payment type selection screen (#198), a merchant may select the biometric selection bar (#200) to display a biometric entry screen (#338). The biometric entry screen includes instructions (#340) that prompt a customer to place their finger on the biometric sensor, shown below as a fingerprint scanner.


If that kind of security feature tends to "creep you out," then be aware that Apple is also considering the implementation of other types of sensors such as face recognition, hand geometry, and/or voice recognition.

  3 - BIOMETRIC FINGER SCANNER ON IPHONE - NFC, FIG 16
To enter payment information, a customer may place their finger on the biometric sensor. The iPhone may read the fingerprint and acquire payment information based on the fingerprint. For example, the iPhone may compare the fingerprint to a biometric database of fingerprints linked to payment information. The biometric database may be maintained by the merchant or by a third-party service provider and may be stored on the iPhone or on an external device accessed through the external server (#96) illustrated below in FIG. 4.


The iPhone may query the biometric database to identify the customer. Upon identification of the customer, the customer's name and address, as well as other identifying information, may be displayed within the display areas (# 342). If the information in the display areas is not correct, the merchant may select the rescan graphical element (#344) to re-execute the biometric scanning process.


However, if the information is correct, the merchant may select the pay graphical element (#228) to process a payment based on the biometric feature. For example, a customer may link their bank account or credit card information with the biometric feature stored in the biometric database. In response to selection of the graphical element, the device may query the biometric database for the payment information associated with the customer. The device may then transmit the payment information as described in FIG. 4 to obtain authorization for payment. Once the authorization has been received, an approval message may be displayed on the transaction status screen (#240) within the display window (#242). After completion of the transaction, the merchant may select the POP element (#224) to conduct another transaction.


Authorization for Payment Process

 

4- SALES TRANSACTION SYSTEM FIG 4 & 5 

Apple's patent FIG. 4 illustrates a system (#90) for conducting a sales transaction using Apple's iPhone. Due to the iPhone's portability, the sales transaction maybe conducted within a wide variety of environments. For example, the sales transaction may occur near a clothing rack within a retail store, when ordering a pizza at home or when you're on an airplane. For example, when on an airplane, the flight attendant may sell you a snack or when you're home you may pay the pizza delivery guy simply using your iPhone if the merchant is set up with this simple POP system.


The iPhone may receive identification information, such as a SKU number, UPC code, model number, serial number, or other identifier, for an article (#92). The article of merchandise may be any article generally available for sale, such as an article of clothing, an electronic device, or an article of food. In certain embodiments, the article of merchandise may represent a service item such as car wash or even a medical procedure.


NFC Retail and Credit Card Scanning Processes


Apple's patent FIG. 7 shown below illustrates a near field communication based scanning process. A merchant (#178) is shown here to be a retail store employee approaching a customer with their POP based iPhone to begin the sales transaction. The portability of the iPhone allows the sales transaction to occur anywhere within the retail store – very much like it is today at a brick and mortar Apple Store. A fixed transaction terminal, such as a cash register, is not required to complete the sales transaction – though it could be used in conjunction with a fixed transaction terminal in other embodiments.

 

5 - NFC Retail Scanning & Credit Card Processes - FIGS 7, 8, 9, 10

Apple's patent FIGS. 8, 9 and 10 illustrate the various steps taken in any given retail transaction and the various detailed screen options that the merchant will navigate through using their iPhone's POP application. While there are just too many additional detailed transaction centric screenshots to display in this initial report, managers or shop owners interested in seeing more of the potential iPhone based POP system could review this specific patent which is noted below for your convenience.


Cash Transactions Covered

 

6 - NFC IPHONE FOR CASH TRANSACTIONS WITH OPTIONAL CASH BOX ATTACHMENT - FIG 18

In addition to receiving payment by credit card, check, or biometric features, the iPhone will also be able to receive a cash payment as illustrated in patent FIG. 18. From the payment type selection screen (#198), a merchant may select the cash selection bar (#200) to display the cash payment screen (#367). The cash payment screen includes instructions (#368) that prompt the merchant to enter the amount of cash received using the graphical elements (#370). Each graphical element may correspond to a different cash denomination, such as one, five, ten, or twenty dollars. The patent covers this in extensive detail.


In-Store Smart Basket System


In Apple's patent FIG. 43 shown below we see a system (#920) that may be used to conduct a sales transaction. The system may allow a customer to scan articles and pay for the articles without the assistance of a salesperson. The system also may operate in conjunction with the merchant's security system to impede the removal of unpurchased articles from the store. For example, the articles may include security tags that can be deactivated after payment to prevent an alarm from sounding when the articles are removed from the store. Once again, the patent goes into great detail about the container and process of how this is achieved.


7 - NFC POINT OF PURCHASE BASKET SYSTEM - PART 1 
Apple's patent FIG. 47 and 50 shown below illustrate two other systems (#992 and #1030) that may be used to conduct a sales transaction using the POP enabled iPhone.


8 - NFC POINT OF PURCHASE IN-STORE BASKET SYSTEM - PART 2 - FIG. 47, 48 & 50 
9 - Misc - returns exchanges, rewards etc 
System Component Overview


10 - BLOCK DIAGRAM OF NFC COMPONENTS, FEATURES ON IPHONE - FIG 3 
Although the following videos are about of how the rest of the PC world will be using this technology later this year, I don' think you'll have any problems understanding how Apple will be integrated into 2010 MacBooks and the Apple TV for the summer or this fall. Let's just hope that Apple doesn't drop the ball here.


Overview of TransferJet: Video One


(Note that at the 1:34 mark of this video you'll see Toshiba's Apple-TV-like device next to an HDTV illustrating how easy it will be to transfer movies and other content in a snap.)


 


Overview of TransferJet: Video Two




Apple credits Gloria Lin, Amir Mikhak, Taido Nakajima, Sean Mayo and Michael Rosenblatt as the inventors of patent application 20100082444, originally filed in Q3 2008. A second Point of Purchase related patent was also published a week ago under patent number 20100082485.


An NFC Patent Bonanza


In November 2009 Patently Apple posted a major NFC related patent which was titled "Apple Developing 'Grab & Go' Application for Life in the Fast Lane." A second Apple NFC related patent on this same Grab & Go theme has been published under patent number 20100082567.


Other NFC patents include three that are Shopping Themed under numbers 20100082447, 20100082455 (IKEA) and 20100082445; Two financial industry related NFC patents covering Automated Teller Machines 20100082490 and another relating to peer-to-peer financial transactions under 20100082481; and finally two NFC related patents covering media gifting devices under patents 20100082448 and 20100082489.


Notice: Patently Apple presents only a brief summary of patents with associated graphic(s) for journalistic news purposes as each such patent application is revealed by the U.S. Patent & Trade Office. Readers are cautioned that the full text of any patent application should be read in its entirety for further details. For additional information on any patent reviewed here today, simply feed the individual patent number(s) noted in this report into this search engine.

 

Other Patently Apple NFC Reports:

 

Apple Getting Serious About Near Field Communication on the iPhone

Apple Working on Next Gen Millimeter-Wave Communication Applications

 

 

원문출처 : http://bit.ly/cUcYmm

:     

TISTORY에 Login하려면 여기를 누르세요.


ORA-20023: Missing start and end values for time model stat

Oracle 2012. 5. 15. 11:01

"ORA-20023: Missing start and end values for time model stat"

 

이는 Oracle11g License의 정책으로 인해서 생성된 Parameter설정과 연관되어 있는 Error 입니다.

 

하여 CONTROL_MANAGEMENT_PACK_ACCESS Parameter의 값을 확인 해보셔야 합니다.

 

11g에서는 기본값이 DIAGNOSTIC+TUNING 으로 되어 있는데,

 

이를, NONE으로 설정 시, Snapshot에 대한 조회 권한이 없어집니다.

  

해당 Parameter 값을 변경하기 위해서는 아래와 같이 해주시면 됩니다.

 

 

alter system set CONTROL_MANAGEMENT_PACK_ACCESS="DIAGNOSTIC+TUNING" scope=both;


 

Snapshot 정보는 계속 자동으로 생성되더라도, 위와 같이 설정이 되어 있지 않다면 이를 이용하여 분석할 수 없습니다.

 

보다 자세한 정보는 아래 Link에서 확인해보시기 바랍니다.

 


http://docs.oracle.com/cd/E11882_01/server.112/e25513/initparams037.htm

 

:     

TISTORY에 Login하려면 여기를 누르세요.


Atlanta의 지하철 MARTA와 Breeze Card

Happening 2012. 5. 7. 17:47


Atlanta에 처음으로 도착해서 공항에서 숙소까지 Suttle을 타고 인당 $17이라는 거금을 들여서 이동을 했다.


고작 20분 거리를....


그래서 대체 수단을 찾던 차에 근처에 지하철이 있음을 알게되어 이용하게된 MARTA 지하철...


이 지하철을 이용하기 위해서는 아래와 같이 "breeze"라는 교통카드를 구입해야 한다.


다른 방법도 있는거 같기는 하던데... 우리는 여행객이니까... ^^

< 교통카드 breeze >



이 교통카드를 가지고 Bus도 탈 수 있다고는 하던데... 난 지하철만 이용해 봤다.


이 카드는 아래와 같이 생긴 Ticket Kiosk를 이용해서 구매할 수 있다.



한 두 번만 탈 것이라면, Trip 형태의 요금제를 선택하면 되고, 하루에 몇 번이고 자주 타게 될 것 같다면 일자별 요금제를 선택하면


교통비용을 상당 부분 줄일 수 있다. (e,g. 오늘 하루 동안 지하철 10번 이상 탄다 : 1일 이용권 구매,     딱 한 번만 탄다 : Trip 요금제 )


지하철은 Red, Gold, Green, Blue Line으로 아주 Simple하게 구성되어 있다.


우리의 1호선, 2호선 같은 개념이고, 가고자 하는 곳이 현재의 Station을 기준으로 동,서,남,북 중 어느 곳인지만 알면 해당 방향의 


지하철을 이용하면 된다. 


Breeze 카드를 이용하고 난 뒤는??


우리의 지하철 역에서 지하철 티켓을 구매하면, 위와 같은 형태의 카드가 발급되면서 보증금이라는 것을 내지 않는가?


그래서 이용후에는 보증금을 돌려받는다. 하지만, breeze 카드는 그냥 1$을 지불하고 사는 거다. 


충전된 요금을 다 소진한 이후에는 Kiosk에서 "Tap Card" 라는 곳을 이용해서 충전해서 사용하면 된다.


알고나면 간단한데, 처음 딱 보았을 때는 선택해야할 메뉴도 많고 복잡해 보였다는.... ^^


:     

TISTORY에 Login하려면 여기를 누르세요.


Power Designer와 ERWin의 비교

Data Architecture 2012. 2. 16. 16:38



Power Designer와 ERWin Tool의 기능 비교 자료입니다.

제품을 선택함에 있어서 도움이 되시길~ ^^

'Data Architecture' 카테고리의 다른 글

12인이 말하는 ‘아키텍트의 길’  (0) 2010.11.05
OLAP의 정의와 활용  (0) 2010.09.15
The Nine Circles of Data Quality Hell  (0) 2010.08.13
:     

TISTORY에 Login하려면 여기를 누르세요.


2011년 9월말에 시행되는 개인정보 보호법에 대한 자료

IT News 2011. 8. 24. 16:27

2011년 9월말에 시행되는 개인정보 보호법에 대한 자료입니다.

자세한 내용은 PDF 파일을 읽어보면 되지만....

아직 어떤 정보를 암호화할 것인지에 법령이 확정되지 않은 상태임....

2011년 9월 초~ 중순 사이에 나올꺼라는 설이 있는데.... 법령을 빨리 공지해주어야 제대 시행될 수 있게 준비를 할 거 아닙니까~ 예~


:     

TISTORY에 Login하려면 여기를 누르세요.


Bug 5969934: EXPDP CLIENT GETS UDE-00008 ORA-31626 WHILE THE SERVER SIDE EXPORT IS OK

Oracle 2011. 8. 11. 15:24

 버그 속성


유형 B - Defect 제품 버전에서 수정됨 - (수정된 버전 없음)
중요도 2 - Severe Loss of Service 제품 버전 10.2.0.2
상태 44 - Not Feasible to fix, to Filer 플랫폼 46 - Linux x86
생성 날짜 02-Apr-2007 플랫폼 버전 LINUX AS4.0
업데이트 날짜 06-Aug-2008 기본 버그 -
데이터베이스 버전 10.2.0.2
영향을 받는 플랫폼 Generic
제품 소스 Oracle

관련 제품 표시 관련 제품


라인 Oracle Database Products 제품군 Oracle Database
영역 Oracle Database 제품 5 - Oracle Server - Enterprise Edition

Hdr: 5969934 10.2.0.2 RDBMS 10.2.0.2 DATA PUMP EXP PRODID-5 PORTID-46
Abstract: EXPDP CLIENT GETS UDE-00008 ORA-31626 WHILE THE SERVER SIDE EXPORT IS OK

*** 04/02/07 10:22 pm ***
TAR:
----

PROBLEM:
--------
1. Clear description of the problem encountered:

    EXPDP client gets UDE-00008 and ORA-31626 while the server side export is
OK.
    The export log from the server side looks OK.

    // client console log
    ------------------------------
    UDE-00008: operation generated ORACLE error 31626
    ORA-31626: job does not exist
    ORA-39086: cannot retrieve job information
    ORA-6512: at "SYS.DBMS_DATAPUMP", line 2745
    ORA-6512: at "SYS.DBMS_DATAPUMP", line 3712
    ORA-6512: at line 1
    ------------------------------

2. Pertinent configuration information (MTS/OPS/distributed/etc)

    2-node RAC

3. Indication of the frequency and predictability of the problem 

    100% reproducible at the customer's site.

4. Sequence of events leading to the problem 

    Please see attached trace files.


DIAGNOSTIC ANALYSIS:
--------------------
No error in alert log on both nodes.

The following is the output of expdp with trace=EB0300.
Deleting queue from the master table fails, same as BUG 5663241.

// expdep command line
expdp \'sys/XXX as sysdba\' trace=EB0300
DUMPFILE=work_app_dmp:20070330_expdp_err_test.dmp
FULL=y LOGFILE=work_app_dmp:20070330_expdp_err_test.log

// trace of Master Control Process
------------------------------
KUPM: 17:54:40.520: Closing job....
KUPM: 17:54:40.520: Final state in Close_job is:  COMPLETED
KUPM: 17:54:40.520: dropping master since job never started
KUPM: 17:54:40.520: keep_master_flag = FALSE
KUPM: 17:54:40.520: Delete files = FALSE
KUPM: 17:54:40.520: File subsystem shutdown
KUPM: 17:54:40.520: In set_longops
KUPM: 17:54:40.521: Work so far is: 66.80495548248291015625
KUPM: 17:54:40.521: Master delete flag is: TRUE
KUPV: 17:54:40.521: Delete request for job: SYS.SYS_EXPORT_FULL_01
KUPV: 17:54:40.535: Deleting FT job entry
KUPV: 17:54:40.535: Deleting queues
KUPC: 17:54:40.966: Deleted queue SYS.KUPC$C_1_20070330174720.
KUPC: 17:54:40.968: Error Code: -24018
KUPC: 17:54:40.968: Error Text: deleteQueue: ORA-24018: STOP_QUEUE on
SYS.KUPC$S_1_20070330174720 failed, outstanding transactions found
KUPV: 17:54:40.968: Delete request for MT: SYS.SYS_EXPORT_FULL_01
*** 17:54:51.426
KUPM: 17:54:51.426: Fixed views cleaned up
KUPM: 17:54:51.427: Log file is closed.
KUPV: 17:54:51.427: Detach request
KUPV: 17:54:51.434: Deleting FT att entry
------------------------------


Importing a table (TABLES=test_tbl_2) with the dump file
(20070330_expdp_err_test.dmp)
is successfully done, which means that the export is OK regarding the table
(test_tbl_2).

// impdp command line
impdp \'sys/XXX as sysdba\' DUMPFILE=work_app_dmp:20070330_expdp_err_test.dmp

TABLES=test_tbl_2 LOGFILE=work_app_dmp:20070330_impdp_test.log


WORKAROUND:
-----------
None.

RELATED BUGS:
-------------
BUG 5416274
BUG 5663241 (duplicate bug of BUG 5416274)

REPRODUCIBILITY:
----------------
reproduced twice at customer's site.
CT says every time expdp was done, this phenomenon occured.

TEST CASE:
----------

STACK TRACE:
------------

SUPPORTING INFORMATION:
-----------------------
I will be loading the following files:
dbram01_dm00_19485.trc
dbram01_dw01_19569.trc
expdp.txt
imp.txt

24 HOUR CONTACT INFORMATION FOR P1 BUGS:
----------------------------------------

DIAL-IN INFORMATION:
--------------------

IMPACT DATE:
------------

*** 04/02/07 10:26 pm ***
*** 04/02/07 10:44 pm ***
*** 04/02/07 10:45 pm ***
*** 04/10/07 01:09 am ***
*** 04/10/07 01:09 am ***
*** 04/10/07 01:20 am ***
*** 04/10/07 01:20 am *** (CHG: Sta->11)
*** 04/10/07 01:20 am ***
*** 04/10/07 01:20 am ***
*** 05/06/07 10:57 pm ***
*** 05/22/07 05:02 pm ***
*** 05/31/07 11:52 pm ***
*** 06/13/07 06:39 pm ***
*** 06/18/07 02:38 am ***
*** 06/18/07 02:38 am ***
*** 06/18/07 02:38 am ***
*** 06/20/07 03:41 am ***
*** 06/20/07 03:50 am ***
*** 07/16/07 06:48 pm ***
*** 07/24/07 06:48 pm ***
*** 08/02/07 09:40 pm ***
*** 08/21/07 06:45 pm ***
*** 09/25/07 07:46 pm ***
*** 10/15/07 06:39 pm ***
*** 11/02/07 05:06 pm ***
*** 11/15/07 01:48 am ***
*** 03/06/08 09:52 pm ***
*** 03/20/08 08:17 am ***
*** 03/20/08 08:17 am ***
*** 05/13/08 11:26 am ***
*** 07/08/08 06:35 am ***
*** 08/06/08 08:35 am ***
*** 08/06/08 09:21 am *** (CHG: Sta->44)
*** 08/06/08 09:21 am ***
In the 10.2.0.2 release, there were a number of problems that caused the
expdp and impdp clients to exit prematurely, interpreting a nonfatal error as
a fatal one, giving the appearance that the job had failed when it hadn't. In
fact, inspection of the log file, if one was specified for the job, showed
that the job ran successfully to completion. Often a trace file written by
one of the Data Pump processes would provide more detail on the error that
had been misinterpreted as a fatal one. Many of these errors involved the
queues used for communication between the Data Pump processes, but there were
other issues as well.

With each subsequent release, these problems have been addressed, and the
client has become more robust and rarely, if ever, runs into situations like
this. However, this is the result of dozens of bug fixes in subsequent
releases, some in Data Pump and some in supporting layers. It's impossible to
know, at this point, what combination of bug fixes would address this
specific failure, and even if that was possible, it wouldn't address other
possible failures that look very similar on the client side.

Relying on information in the log file is one way to verify that the job
actually completed successfully. Problems like this one became much more
intermittent by the 10.2.0.4 and 10.2.0.5 releases and are rarely, if ever,
seen in 11.1 or later.



출처 : Oracle Support


:     

TISTORY에 Login하려면 여기를 누르세요.