CD2 issues continue - table initdb inserts only fraction of data

[NoorRashid]

Hi Folks!

After running into the issue of no data being inserted after syncdb, I reinstalled everything, including python, DAP client, PostgreSQL and upgraded to tsv2py 0.6.2.

That seemed to solve the issue of *no* data being inserted into my PostgreSQL db. However, now I notice that the "courses" table only inserts 215 rows, where there should over 3000. Is this a change in policy to only return most recent courses?

I also tried to initdb the enrolments (we have enrolled over 250k students) table and similarly only a fraction of the data has been retrieved (3k rows returned). I previously had to drop everything manually in order to diagnose the issues, and now face the prospect of only a tiny % of the data being returned.

Have attached the log file below. 

I would sincerely appreciate any and all help - everything seems to be going wrong for us at the moment!

Best wishes,

Noor

[LeventeHunyadi]

One obvious reason for the difference that I can think of is that you are running replication for the wrong root account. Isolation for DAP API (a.k.a. CD 2) is at the root account level, i.e. if you query data for a root account, you won't see data from other root accounts. If your institution spans multiple root accounts, make sure you are replicating the right one. (Many school districts and universities have several root accounts.)

[NoorRashid]

Hi Levente!

Thank you as always for your prompt and helpful replies - you are a lifesaver. However, in this case I am very puzzled. The only changes I have made were dropping the existing tables and running the exact same .bat script I use to automate the initdb and syncdb processes.

How would one confirm if the issue is a root account issue? Would this be at the identity level (which was used to generate the keys)? Are there any arguments to chain to the DAP CLI commands?

Many many thanks as always,

Noor