faq:pervasive_troubleshooting
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
faq:pervasive_troubleshooting [2019/11/21 15:13 (4 years ago)] – created kevin | faq:pervasive_troubleshooting [2020/06/25 11:11 (4 years ago)] (current) – kevin | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Pervasive Troubleshooting ====== | + | ====== Pervasive |
- | Use this document to give you ideas on where to look for errors | + | Use this document to give you ideas on where to look for when experiencing a crashing Pervasive SQL service. This article is written expecting you to know how to run the PCC (Pervasive Control Center) or ZenCC and have a technical background in System Five. If you are unsure what to do, contact Windward Software customer care. |
+ | <note tip>This article was written with Pervasive SQL version 12 in mind. Many of the issues will pertain to Actian Zen PSQL 14 which was a rebrand by Actian Software. | ||
===== Questions to Ask ===== | ===== Questions to Ask ===== | ||
+ | * What is the plan to restore from backup? | ||
+ | * It can take time to rebuild a new virtual machine and to restore from backup. | ||
+ | * Restoring from last known backup gets the business back into operation. | ||
* What has changed? | * What has changed? | ||
* Groom the logs and ask questions to understand service restarts or messages. | * Groom the logs and ask questions to understand service restarts or messages. | ||
- | * When was the last known good server state? | + | * What date and time was the last known good server state? |
- | * When was the last known good backup? | + | * What date and time was the last known good backup |
- | * What is the plan to restore from backup? (Do this while you continue to trouble shoot) | + | |
- | ===== Known Pervasive | + | ===== Known Service Crashing Culprits ===== |
- | If the Peravsive | + | If the Pervasive |
- | - Unpack fresh set of DDF's as a corrupt view can cause the PSQL engine to crash without error in log | + | |
+ | | ||
- Checking the PVSW Logs. PCC and Help menu. (This can give you an idea of why the service or what file or application is causing an issue) | - Checking the PVSW Logs. PCC and Help menu. (This can give you an idea of why the service or what file or application is causing an issue) | ||
- Is the Pervasive database version patched and up to date. (Verify service pack and version) | - Is the Pervasive database version patched and up to date. (Verify service pack and version) | ||
- If receiving a "Roll forward recovery" | - If receiving a "Roll forward recovery" | ||
- | - A corrupt database can cause a crash. | + | - An operating system patch or pending |
- | - A operating system patch or pending patch can cause crashing. Restore | + | |
===== Trouble Shooting ===== | ===== Trouble Shooting ===== | ||
* Test network transmission of larger packet size as corrupt packets of data can cause failure | * Test network transmission of larger packet size as corrupt packets of data can cause failure | ||
- | * At command prompt ping -t -s2000 (Is there packet loss?) | + | * At command prompt |
* Post and search the symptoms on [[https:// | * Post and search the symptoms on [[https:// | ||
* Capture the PVSW log file to be able to show other technicians. | * Capture the PVSW log file to be able to show other technicians. | ||
- | | + | {{: |
+ | | ||
+ | * Using the PCC you can go table by table and view to find the offending file that will crash the database service. | ||
+ | * Consider stopping the relational service which will stop SQL support. This may help isolate the issue to the application causing the problem. |
faq/pervasive_troubleshooting.1574377994.txt.gz · Last modified: 2019/11/21 15:13 (4 years ago) by kevin