Support #5303
[SCP ID :##2661##] : RFI W1 154 Trx Credit Error - 5.5.2015
| Status: | Closed - End of life cycle | Start date: | May 05, 2015 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: |  Zahir Abd Latif | % Done: | 100% | |
| Category: | MY IBG | Spent time: | - | |
| Target version: | - |
Description
Hi,
Kindly attend below request:
We encountered Credit Error status again for RFI W1 crediting today @ 9.30am.
Total 154 transactions (RM853,551,79) were unsuccessful with "Credit Error" status with rejection description as "Unable to locate profile".
Hence all these 154 transactions were not credited. Has randomly checked on the accounts# in phoenix and it were a valid account type.
We seek your assistance to look into the root cause immediately and advise on the next action.
Fyi, the next window for RFI W2 crediting will be at 12.30pm.
History
#1
Updated by Tan Lee Yong over 9 years ago
- Assignee changed from Hafizudin MD to Ngoh Chee Ping
Hafiz is MIA. So, assign to Chee Ping to look into this issue.
#2
Updated by Ngoh Chee Ping over 9 years ago
- Status changed from New - Begin Life Cycle to Finished Development
- Assignee changed from Ngoh Chee Ping to Zahir Abd Latif
- % Done changed from 0 to 100
In the log file i found there is a period of downtime for phoenix database. Below are the phoenix error message. This is the root cause for this issue. After this period of time, phoenix database is up and running, that why RFI w2 does not have this problem.
JNDI: PhoenixDS
exec atm.dbo.psp_ex_main3 41,'20150505','20150505',null,'Y',null,'N','20150505093017275',null,'N','N',null,null,null,61,null,null,'RM','RM','53482',null,null,null,0,null,null,null,null,null,null,null,null,null,null,null,'3.0',6,'',null,'IB',null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,null,null
Profile query: {call crystal.dbo.sp_comp_det('010103001619')}
Return Header = {ErrorMessage=Database 'phoenix' has not been recovered yet - please wait and try again., ServicesID=41, ReferenceNo=20150505093017275, Version=3.0, TranCode=61, ResponseCode=9999}
<May 5, 2015 9:30:17 AM MYT> <Error> <ALSB Logging> <000000> < [Logging, Logging_response, Outbound Error Logging, RESPONSE] <Msg>
<MsgHeader>
<ErrorMessage>Database 'phoenix' has not been recovered yet - please wait and try again.</ErrorMessage>
<ServicesID>41</ServicesID>
<ReferenceNo>20150505093017275</ReferenceNo>
<Version>3.0</Version>
<TranCode>61</TranCode>
<ResponseCode>9999</ResponseCode>
</MsgHeader>
<MsgBody>
<Records/>
</MsgBody>
</Msg>>
#3
Updated by Zahir Abd Latif over 9 years ago
- Status changed from Finished Development to Closed - End of life cycle