Results 1 to 11 of 11
  1. #1
    Join Date
    Mar 2017
    Posts
    8

    Unanswered: PSQL v8 export with PCC

    Hello,

    I have recently been in charge of shutting down an old system used by the company.
    Before that, I need to export all the data into a read-only database for report purpose (ie. Access).

    I am completly new to Pervasive SQL (v8) and its components.

    I read into the documentation that the databases can be exported into text files using Pervasive Control Center (PCC).
    And it is exactly what I am trying to do.

    As a domain admin, I am able to open the PCC and display databases and tables.
    Then, right click on database > Tasks > Export data
    I get a box with the database name and credential fields (if needed).
    I let the credential blank as I do not know any, and click on Next.
    A warning box appear and says 'incorrect login'.

    How is it possible that I have access to all the data in PCC and Pervasive Data Manager, but I can't export?

  2. #2
    Join Date
    Mar 2017
    Posts
    8
    Weard thing, it is working on tables from a different database, but not on the one I was testing until now.

  3. #3
    Join Date
    Mar 2017
    Posts
    8
    So, when I run the export wizard on a hudge table: it stops randomly after 1 to 3 minutes.

    Export incomplete. Would you like to delete the partial exported file?

    Error while running Wizard.
    Error The remote procedure call failed. (0x800706be)

    What am I doing wrong?

  4. #4
    Join Date
    Dec 2001
    Posts
    1,115
    Provided Answers: 5
    PSQL v8 is very old and hasn't been supported in many years. THe export tool was built as a COM object and had some issues. I wouldn't be surprised if it has problems.

    Can you open the "huge" table in the PCC in "Text" mode? Does it work or does it fail to bring out all of the records?
    Have you tried another tool to export the table? Any ODBC tool should work including my own DataXtraction. Even if the export fails, it should give a better error that might help you fix it.
    Mirtheil Software
    Certified Pervasive Developer
    Certified Pervasive Technician
    Custom Btrieve/VB development
    http://www.mirtheil.com
    I do not answer questions by email. Please post on the forum.

  5. #5
    Join Date
    Mar 2017
    Posts
    8
    Thank you for your reply mirtheil.

    Yes, I am able to open and see the records of the tables.
    Because the wizard was not working, I have already looked into the ODBC way.

    I successfully made the connexion between PSQL v8 and Access 2016 using ODBC.
    When I can easily import small tables using Access, other tables display the following error:
    ODBC-call failed---[Pervasive][ODBC Client Interface][LNA][Pervasive][ODBC Engine Interface][Data Record Manager]No such index. #-1404
    I suspect that tables parameters or configuration in PSQL can't be imported properly into Access?

  6. #6
    Join Date
    Dec 2001
    Posts
    1,115
    Provided Answers: 5
    That's very possible. Access has traditionally been very particular when it comes to indexes and importing data. It could also be that the indexes aren't properly defined in the Pervasive DB itself. THis is common in older databases where ODBC compatibility wasn't needed (or thought about).
    Instead of Importing, have you tried Linking the table?
    Mirtheil Software
    Certified Pervasive Developer
    Certified Pervasive Technician
    Custom Btrieve/VB development
    http://www.mirtheil.com
    I do not answer questions by email. Please post on the forum.

  7. #7
    Join Date
    Mar 2017
    Posts
    8
    Yesterday, I tried to remove several indexes of this 2Go table but it froze during the process. I had to cancel the saving window this morning.

    I will try to link the table instead and come back with the result.

  8. #8
    Join Date
    Mar 2017
    Posts
    8
    As I can't use the computer that has Access right now, I was looking at your soft DataXtraction.
    I did the exact same thing: connection using ODBC, working well for several small databases.
    And then, on the main database:
    Click image for larger version. 

Name:	error.PNG 
Views:	5 
Size:	10.1 KB 
ID:	17304

    It looks like we can't select the table because of the caracter "-" in DAILHIST-T1?

    edit: After changing the table name in order to remove the "-" caracter.
    Click image for larger version. 

Name:	error2.PNG 
Views:	3 
Size:	7.8 KB 
ID:	17305
    Not enough memory.

    Which memory are we talking about?
    Last edited by Rouky; 03-09-17 at 15:38.

  9. #9
    Join Date
    Dec 2001
    Posts
    1,115
    Provided Answers: 5
    How big is the table you are trying to export?
    Does it have a large number of fields?
    Does it have variable length fields?

    The error is most likely coming back from the ADO interface DataXtraction is using to access the database.
    Mirtheil Software
    Certified Pervasive Developer
    Certified Pervasive Technician
    Custom Btrieve/VB development
    http://www.mirtheil.com
    I do not answer questions by email. Please post on the forum.

  10. #10
    Join Date
    Mar 2017
    Posts
    8
    Columns 62
    Record length 200
    Page size 4096
    Number of records 6 072 096
    Number of duplicate Ptrs 9
    Variable records No

    Click image for larger version. 

Name:	screen.PNG 
Views:	3 
Size:	5.4 KB 
ID:	17307

    The 2,5GB .DTA file seems to contain 2 tables. One of them is the DAILHISTT1 I am trying to export.

  11. #11
    Join Date
    Mar 2017
    Posts
    8
    I finally installed PSQL v8 on my Windows 10 computer.
    After few errors during installation, I launched the Export Wizard and it went well.
    I got my data in a SDF format.
    Thanx for your help.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •