AIRBUS 310 FLT CREW HAS TRACK AND HDG DEV DURING DEP FROM LFPG.

Narrative

DEP STATED THAT OUR AIRPLANE BEGAN A TURN PREMATURELY AFTER PG264 (A MANDATORY FLYOVER POINT AND PG266) ON THE OKASI 1B DEP; RWY 26R; LFPG. MAINT HAD TO RELOAD DATABASE PRIOR TO DEP. ALL DATA POINTS WERE PROPERLY ENTERED; VERIFIED IN BOTH PRIMARY AND SECONDARY FLT PLANS. THERE WAS NO ERROR IN DATA ENTRY OR PERFORMANCE ERROR NOTED IN THE FLT PLAN OR ACFT 'NAVING.' PLEASE NOTE DIFFERENCE BTWN COMMERCIAL CHART PAGE X AND INITIAL CLB PAGE Y. NOTE: FMS DATABASE LOADS PG264 (HARD POINT); PG266; PG289; DOPAP; ODEBU; OKASI (PAGE X). FMS WILL LEAD PG266. ON PAGE Y; INITIAL CLB PLAN VIEW; THERE IS AN ADDITIONAL POINT; PG265. THIS IS NOT IN DATABASE. SHOULD PG265 BE IN DATABASE? SHOULD IT BE A 'HARD POINT?' OR; WAS CTLR MISTAKEN? I DO NOT EXPECT ANYTHING TO COME OF THIS. CTLR ADVISED THAT ACFT WAS TURNING PREMATURELY AFTER PG264; WHICH IS A MANDATORY FLYOVER POINT AND THERE WAS NO PROB THERE. FROM THAT POINT; THE FMS WOULD NORMALLY LEAD POINT PG266; THE NEXT POINT IN THE DATABASE; BUT CTLR THOUGHT IT WAS TURNING EARLY. WE USE COMMERCIAL CHARTS AND PROCS NOW. COULD THERE BE A PROB IN THE CHARTED POINTS OR IN THE DATABASE? WHEN WE CAME TO THE ACFT PRIOR TO DEP; THE FMS WOULD NOT LOAD. MAINT HAD PUT A NEW DATABASE IN PRIOR TO OUR ARR AT THE ACFT. THEY HAD TO COME OUT AND UPLOAD THE DATABASE AGAIN PRIOR TO DEP. I DO NOT THINK THIS IS CAUSAL; BUT; A POTENTIAL ISSUE. EVERYTHING WAS THOROUGHLY VERIFIED IN THE FMS PRIOR TO DEP AND BRIEFED AND VERIFIED DURING THE EVENT; NO ABNORMALITIES WERE NOTED IN EITHER THE DATA IN THE FMS OR ACFT PERFORMANCE.