Support #8109

SCP ID :##4308 ##] : M2U Slowly - make other session locked

Added by Nurul Akmal almost 7 years ago. Updated over 6 years ago.

Status:Closed - End of life cycleStart date:November 30, 2017
Priority:NormalDue date:
Assignee:Avatar?id=2607&size=14Rayvandy Gabbytian % Done:

0%

Category:-Spent time:-
Target version:-

Description

Hi Gabby,
Kindly attend below request.

Can you investigate why when m2u run this query  

“select ibaccount0_.USER_ID as USER2_1_, ibaccount0_.ACCOUNT_NUMBER as ACCOUNT1_1_, ibaccount0_.ACCOUNT_NUMBER as ACCOUNT1_35_0_, ibaccount0_.USER_ID as USER2_35_0_, ibaccount0_.ACCOUNT_TYPE as ACCOUNT3_35_0_, ibaccount0_.ACCOUNT_CODE as ACCOUNT4_35_0_, ibaccount0_.ACCOUNT_NICKNAME as ACCOUNT5_35_0_, ibaccount0_.ACCOUNT_CURRENCY as ACCOUNT6_35_0_, ibaccount0_.ACCOUNT_HOLDER_NAME as ACCOUNT7_35_0_, ibaccount0_.ACCOUNT_RULE as ACCOUNT8_35_0_ from dbo.IB_CUST_ACCOUNTS ibaccount0_ where ibaccount0_.USER_ID in (select this_.USER_ID from dbo.IB_CUST_PROFILE this_ where this_.CP_CUST_NO=?)

This data query for investigation as penril needed.

