Chinese characters being sent to TmpV2: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
Line 7: Line 7:
As of [[CCMDB.mdb_Change_Log_2013#ver_2013-08-12]] all data incl. tmp will be sent to [[Centralized_data.mdb]]. For the moment this is in duplication of sending to [[TmpV2_1.mdb]], but it will replace that process eventually. In the meantime I would be interested to see if, in the cases where Chinese characters are being sent, ''both'' targets get Chinese characters. Will check as I see an update in the occurrence log. Ttenbergen 11:03, 2013 August 29 (CDT)
As of [[CCMDB.mdb_Change_Log_2013#ver_2013-08-12]] all data incl. tmp will be sent to [[Centralized_data.mdb]]. For the moment this is in duplication of sending to [[TmpV2_1.mdb]], but it will replace that process eventually. In the meantime I would be interested to see if, in the cases where Chinese characters are being sent, ''both'' targets get Chinese characters. Will check as I see an update in the occurrence log. Ttenbergen 11:03, 2013 August 29 (CDT)
{{Discussion}}
{{Discussion}}
if there is a problem and Pagasa has to edit or changed errors especially if there are lots of edits or changes that need to be made.  It is extremely slow to work with. This is a big concern!.[[User:TOstryzniuk|Trish Ostryzniuk]] 11:08, 2013 August 29 (CDT)
*if there is a problem and Pagasa has to edit or changed errors especially if there are lots of edits or changes that need to be made.  It is extremely slow to work with. This is a big concern!.[[User:TOstryzniuk|Trish Ostryzniuk]] 11:08, 2013 August 29 (CDT)


== Occurrence Log ==
== Occurrence Log ==

Revision as of 11:09, 2013 August 29

Intermittently, contents of all the com_var field (eg Postal code or overstay color) in TMPV2 are corrupted/scrambled into "Chinese characters" on send.

This started 2013-06-05. Initially the thought was that doing a compact on the data file before sending would fix the problem. CCMDB.mdb was updated as part of CCMDB.mdb_Change_Log_2013#ver_2013-06-10 to compact/repair to run each time the program is started. However, there appear to have been cases where the problem has happened even right after a compact.

Troubleshooting Log

As of CCMDB.mdb_Change_Log_2013#ver_2013-08-12 all data incl. tmp will be sent to Centralized_data.mdb. For the moment this is in duplication of sending to TmpV2_1.mdb, but it will replace that process eventually. In the meantime I would be interested to see if, in the cases where Chinese characters are being sent, both targets get Chinese characters. Will check as I see an update in the occurrence log. Ttenbergen 11:03, 2013 August 29 (CDT) Template:Discussion

  • if there is a problem and Pagasa has to edit or changed errors especially if there are lots of edits or changes that need to be made. It is extremely slow to work with. This is a big concern!.Trish Ostryzniuk 11:08, 2013 August 29 (CDT)

Occurrence Log

  1. August 20.13
  2. August 14.13
    • HSC/B3-D5 Batch#33
      • no problems for a while, but today Lou had a chinese character in her send... I emailed her and Pagasa to find out if they have any idea why there were chinese characters... Ttenbergen 15:54, 2013 August 15 (CDT)
        • comment from Lou: "When I came in to work Wed, I remember now that I did not fully shut down computer but just did my “News and Backup” and logged off. (Went to the biffy and forgot to totally shut down). I only noticed when I came in next day and didn’t have such a long start up time. Maybe this was the issue as it wouldn’t have booted up with the latest changes in CMDB or server?
  3. July 3.13
    • STB_CICU & HSC_B3/D5:
      • Trish and Sheila R have Resent the files from backup for:
        • STB CICU batch 21
        • HSC B3/D5 batch 27
        • Deleted files with chinese in comment column in tmpV2.
  4. June 11.13
    • GRA_N3, HSC_B3/D5
  5. June 6.13
    • VIC_S4
  6. June 5.13
    • HSC_SICU,(not sure why SICU affected)
    • GRA_N3, STB_E5