Last SQL Operation: 
SQL Fetch
SQL: 
select this_.USER_ID as USER1_450_1_, this_.USER_NAME as USER2_450_1_, this_.USER_DOB_BRD as USER3_450_1_, this_.USER_EMAIL as USER4_450_1_, this_.USER_GENDER as USER5_450_1_, this_.USER_RACE as USER6_450_1_, this_.USER_HOME_PHONE as USER7_450_1_, this_.USER_OFFICE_PHONE as USER8_450_1_, this_.USER_MOBILE_PHONE as USER9_450_1_, this_.USER_TAC_PHONE as USER10_450_1_, this_.USER_ADDR1 as USER11_450_1_, this_.USER_ADDR2 as USER12_450_1_, this_.USER_ADDR3 as USER13_450_1_, this_.USER_ADDR4 as USER14_450_1_, this_.USER_ADDR5 as USER15_450_1_, this_.USER_ACCESS_NO as USER16_450_1_, this_.USER_TYPE as USER17_450_1_, this_.UPDATED_BY as UPDATED18_450_1_, this_.UPDATED_DATE as UPDATED19_450_1_, this_.USER_CITY as USER20_450_1_, this_.USER_STATE as USER21_450_1_, this_.USER_POSTCODE as USER22_450_1_, this_.USER_COUNTRY as USER23_450_1_, this_.USER_AGE_RANGE as USER24_450_1_, this_.USER_INCOME_RANGE as USER25_450_1_, this_.USER_MARITAL_STATUS as USER26_450_1_, this_.USER_EMPLOY_STATUS as USER27_450_1_, this_.USER_EDUCATION_LEVEL as USER28_450_1_, this_.USER_DISPLAY_NAME as USER29_450_1_, this_.INSIDER as INSIDER450_1_, this_.INQUIRY_CODE as INQUIRY31_450_1_, this_.MOTHER_MAIDEN_NAME as MOTHER32_450_1_, this_.NATIONALITY as NATIONA33_450_1_, this_.BUMI as BUMI450_1_, this_.RESIDENCE as RESIDENCE450_1_, this_.RELIGION_CODE as RELIGION36_450_1_, this_.LANGUAGE as LANGUAGE450_1_, this_.MARITAL_DATE as MARITAL38_450_1_, this_.CUST_STATUS as CUST39_450_1_, this_.CUST_STATUS_DATE as CUST40_450_1_, this_.DECEASED as DECEASED450_1_, this_.DECEASED_DATE as DECEASED42_450_1_, this_.HOLD_MAIL_CODE as HOLD43_450_1_, this_.PROMO_MAIL_CODE as PROMO44_450_1_, this_.ADDRESS_SEQ as ADDRESS45_450_1_, this_.START_RELATIONSHIP as START46_450_1_, this_.REVIEW_DATE as REVIEW47_450_1_, this_.CREATION_DATE as CREATION48_450_1_, this_.RETENTION as RETENTION450_1_, this_.CONSITUTION as CONSITU50_450_1_, this_.PLACE_OF_BIRTH as PLACE51_450_1_, this_.CUST_SEGMENT_CODE as CUST52_450_1_, this_.NO_OF_EMP as NO53_450_1_, this_.HIGH_RISK as HIGH54_450_1_, this_.HIGH_RISK_CODE as HIGH55_450_1_, this_.STAFF_FLAG as STAFF56_450_1_, this_.STAFF_ID_NO as STAFF57_450_1_, this_.DURATION_STAY_PRE_ADD as DURATION58_450_1_, this_.HOUSE_OWNER_CODE as HOUSE59_450_1_, this_.TYPE_DWELLING as TYPE60_450_1_, this_.NO_OF_DEPENDENTS as NO61_450_1_, this_.BUSS_PREMISE_CODE as BUSS62_450_1_, this_.BUSSINESS_TYPE as BUSSINESS63_450_1_, this_.BUSS_OPER_HOURS as BUSS64_450_1_, this_.ID_NO as ID65_450_1_, this_.ID_TYPE as ID66_450_1_, this_.SALUTATION as SALUTATION450_1_, this_.OFFICE_CONTACT_NAME as OFFICE68_450_1_, this_.TOKEN as TOKEN450_1_, this_.REG_REF_NO as REG70_450_1_, this_.PRIMARY_ACC_NO as PRIMARY71_450_1_, this_.FAX as FAX450_1_, this_.FAX_CONTACT_NAME as FAX73_450_1_, this_.YEAR as YEAR450_1_, this_.ANNUAL_TURNOVER as ANNUAL75_450_1_, this_.SECTOR as SECTOR450_1_, this_.NO_FULLTIME_EMP as NO77_450_1_, this_.CLIENT_TYPE as CLIENT78_450_1_, this_.MK_PENDING as MK79_450_1_, this_.BEFORE_VALUE as BEFORE80_450_1_, this_.AFTER_VALUE as AFTER81_450_1_, this_.TRNX_MODE as TRNX82_450_1_, this_.USER_DOB_BRD_UPDATE_FLAG as USER83_450_1_, this_.CP_CUST_NO as CP84_450_1_, this_.REMARK_DESC as REMARK85_450_1_, this_.MOBILE_NO_FLAG as MOBILE86_450_1_, this_.GROUP_ID as GROUP87_450_1_, this_.ORG_ID as ORG88_450_1_, this_.ROLE_ID as ROLE89_450_1_, mainprofil1_.USER_ID as USER1_458_0_, mainprofil1_.ACCOUNT_ID as ACCOUNT2_458_0_, mainprofil1_.USER_ALIAS as USER3_458_0_, mainprofil1_.CHANNEL_ID as CHANNEL4_458_0_, mainprofil1_.PASSWORD_ERROR_COUNT as PASSWORD5_458_0_, mainprofil1_.USER_STATE as USER6_458_0_, mainprofil1_.LAST_LOGIN_DATE as LAST7_458_0_, mainprofil1_.MODIF_TIME as MODIF8_458_0_, mainprofil1_.CREATION_DATE as CREATION9_458_0_, mainprofil1_.LAST_CHANGE_PASSWORD_DATE as LAST10_458_0_, mainprofil1_.TAC_TRNX_ID as TAC11_458_0_, mainprofil1_.TAC_GENERATED_DATE as TAC12_458_0_, mainprofil1_.TAC_ERROR_COUNT as TAC13_458_0_ 
from dbo.IB_CUST_PROFILE this_ 
inner join 
dbo.IB_USER mainprofil1_ on this_.USER_ID=mainprofil1_.USER_ID where lcase(mainprofil1_.USER_ALIAS)=? and mainprofil1_.CHANNEL_ID=? and mainprofil1_.USER_STATE<>?

Last SQL Operation: 
SQL Execute
SQL: 
update dbo.IB_CUST_PROFILE set USER_NAME=?, USER_DOB_BRD=?, USER_EMAIL=?, USER_GENDER=?, USER_RACE=?, USER_HOME_PHONE=?, USER_OFFICE_PHONE=?, USER_MOBILE_PHONE=?, USER_TAC_PHONE=?, USER_ADDR1=?, USER_ADDR2=?, USER_ADDR3=?, USER_ADDR4=?, USER_ADDR5=?, USER_ACCESS_NO=?, USER_TYPE=?, UPDATED_BY=?, UPDATED_DATE=?, USER_CITY=?, USER_STATE=?, USER_POSTCODE=?, USER_COUNTRY=?, USER_AGE_RANGE=?, USER_INCOME_RANGE=?, USER_MARITAL_STATUS=?, USER_EMPLOY_STATUS=?, USER_EDUCATION_LEVEL=?, USER_DISPLAY_NAME=?, INSIDER=?, INQUIRY_CODE=?, MOTHER_MAIDEN_NAME=?, NATIONALITY=?, BUMI=?, RESIDENCE=?, RELIGION_CODE=?, LANGUAGE=?, MARITAL_DATE=?, CUST_STATUS=?, CUST_STATUS_DATE=?, DECEASED=?, DECEASED_DATE=?, HOLD_MAIL_CODE=?, PROMO_MAIL_CODE=?, ADDRESS_SEQ=?, START_RELATIONSHIP=?, REVIEW_DATE=?, CREATION_DATE=?, RETENTION=?, CONSITUTION=?, PLACE_OF_BIRTH=?, CUST_SEGMENT_CODE=?, NO_OF_EMP=?, HIGH_RISK=?, HIGH_RISK_CODE=?, STAFF_FLAG=?, STAFF_ID_NO=?, DURATION_STAY_PRE_ADD=?, HOUSE_OWNER_CODE=?, TYPE_DWELLING=?, NO_OF_DEPENDENTS=?, BUSS_PREMISE_CODE=?, BUSSINESS_TYPE=?, BUSS_OPER_HOURS=?, ID_NO=?, ID_TYPE=?, SALUTATION=?, OFFICE_CONTACT_NAME=?, TOKEN=?, REG_REF_NO=?, PRIMARY_ACC_NO=?, FAX=?, FAX_CONTACT_NAME=?, YEAR=?, ANNUAL_TURNOVER=?, SECTOR=?, NO_FULLTIME_EMP=?, CLIENT_TYPE=?, MK_PENDING=?, BEFORE_VALUE=?, AFTER_VALUE=?, TRNX_MODE=?, USER_DOB_BRD_UPDATE_FLAG=?, CP_CUST_NO=?, REMARK_DESC=?, MOBILE_NO_FLAG=?, GROUP_ID=?, ORG_ID=?, ROLE_ID=? where USER_ID=?

Last SQL Operation: 
SQL Close
SQL: 
select ibusersecu0_.USER_ID as USER1_33_0_, ibusersecu0_.IB_SESSION_ID as IB2_33_0_, ibusersecu0_.IMAGE as IMAGE33_0_, ibusersecu0_.QUESTION_1 as QUESTION4_33_0_, ibusersecu0_.ANSWER_1 as ANSWER5_33_0_, ibusersecu0_.QUESTION_2 as QUESTION6_33_0_, ibusersecu0_.ANSWER_2 as ANSWER7_33_0_, ibusersecu0_.QUESTION_3 as QUESTION8_33_0_, ibusersecu0_.ANSWER_3 as ANSWER9_33_0_, ibusersecu0_.CAPTION as CAPTION33_0_, ibusersecu0_.NUM_OF_SEC_ATTEMPTS as NUM11_33_0_, ibusersecu0_.NUM_OF_ATM_ATTEMPTS as NUM12_33_0_ 
from dbo.IB_USER_SECURITY ibusersecu0_ where ibusersecu0_.USER_ID=?

“
It’s make other session locked in m2u.

Thank you.

image001.jpg (49.6 KB) Nurul Akmal, November 30, 2017 14:48

image002.jpg (25.9 KB) Nurul Akmal, November 30, 2017 14:48

History

#1 Updated by Zahir Abd Latif over 6 years ago

  • Status changed from New - Begin Life Cycle to Closed - End of life cycle

Gabby, Dec 18, 2017 11:19 AM:-

Dear Pak Paulus,

Regarding SMS_NOTIFICATION table, Penril suggests to remove that table because the data inside is never being used.

It means that M2U / MSS application never utilised that table for the purpose of reading / display.
Also based on our experience, we never used the data for the purpose of troubelshooting issue in production.
Why does the table exist in the first place? Because, we thought that the data might be useful for reconciliation purpose with telecommunication provider (incase sms doesn’t reach customer, etc). However, it turns out the table is not being used. Correct me if I’m wrong.

So we still suggest to remove it, in order to reduce the table size, and easier maintenance in the future.
Please kindly reconsider it again to remove.

Below is the sample data in development.

Issue closed in SCP.

Also available in: Atom PDF