All you need to help people in your area to find their polling station.
Our polling station finder uses data sent to us from councils.
**If you work for a council you can send us data by emailing
[pollingstations@democracyclub.org.uk](mailto:pollingstations@democracyclub.org.uk).**
Please send us new data for each election, or confirm that it has not changed.
By default we direct users to their polling station using the polling station postcode.
Providing co-ordinates or UPRNs for the polling stations allows us to provide more accurate directions.
### Exporting from your EMS
Some suppliers have added exports in their software to make it easy to email us the data.
#### Xpress
The Democracy Club report is in "Express Management" under "Elections/Exports"
and the report is called "EC & Democracy Club Polling Place Lookup".
#### Democracy Counts Elector8
For Elector8 Users, go to "Planning & Reporting" then "Category Searches"
and select both of the following:
* Democracy Club - Polling Districts
* Democracy Club - Polling Stations
Right click on the data grid and click "export".
#### Idox Eros (formerly Halarose)
There is a Knowledge Base Article (KBA) about how to export data. Click on
"Democracy Club" in the tag cloud or use this link:
[https://www.halarose.co.uk/helpspot/index.php?pg=kb.page&id=384](https://www.halarose.co.uk/helpspot/index.php?pg=kb.page&id=384)
#### Idox Strand
Unfortunately Idox haven't provided an easy export from Strand yet,
but they are working on it.
It's worth emailing [pollingstations<EMAIL_ADDRESS>anyway, as we might be able to work with your GIS team on getting data.
### Data changes
We only use data sent to us for the elections you tell us it's valid for.
If we're not sure we don't re-use data between elections, and we will email you asking
for updates.
For last minute changes, including on polling day, you can email us and we will make
changes to the data on the live site. In the worse case we can remove all your data from
the site very quickly, just get in touch.
### Data restrictions
We don't need personal data to run the polling station finder but we may need
UPRNs or data from some of Ordnance Survey's products depending on the type of
data you are able to provide us with.
We have an agreement with The Electoral Commission under the Public Sector Mapping Agreement
that allows us to receive data that's in AddressBase including UPRNs.
If you send us geospatial data that's created from OS's BaseMap then this can be made public
under ‘presumption to publish’.
[You can read more about this here](http://www.ordnancesurvey.co.uk/docs/public-disclosures/presumption-to-publish-guidance-march-2015.pdf).
We suggest that you publish Geo data as a WFS layer from your GIS software.
### Using the finder on your website
If you provide data to us then you can embed our polling station finder directly on
your website, free of charge.
You'll need to add a bit of code to your site.
[Find out how]({% url "projects:polling_embed_code" %}).
*Want to talk to a human? Please email [pollingstations<EMAIL_ADDRESS>or call on [03331 122450](tel:443331122450)*
{% endfilter %}
{% endblock main_content %}


Giant Floating Baby Head (GFBH) Extension Options
Configure GFBH to function the way you want.
Am I missing a setting you'd like to configure? Did you find a bug? Do you want to help by translating this page?
Let me know at https://github.com/homelessbread/giant-floating-baby-head/issues or<EMAIL_ADDRESS>Don't forget to rate the extension!


New Product
| |
| Project File | DS301_profile.xpd |
| File Version | 1 |
| Created | 23. 11. 2020 12:00:00 |
| Created By | |
| Modified | 24. 11. 2020 13:31:53 |
| Modified By | |
This file was automatically generated with libedssharp Object Dictionary Editor v0.8-99-g0425f94
Device Information
| |
| Vendor Name | |
| Vendor ID | |
| Product Name | New Product |
| Product ID | |
| Granularity | 8 |
| RPDO count | 4 |
| TPDO count | 4 |
| LSS Slave | True |
| LSS Master | False |
Supported Baud rates
- [x] 10 kBit/s
- [x] 20 kBit/s
- [x] 50 kBit/s
- [x] 125 kBit/s
- [x] 250 kBit/s
- [x] 500 kBit/s
- [x] 800 kBit/s
- [x] 1000 kBit/s
- [ ] auto
PDO Mapping
Communication Specific Parameters
0x1000 - Device type
| Object Type | Count Label | Storage Group | IO extension | PDO flags |
| VAR | NMT | PERSIST_COMM | False | False |
| Data Type | SDO | PDO | SRDO | Default Value |
| UNSIGNED32 | ro | no | no | 0x00000000 |
- bit 16-31: Additional information
- bit 0-15: Device profile number
0x1001 - Error register
| Object Type | Count Label | Storage Group | IO extension | PDO flags |
| VAR | EM | RAM | False | False |
| Data Type | SDO | PDO | SRDO | Default Value |
| UNSIGNED8 | ro | tr | no | 0x00 |
- bit 7: manufacturer specific
- bit 6: Reserved (always 0)
- bit 5: device profile specific
- bit 4: communication error (overrun, error state)
- bit 3: temperature
- bit 2: voltage
- bit 1: current
- bit 0: generic error
0x1003 - Pre-defined error field
| Object Type | Count Label | Storage Group | IO extension | PDO flags |
| ARRAY | | RAM | True | False |
| Sub | Name | Data Type | SDO | PDO | SRDO | Default Value |
| 0x00 | Number of errors | UNSIGNED8 | rw | no | no | 0 |
| 0x01 | Standard error field | UNSIGNED32 | ro | no | no | 0x00000000 |
| 0x02 | Standard error field | UNSIGNED32 | ro | no | no | 0x00000000 |
| 0x03 | Standard error field | UNSIGNED32 | ro | no | no | 0x00000000 |
| 0x04 | Standard error field | UNSIGNED32 | ro | no | no | 0x00000000 |
| 0x05 | Standard error field | UNSIGNED32 | ro | no | no | 0x00000000 |
| 0x06 | Standard error field | UNSIGNED32 | ro | no | no | 0x00000000 |
| 0x07 | Standard error field | UNSIGNED32 | ro | no | no | 0x00000000 |
| 0x08 | Standard error field | UNSIGNED32 | ro | no | no | 0x00000000 |
- Sub Index 0: Contains number of actual errors. 0 can be written to clear error history.
- sub-index 1 and above:
- bit 16-31: Manufacturer specific additional information
- bit 0-15: Error code as transmited in the Emergency object
0x1005 - COB-ID SYNC message
| Object Type | Count Label | Storage Group | IO extension | PDO flags |
| VAR | SYNC | PERSIST_COMM | True | False |
| Data Type | SDO | PDO | SRDO | Default Value |
| UNSIGNED32 | rw | no | no | 0x00000080 |
- bit 31: set to 0
- bit 30: If set, CANopen device generates SYNC object
- bit 11-29: set to 0
- bit 0-10: 11-bit CAN-ID
0x1006 - Communication cycle period
| Object Type | Count Label | Storage Group | IO extension | PDO flags |
| VAR | SYNC_PROD | PERSIST_COMM | True | False |
| Data Type | SDO | PDO | SRDO | Default Value |
| UNSIGNED32 | rw | no | no | 0 |
Period of SYNC transmission in µs (0 = transmission disabled).
0x1007 - Synchronous window length
| Object Type | Count Label | Storage Group | IO extension | PDO flags |
| VAR | | PERSIST_COMM | True | False |
| Data Type | SDO | PDO | SRDO | Default Value |
| UNSIGNED32 | rw | no | no | 0 |
Synchronous window leghth in µs (0 = not used). All synchronous PDOs must be transmitted within this time window.
0x1010 - Store parameters
| Object Type | Count Label | Storage Group | IO extension | PDO flags |
| ARRAY | | RAM | True | False |
| Sub | Name | Data Type | SDO | PDO | SRDO | Default Value |
| 0x00 | Highest sub-index supported | UNSIGNED8 | ro | no | no | 0x04 |
| 0x01 | Save all parameters | UNSIGNED32 | rw | no | no | 0x00000001 |
| 0x02 | Save communication parameters | UNSIGNED32 | rw | no | no | 0x00000001 |
| 0x03 | Save application parameters | UNSIGNED32 | rw | no | no | 0x00000001 |
| 0x04 | Save manufacturer defined parameters | UNSIGNED32 | rw | no | no | 0x00000001 |
Sub-indexes 1 and above:
- Reading provides information about its storage functionality:
- bit 1: If set, CANopen device saves parameters autonomously
- bit 0: If set, CANopen device saves parameters on command
- Writing value 0x65766173 ('s','a','v','e' from LSB to MSB) stores corresponding data.
0x1011 - Restore default parameters
| Object Type | Count Label | Storage Group | IO extension | PDO flags |
| ARRAY | | RAM | True | False |
| Sub | Name | Data Type | SDO | PDO | SRDO | Default Value |
| 0x00 | Highest sub-index supported | UNSIGNED8 | ro | no | no | 0x04 |
| 0x01 | Restore all default parameters | UNSIGNED32 | rw | no | no | 0x00000001 |
| 0x02 | Restore communication default parameters | UNSIGNED32 | rw | no | no | 0x00000001 |
| 0x03 | Restore application default parameters | UNSIGNED32 | rw | no | no | 0x00000001 |
| 0x04 | Restore manufacturer defined default parameters | UNSIGNED32 | rw | no | no | 0x00000001 |
Sub-indexes 1 and above:
- Reading provides information about its restoring capability:
- bit 0: If set, CANopen device restores parameters
- Writing value 0x64616F6C ('l','o','a','d' from LSB to MSB) restores corresponding data.
0x1012 - COB-ID time stamp object
| Object Type | Count Label | Storage Group | IO extension | PDO flags |
| VAR | TIME | PERSIST_COMM | True | False |
| Data Type | SDO | PDO | SRDO | Default Value |
| UNSIGNED32 | rw | no | no | 0x00000100 |
- bit 31: If set, CANopen device consumes TIME message
- bit 30: If set, CANopen device produces TIME message
- bit 11-29: set to 0
- bit 0-10: 11-bit CAN-ID
0x1014 - COB-ID EMCY
| Object Type | Count Label | Storage Group | IO extension | PDO flags |
| VAR | EM_PROD | PERSIST_COMM | True | False |
| Data Type | SDO | PDO | SRDO | Default Value |
| UNSIGNED32 | rw | no | no | 0x80+$NODEID |
- bit 31: If set, EMCY does NOT exist / is NOT valid
- bit 11-30: set to 0
- bit 0-10: 11-bit CAN-ID
0x1015 - Inhibit time EMCY
| Object Type | Count Label | Storage Group | IO extension | PDO flags |
| VAR | | PERSIST_COMM | True | False |
| Data Type | SDO | PDO | SRDO | Default Value |
| UNSIGNED16 | rw | no | no | 0 |
Inhibit time of emergency message in multiples of 100µs. The value 0 disables the inhibit time.
0x1016 - Consumer heartbeat time
| Object Type | Count Label | Storage Group | IO extension | PDO flags |
| ARRAY | HB_CONS | PERSIST_COMM | True | False |
| Sub | Name | Data Type | SDO | PDO | SRDO | Default Value |
| 0x00 | Highest sub-index supported | UNSIGNED8 | ro | no | no | 0x08 |
| 0x01 | Consumer heartbeat time | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x02 | Consumer heartbeat time | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x03 | Consumer heartbeat time | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x04 | Consumer heartbeat time | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x05 | Consumer heartbeat time | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x06 | Consumer heartbeat time | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x07 | Consumer heartbeat time | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x08 | Consumer heartbeat time | UNSIGNED32 | rw | no | no | 0x00000000 |
Consumer Heartbeat Time:
- bit 24-31: set to 0
- bit 16-23: Node ID of the monitored node. If 0 or greater than 127, sub-entry is not used.
- bit 0-15: Heartbeat time in ms (if 0, sub-intry is not used). Value should be higher than the corresponding producer heartbeat time.
0x1017 - Producer heartbeat time
| Object Type | Count Label | Storage Group | IO extension | PDO flags |
| VAR | HB_PROD | PERSIST_COMM | True | False |
| Data Type | SDO | PDO | SRDO | Default Value |
| UNSIGNED16 | rw | no | no | 0 |
Heartbeat producer time in ms (0 = disable transmission).
0x1018 - Identity
| Object Type | Count Label | Storage Group | IO extension | PDO flags |
| RECORD | | PERSIST_COMM | False | False |
| Sub | Name | Data Type | SDO | PDO | SRDO | Default Value |
| 0x00 | Highest sub-index supported | UNSIGNED8 | ro | no | no | 0x04 |
| 0x01 | Vendor-ID | UNSIGNED32 | ro | no | no | 0x00000000 |
| 0x02 | Product code | UNSIGNED32 | ro | no | no | 0x00000000 |
| 0x03 | Revision number | UNSIGNED32 | ro | no | no | 0x00000000 |
| 0x04 | Serial number | UNSIGNED32 | ro | no | no | 0x00000000 |
- Vendor-ID, assigned by CiA
- Product code, manufacturer specific
- Revision number:
- bit 16-31: Major revision number (CANopen behavior has changed)
- bit 0-15: Minor revision num. (CANopen behavior has not changed)
- Serial number, manufacturer specific
0x1019 - Synchronous counter overflow value
| Object Type | Count Label | Storage Group | IO extension | PDO flags |
| VAR | | PERSIST_COMM | False | False |
| Data Type | SDO | PDO | SRDO | Default Value |
| UNSIGNED8 | rw | no | no | 0 |
- Value 0: SYNC message is transmitted with data length 0.
- Value 1: reserved.
- Value 2-240: SYNC message has one data byte, which contains the counter.
- Value 241-255: reserved.
0x1200 - SDO server parameter
| Object Type | Count Label | Storage Group | IO extension | PDO flags |
| RECORD | SDO_SRV | RAM | True | False |
| Sub | Name | Data Type | SDO | PDO | SRDO | Default Value |
| 0x00 | Highest sub-index supported | UNSIGNED8 | ro | no | no | 2 |
| 0x01 | COB-ID client to server (rx) | UNSIGNED32 | ro | t | no | 0x600+$NODEID |
| 0x02 | COB-ID server to client (tx) | UNSIGNED32 | ro | t | no | 0x580+$NODEID |
Sub-indexes 1 and 2:
- bit 11-31: set to 0
- bit 0-10: 11-bit CAN-ID
0x1280 - SDO client parameter
| Object Type | Count Label | Storage Group | IO extension | PDO flags |
| RECORD | SDO_CLI | PERSIST_COMM | True | False |
| Sub | Name | Data Type | SDO | PDO | SRDO | Default Value |
| 0x00 | Highest sub-index supported | UNSIGNED8 | ro | no | no | 0x03 |
| 0x01 | COB-ID client to server (tx) | UNSIGNED32 | rw | tr | no | 0x80000000 |
| 0x02 | COB-ID server to client (rx) | UNSIGNED32 | rw | tr | no | 0x80000000 |
| 0x03 | Node-ID of the SDO server | UNSIGNED8 | rw | no | no | 0x01 |
- Sub-indexes 1 and 2:
- bit 31: If set, SDO does NOT exist / is NOT valid
- bit 30: If set, value is assigned dynamically
- bit 11-29: set to 0
- bit 0-10: 11-bit CAN-ID
- Node-ID of the SDO server, 0x01 to 0x7F
0x1400 - RPDO communication parameter
| Object Type | Count Label | Storage Group | IO extension | PDO flags |
| RECORD | RPDO | PERSIST_COMM | True | False |
| Sub | Name | Data Type | SDO | PDO | SRDO | Default Value |
| 0x00 | Highest sub-index supported | UNSIGNED8 | ro | no | no | 0x05 |
| 0x01 | COB-ID used by RPDO | UNSIGNED32 | rw | no | no | 0x80000200+$NODEID |
| 0x02 | Transmission type | UNSIGNED8 | rw | no | no | 254 |
| 0x05 | Event timer | UNSIGNED16 | rw | no | no | 0 |
- COB-ID used by RPDO:
- bit 31: If set, PDO does not exist / is not valid
- bit 11-30: set to 0
- bit 0-10: 11-bit CAN-ID
- Transmission type:
- Value 0-240: synchronous, processed after next reception of SYNC object
- Value 241-253: not used
- Value 254: event-driven (manufacturer-specific)
- Value 255: event-driven (device profile and application profile specific)
- Event timer in ms (0 = disabled) for deadline monitoring.
0x1401 - RPDO communication parameter
| Object Type | Count Label | Storage Group | IO extension | PDO flags |
| RECORD | RPDO | PERSIST_COMM | True | False |
| Sub | Name | Data Type | SDO | PDO | SRDO | Default Value |
| 0x00 | Highest sub-index supported | UNSIGNED8 | ro | no | no | 0x05 |
| 0x01 | COB-ID used by RPDO | UNSIGNED32 | rw | no | no | 0x80000300+$NODEID |
| 0x02 | Transmission type | UNSIGNED8 | rw | no | no | 254 |
| 0x05 | Event timer | UNSIGNED16 | rw | no | no | 0 |
- COB-ID used by RPDO:
- bit 31: If set, PDO does not exist / is not valid
- bit 11-30: set to 0
- bit 0-10: 11-bit CAN-ID
- Transmission type:
- Value 0-240: synchronous, processed after next reception of SYNC object
- Value 241-253: not used
- Value 254: event-driven (manufacturer-specific)
- Value 255: event-driven (device profile and application profile specific)
- Event timer in ms (0 = disabled) for deadline monitoring.
0x1402 - RPDO communication parameter
| Object Type | Count Label | Storage Group | IO extension | PDO flags |
| RECORD | RPDO | PERSIST_COMM | True | False |
| Sub | Name | Data Type | SDO | PDO | SRDO | Default Value |
| 0x00 | Highest sub-index supported | UNSIGNED8 | ro | no | no | 0x05 |
| 0x01 | COB-ID used by RPDO | UNSIGNED32 | rw | no | no | 0x80000400+$NODEID |
| 0x02 | Transmission type | UNSIGNED8 | rw | no | no | 254 |
| 0x05 | Event timer | UNSIGNED16 | rw | no | no | 0 |
- COB-ID used by RPDO:
- bit 31: If set, PDO does not exist / is not valid
- bit 11-30: set to 0
- bit 0-10: 11-bit CAN-ID
- Transmission type:
- Value 0-240: synchronous, processed after next reception of SYNC object
- Value 241-253: not used
- Value 254: event-driven (manufacturer-specific)
- Value 255: event-driven (device profile and application profile specific)
- Event timer in ms (0 = disabled) for deadline monitoring.
0x1403 - RPDO communication parameter
| Object Type | Count Label | Storage Group | IO extension | PDO flags |
| RECORD | RPDO | PERSIST_COMM | True | False |
| Sub | Name | Data Type | SDO | PDO | SRDO | Default Value |
| 0x00 | Highest sub-index supported | UNSIGNED8 | ro | no | no | 0x05 |
| 0x01 | COB-ID used by RPDO | UNSIGNED32 | rw | no | no | 0x80000500+$NODEID |
| 0x02 | Transmission type | UNSIGNED8 | rw | no | no | 254 |
| 0x05 | Event timer | UNSIGNED16 | rw | no | no | 0 |
- COB-ID used by RPDO:
- bit 31: If set, PDO does not exist / is not valid
- bit 11-30: set to 0
- bit 0-10: 11-bit CAN-ID
- Transmission type:
- Value 0-240: synchronous, processed after next reception of SYNC object
- Value 241-253: not used
- Value 254: event-driven (manufacturer-specific)
- Value 255: event-driven (device profile and application profile specific)
- Event timer in ms (0 = disabled) for deadline monitoring.
0x1600 - RPDO mapping parameter
| Object Type | Count Label | Storage Group | IO extension | PDO flags |
| RECORD | | PERSIST_COMM | True | False |
| Sub | Name | Data Type | SDO | PDO | SRDO | Default Value |
| 0x00 | Number of mapped application objects in PDO | UNSIGNED8 | rw | no | no | 0 |
| 0x01 | Application object 1 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x02 | Application object 2 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x03 | Application object 3 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x04 | Application object 4 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x05 | Application object 5 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x06 | Application object 6 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x07 | Application object 7 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x08 | Application object 8 | UNSIGNED32 | rw | no | no | 0x00000000 |
- Number of mapped application objects in PDO:
- Value 0: mapping is disabled.
- Value 1: sub-index 0x01 is valid.
- Value 2-8: sub-indexes 0x01 to (0x02 to 0x08) are valid.
- Application object 1-8:
- bit 16-31: index
- bit 8-15: sub-index
- bit 0-7: data length in bits
0x1601 - RPDO mapping parameter
| Object Type | Count Label | Storage Group | IO extension | PDO flags |
| RECORD | | PERSIST_COMM | True | False |
| Sub | Name | Data Type | SDO | PDO | SRDO | Default Value |
| 0x00 | Number of mapped application objects in PDO | UNSIGNED8 | rw | no | no | 0 |
| 0x01 | Application object 1 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x02 | Application object 2 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x03 | Application object 3 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x04 | Application object 4 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x05 | Application object 5 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x06 | Application object 6 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x07 | Application object 7 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x08 | Application object 8 | UNSIGNED32 | rw | no | no | 0x00000000 |
- Number of mapped application objects in PDO:
- Value 0: mapping is disabled.
- Value 1: sub-index 0x01 is valid.
- Value 2-8: sub-indexes 0x01 to (0x02 to 0x08) are valid.
- Application object 1-8:
- bit 16-31: index
- bit 8-15: sub-index
- bit 0-7: data length in bits
0x1602 - RPDO mapping parameter
| Object Type | Count Label | Storage Group | IO extension | PDO flags |
| RECORD | | PERSIST_COMM | True | False |
| Sub | Name | Data Type | SDO | PDO | SRDO | Default Value |
| 0x00 | Number of mapped application objects in PDO | UNSIGNED8 | rw | no | no | 0 |
| 0x01 | Application object 1 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x02 | Application object 2 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x03 | Application object 3 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x04 | Application object 4 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x05 | Application object 5 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x06 | Application object 6 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x07 | Application object 7 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x08 | Application object 8 | UNSIGNED32 | rw | no | no | 0x00000000 |
- Number of mapped application objects in PDO:
- Value 0: mapping is disabled.
- Value 1: sub-index 0x01 is valid.
- Value 2-8: sub-indexes 0x01 to (0x02 to 0x08) are valid.
- Application object 1-8:
- bit 16-31: index
- bit 8-15: sub-index
- bit 0-7: data length in bits
0x1603 - RPDO mapping parameter
| Object Type | Count Label | Storage Group | IO extension | PDO flags |
| RECORD | | PERSIST_COMM | True | False |
| Sub | Name | Data Type | SDO | PDO | SRDO | Default Value |
| 0x00 | Number of mapped application objects in PDO | UNSIGNED8 | rw | no | no | 0 |
| 0x01 | Application object 1 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x02 | Application object 2 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x03 | Application object 3 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x04 | Application object 4 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x05 | Application object 5 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x06 | Application object 6 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x07 | Application object 7 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x08 | Application object 8 | UNSIGNED32 | rw | no | no | 0x00000000 |
- Number of mapped application objects in PDO:
- Value 0: mapping is disabled.
- Value 1: sub-index 0x01 is valid.
- Value 2-8: sub-indexes 0x01 to (0x02 to 0x08) are valid.
- Application object 1-8:
- bit 16-31: index
- bit 8-15: sub-index
- bit 0-7: data length in bits
0x1800 - TPDO communication parameter
| Object Type | Count Label | Storage Group | IO extension | PDO flags |
| RECORD | TPDO | PERSIST_COMM | True | False |
| Sub | Name | Data Type | SDO | PDO | SRDO | Default Value |
| 0x00 | Highest sub-index supported | UNSIGNED8 | ro | no | no | 0x06 |
| 0x01 | COB-ID used by TPDO | UNSIGNED32 | rw | no | no | 0xC0000180+$NODEID |
| 0x02 | Transmission type | UNSIGNED8 | rw | no | no | 254 |
| 0x03 | Inhibit time | UNSIGNED16 | rw | no | no | 0 |
| 0x05 | Event timer | UNSIGNED16 | rw | no | no | 0 |
| 0x06 | SYNC start value | UNSIGNED8 | rw | no | no | 0 |
- COB-ID used by RPDO:
- bit 31: If set, PDO does not exist / is not valid
- bit 30: If set, NO RTR is allowed on this PDO
- bit 11-29: set to 0
- bit 0-10: 11-bit CAN-ID
- Transmission type:
- Value 0: synchronous (acyclic)
- Value 1-240: synchronous (cyclic every (1-240)-th sync)
- Value 241-253: not used
- Value 254: event-driven (manufacturer-specific)
- Value 255: event-driven (device profile and application profile specific)
- Inhibit time in multiple of 100µs, if the transmission type is set to 254 or 255 (0 = disabled).
- Event timer interval in ms, if the transmission type is set to 254 or 255 (0 = disabled).
- SYNC start value
- Value 0: Counter of the SYNC message shall not be processed.
- Value 1-240: The SYNC message with the counter value equal to this value shall be regarded as the first received SYNC message.
0x1801 - TPDO communication parameter
| Object Type | Count Label | Storage Group | IO extension | PDO flags |
| RECORD | TPDO | PERSIST_COMM | True | False |
| Sub | Name | Data Type | SDO | PDO | SRDO | Default Value |
| 0x00 | Highest sub-index supported | UNSIGNED8 | ro | no | no | 0x06 |
| 0x01 | COB-ID used by TPDO | UNSIGNED32 | rw | no | no | 0xC0000280+$NODEID |
| 0x02 | Transmission type | UNSIGNED8 | rw | no | no | 254 |
| 0x03 | Inhibit time | UNSIGNED16 | rw | no | no | 0 |
| 0x05 | Event timer | UNSIGNED16 | rw | no | no | 0 |
| 0x06 | SYNC start value | UNSIGNED8 | rw | no | no | 0 |
- COB-ID used by RPDO:
- bit 31: If set, PDO does not exist / is not valid
- bit 30: If set, NO RTR is allowed on this PDO
- bit 11-29: set to 0
- bit 0-10: 11-bit CAN-ID
- Transmission type:
- Value 0: synchronous (acyclic)
- Value 1-240: synchronous (cyclic every (1-240)-th sync)
- Value 241-253: not used
- Value 254: event-driven (manufacturer-specific)
- Value 255: event-driven (device profile and application profile specific)
- Inhibit time in multiple of 100µs, if the transmission type is set to 254 or 255 (0 = disabled).
- Event timer interval in ms, if the transmission type is set to 254 or 255 (0 = disabled).
- SYNC start value
- Value 0: Counter of the SYNC message shall not be processed.
- Value 1-240: The SYNC message with the counter value equal to this value shall be regarded as the first received SYNC message.
0x1802 - TPDO communication parameter
| Object Type | Count Label | Storage Group | IO extension | PDO flags |
| RECORD | TPDO | PERSIST_COMM | True | False |
| Sub | Name | Data Type | SDO | PDO | SRDO | Default Value |
| 0x00 | Highest sub-index supported | UNSIGNED8 | ro | no | no | 0x06 |
| 0x01 | COB-ID used by TPDO | UNSIGNED32 | rw | no | no | 0xC0000380+$NODEID |
| 0x02 | Transmission type | UNSIGNED8 | rw | no | no | 254 |
| 0x03 | Inhibit time | UNSIGNED16 | rw | no | no | 0 |
| 0x05 | Event timer | UNSIGNED16 | rw | no | no | 0 |
| 0x06 | SYNC start value | UNSIGNED8 | rw | no | no | 0 |
- COB-ID used by RPDO:
- bit 31: If set, PDO does not exist / is not valid
- bit 30: If set, NO RTR is allowed on this PDO
- bit 11-29: set to 0
- bit 0-10: 11-bit CAN-ID
- Transmission type:
- Value 0: synchronous (acyclic)
- Value 1-240: synchronous (cyclic every (1-240)-th sync)
- Value 241-253: not used
- Value 254: event-driven (manufacturer-specific)
- Value 255: event-driven (device profile and application profile specific)
- Inhibit time in multiple of 100µs, if the transmission type is set to 254 or 255 (0 = disabled).
- Event timer interval in ms, if the transmission type is set to 254 or 255 (0 = disabled).
- SYNC start value
- Value 0: Counter of the SYNC message shall not be processed.
- Value 1-240: The SYNC message with the counter value equal to this value shall be regarded as the first received SYNC message.
0x1803 - TPDO communication parameter
| Object Type | Count Label | Storage Group | IO extension | PDO flags |
| RECORD | TPDO | PERSIST_COMM | True | False |
| Sub | Name | Data Type | SDO | PDO | SRDO | Default Value |
| 0x00 | Highest sub-index supported | UNSIGNED8 | ro | no | no | 0x06 |
| 0x01 | COB-ID used by TPDO | UNSIGNED32 | rw | no | no | 0xC0000480+$NODEID |
| 0x02 | Transmission type | UNSIGNED8 | rw | no | no | 254 |
| 0x03 | Inhibit time | UNSIGNED16 | rw | no | no | 0 |
| 0x05 | Event timer | UNSIGNED16 | rw | no | no | 0 |
| 0x06 | SYNC start value | UNSIGNED8 | rw | no | no | 0 |
- COB-ID used by RPDO:
- bit 31: If set, PDO does not exist / is not valid
- bit 30: If set, NO RTR is allowed on this PDO
- bit 11-29: set to 0
- bit 0-10: 11-bit CAN-ID
- Transmission type:
- Value 0: synchronous (acyclic)
- Value 1-240: synchronous (cyclic every (1-240)-th sync)
- Value 241-253: not used
- Value 254: event-driven (manufacturer-specific)
- Value 255: event-driven (device profile and application profile specific)
- Inhibit time in multiple of 100µs, if the transmission type is set to 254 or 255 (0 = disabled).
- Event timer interval in ms, if the transmission type is set to 254 or 255 (0 = disabled).
- SYNC start value
- Value 0: Counter of the SYNC message shall not be processed.
- Value 1-240: The SYNC message with the counter value equal to this value shall be regarded as the first received SYNC message.
0x1A00 - TPDO mapping parameter
| Object Type | Count Label | Storage Group | IO extension | PDO flags |
| RECORD | | PERSIST_COMM | True | False |
| Sub | Name | Data Type | SDO | PDO | SRDO | Default Value |
| 0x00 | Number of mapped application objects in PDO | UNSIGNED8 | rw | no | no | 0 |
| 0x01 | Application object 1 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x02 | Application object 2 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x03 | Application object 3 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x04 | Application object 4 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x05 | Application object 5 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x06 | Application object 6 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x07 | Application object 7 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x08 | Application object 8 | UNSIGNED32 | rw | no | no | 0x00000000 |
- Number of mapped application objects in PDO:
- Value 0: mapping is disabled.
- Value 1: sub-index 0x01 is valid.
- Value 2-8: sub-indexes 0x01 to (0x02 to 0x08) are valid.
- Application object 1-8:
- bit 16-31: index
- bit 8-15: sub-index
- bit 0-7: data length in bits
0x1A01 - TPDO mapping parameter
| Object Type | Count Label | Storage Group | IO extension | PDO flags |
| RECORD | | PERSIST_COMM | True | False |
| Sub | Name | Data Type | SDO | PDO | SRDO | Default Value |
| 0x00 | Number of mapped application objects in PDO | UNSIGNED8 | rw | no | no | 0 |
| 0x01 | Application object 1 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x02 | Application object 2 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x03 | Application object 3 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x04 | Application object 4 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x05 | Application object 5 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x06 | Application object 6 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x07 | Application object 7 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x08 | Application object 8 | UNSIGNED32 | rw | no | no | 0x00000000 |
- Number of mapped application objects in PDO:
- Value 0: mapping is disabled.
- Value 1: sub-index 0x01 is valid.
- Value 2-8: sub-indexes 0x01 to (0x02 to 0x08) are valid.
- Application object 1-8:
- bit 16-31: index
- bit 8-15: sub-index
- bit 0-7: data length in bits
0x1A02 - TPDO mapping parameter
| Object Type | Count Label | Storage Group | IO extension | PDO flags |
| RECORD | | PERSIST_COMM | True | False |
| Sub | Name | Data Type | SDO | PDO | SRDO | Default Value |
| 0x00 | Number of mapped application objects in PDO | UNSIGNED8 | rw | no | no | 0 |
| 0x01 | Application object 1 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x02 | Application object 2 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x03 | Application object 3 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x04 | Application object 4 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x05 | Application object 5 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x06 | Application object 6 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x07 | Application object 7 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x08 | Application object 8 | UNSIGNED32 | rw | no | no | 0x00000000 |
- Number of mapped application objects in PDO:
- Value 0: mapping is disabled.
- Value 1: sub-index 0x01 is valid.
- Value 2-8: sub-indexes 0x01 to (0x02 to 0x08) are valid.
- Application object 1-8:
- bit 16-31: index
- bit 8-15: sub-index
- bit 0-7: data length in bits
0x1A03 - TPDO mapping parameter
| Object Type | Count Label | Storage Group | IO extension | PDO flags |
| RECORD | | PERSIST_COMM | True | False |
| Sub | Name | Data Type | SDO | PDO | SRDO | Default Value |
| 0x00 | Number of mapped application objects in PDO | UNSIGNED8 | rw | no | no | 0 |
| 0x01 | Application object 1 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x02 | Application object 2 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x03 | Application object 3 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x04 | Application object 4 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x05 | Application object 5 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x06 | Application object 6 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x07 | Application object 7 | UNSIGNED32 | rw | no | no | 0x00000000 |
| 0x08 | Application object 8 | UNSIGNED32 | rw | no | no | 0x00000000 |
- Number of mapped application objects in PDO:
- Value 0: mapping is disabled.
- Value 1: sub-index 0x01 is valid.
- Value 2-8: sub-indexes 0x01 to (0x02 to 0x08) are valid.
- Application object 1-8:
- bit 16-31: index
- bit 8-15: sub-index
- bit 0-7: data length in bits


This will open Au-to-do in a new tab and log you in. Once you've logged in, the extension will sync automatically.


snakx
We are serving technologies that allows you to access, identify, and manipulate the user interface (UI) elements of another application. We also develop modern solutions based on Xamarin and Rest API.
View on GitHub
Made with ❤ - snakx Team


public class DbBackup
extends java.lang.Object
Backing up without DbBackup
Because JE has an append only log file architecture, it is always possible to do a hot backup without the use of DbBackup by copying all log files (.jdb files) to your archival location. As long as the log files are copied in alphabetical order, (numerical in effect) and all log files are copied, the environment can be successfully backed up without any need to stop database operations or background activity. This means that your backup operation must do a loop to check for the creation of new log files before deciding that the backup is finished. For example:
time files in activity environment t0 000000001.jdb Backup starts copying file 1 000000003.jdb 000000004.jdb t1 000000001.jdb JE log cleaner migrates portion of file 3 to newly 000000004.jdb created file 5 and deletes file 3. Backup finishes 000000005.jdb file 1, starts copying file 4. Backup MUST include file 5 for a consistent backup! t2 000000001.jdb Backup finishes copying file 4, starts and 000000004.jdb finishes file 5, has caught up. Backup ends. 000000005.jdb
In the example above, the backup operation must be sure to copy file 5, which came into existence after the backup had started. If the backup stopped operations at file 4, the backup set would include only file 1 and 4, omitting file 3, which would be an inconsistent set.
Also note that log file 5 may not have filled up before it was copied to archival storage. On the next backup, there might be a newer, larger version of file 5, and that newer version should replace the older file 5 in archive storage.
Using the approach above, as opposed to using DbBackup, will copy all files
including reserved files
as well
as active files
. A large number of
reserved files may be present in an HA Environment, and they are essentially
wasted space in a backup. Using DbBackup is strongly recommended for this
reason, as well as to reduce the complexity of file copying.
Backing up with DbBackup
DbBackup helps simplify application backup by defining the set of active files
that must be copied for each
backup operation. If the environment directory has read/write protection,
the application must pass DbBackup an open, read/write environment handle.
When entering backup mode, JE determines the set of active files needed for a consistent backup, and freezes all changes to those files. The application can copy that defined set of files and finish operation without checking for the ongoing creation of new files. Also, there will be no need to check for a newer version of the last file on the next backup.
In the example above, if DbBackup was used at t0, the application would only have to copy files 1, 3 and 4 to back up. On a subsequent backup, the application could start its copying at file 5. There would be no need to check for a newer version of file 4.
When it is important to minimize the time that it takes to recover using a
backup, a checkpoint should be performed immediately before calling startBackup()
. This will reduce recovery time when opening the environment
with the restored log files. A checkpoint is performed explicitly by
calling Environment.checkpoint(com.sleepycat.je.CheckpointConfig)
using a config object for which
setForce(true)
has been called.
Performing simple/full backups
The following examples shows how to perform a full backup. A checkpoint is performed to minimize recovery time.
void myBackup(Environment env, File destDir) { DbBackup backupHelper = new DbBackup(env); // Optional: Do a checkpoint to reduce recovery time after a restore. env.checkpoint(new CheckpointConfig().setForce(true)); // Start backup, find out what needs to be copied. backupHelper.startBackup(); try { // Copy the necessary files to archival storage. String[] filesToCopy = backupHelper.getLogFilesInBackupSet(); myCopyFiles(env, backupHelper, filesToCopy, destDir); } finally { // Remember to exit backup mode, or the JE cleaner cannot delete // log files and disk usage will grow without bounds. backupHelper.endBackup(); } } void myCopyFiles( Environment env, DbBackup backupHelper, String[] filesToCopy, File destDir) { for (String fileName : filesToCopy) { // Copy fileName to destDir. // SeeWhen copying files to the backup directory, it is critical that each file is verified before or during the copy. If a file is copied that is corrupt (due to an earlier disk failure that went unnoticed, for example), the backup will be invalid and provide a false sense of security.LogVerificationReadableByteChannel
and //LogVerificationInputStream
. .... // Remove protection to allow file to be deleted in order to reclaim // disk space. backupHelper.removeFileProtection(fileName); } }
The example here
shows how to implement
the myCopyFiles
method using LogVerificationInputStream
. A LogVerificationReadableByteChannel
could also be used for higher performance copying. A filter input stream is
used to verify the file efficiently as it is being read. If you choose to
use a script for copying files, the DbVerifyLog
command line tool
can be used instead.
Assuming that the full backup copied files into an empty directory, to restore you can simply copy these files back into another empty directory.
Always start with an empty directory as the destination for a full backup or
a restore, to ensure that no unused files are present. Unused files --
perhaps the residual of an earlier environment or an earlier backup -- will
take up space, and they will never be deleted by the JE log cleaner. Also
note that such files will not be used by JE for calculating utilization and
will not appear in the DbSpace
output.
Performing incremental backups
Incremental backups are used to reduce the number of files copied during each backup. Compared to a full backup, there are two additional pieces of information needed for an incremental backup: the number of the last file in the previous backup, and a list of the active files in the environment directory at the time of the current backup, i.e., the current snapshot. Their purpose is explained below.
The number of the last file in the previous backup is used to avoid copying files that are already present in the backup set. This file number must be obtained before beginning the backup, either by checking the backup archive, or getting this value from a stored location. For example, the last file number could be written to a special file in the backup set at the time of a backup, and then read from the special file before starting the next backup.
The list of files in the current snapshot, which should be obtained by
calling getLogFilesInSnapshot()
(after calling startBackup()
),
is used to avoid unused files after a restore, and may also be used to
reduce the size of the backup set. How to use this list is described below.
Some applications need the ability to restore to the point in time of any of the incremental backups that were made in the past, and other applications only need to restore to the point in time of the most recent backup. Accordingly, the list of current files (that is made at the time of the backup), should be used in one of two ways.
The following two examples shows how to perform an incremental backup. In the first example, the list of current files is used to delete files from the backup set that are no longer needed.
void myBackup(Environment env, File destDir) { // Get the file number of the last file in the previous backup. long lastFileInPrevBackup = ... DbBackup backupHelper = new DbBackup(env, lastFileInPrevBackup); // Optional: Do a checkpoint to reduce recovery time after a restore. env.checkpoint(new CheckpointConfig().setForce(true)); // Start backup, find out what needs to be copied. backupHelper.startBackup(); try { // Copy the necessary files to archival storage. String[] filesToCopy = backupHelper.getLogFilesInBackupSet(); myCopyFiles(env, backupHelper, filesToCopy, destDir); // Delete files that are no longer needed. // WARNING: This should only be done after copying all new files. String[] filesInSnapshot = backupHelper.getLogFilesInSnapshot(); myDeleteUnusedFiles(destDir, filesInSnapshot); // Update knowledge of last file saved in the backup set. lastFileInPrevBackup = backupHelper.getLastFileInBackupSet(); // Save lastFileInPrevBackup persistently here ... } finally { // Remember to exit backup mode, or the JE cleaner cannot delete // log files and disk usage will grow without bounds. backupHelper.endBackup(); } } void myDeleteUnusedFiles(File destDir, String[] filesInSnapshot) { // For each file in destDir that is NOT in filesInSnapshot, it should // be deleted from destDir to save disk space in the backup set, and to // ensure that unused files will not be restored. } See myCopyFiles further above.
When performing backups as shown in the first example above, to restore you can simply copy all files from the backup set into an empty directory.
In the second example below, the list of current files is saved with the backup set so it can be used during a restore. The backup set will effectively hold multiple backups that can be used to restore to different points in time.
void myBackup(Environment env, File destDir) { // Get the file number of the last file in the previous backup. long lastFileInPrevBackup = ... DbBackup backupHelper = new DbBackup(env, lastFileInPrevBackup); // Optional: Do a checkpoint to reduce recovery time after a restore. env.checkpoint(new CheckpointConfig().setForce(true)); // Start backup, find out what needs to be copied. backupHelper.startBackup(); try { // Copy the necessary files to archival storage. String[] filesToCopy = backupHelper.getLogFilesInBackupSet(); myCopyFiles(env, backupHelper, filesToCopy, destDir); // Save current list of files with backup data set. String[] filesInSnapshot = backupHelper.getLogFilesInSnapshot(); // Save filesInSnapshot persistently here ... // Update knowledge of last file saved in the backup set. lastFileInPrevBackup = backupHelper.getLastFileInBackupSet(); // Save lastFileInPrevBackup persistently here ... } finally { // Remember to exit backup mode, or the JE cleaner cannot delete // log files and disk usage will grow without bounds. backupHelper.endBackup(); } } See myCopyFiles further above.
When performing backups as shown in the second example above, to restore you must choose one of the file lists that was saved. You may choose the list written by the most recent backup, or a list written by an earlier backup. To restore, the files in the list should be copied into an empty destination directory.
As described in the sections above, the restore procedure is to copy the files from a backup set into an empty directory. Depending on the type of backup that was performed (see above), either all files from the backup set are copied, or only the files on a list that was created during the backup.
There is one additional consideration when performing a restore, under the following condition:
If the above condition holds, after copying the files an additional step is
needed. To enable the creation of future incremental backups using the
restored files, the EnvironmentConfig.ENV_RECOVERY_FORCE_NEW_FILE
parameter
should be set to true when opening the JE Environment for the first time
after the restore. When this parameter is set to true, the last .jdb file
restored will not be modified when opening the Environment, and the next
.jdb file will be created and will become the end-of-log file.
WARNING: When the above special condition is true and this property is not set to true when opening the environment for the first time after a restore, then the backup set that was restored may not be used as the basis for future incremental backups. If a future incremental backup were performed based on this backup set, it would be incomplete and data would be lost if that incremental backup were restored.
When JE 6.3 or later is used to create the backup, and the backup is created
in a read-write environment (the usual case), this extra step is
unnecessary. In this case, startBackup()
will have added an
"immutable file" marker to the last file in the backup and this will prevent
that file from being modified, just as if the
ENV_RECOVERY_FORCE_NEW_FILE
parameter were set to true.
| Constructor and Description |
|---|
DbBackup(Environment env)
Creates a DbBackup helper for a full backup.
|
DbBackup(Environment env,
long lastFileInPrevBackup)
Creates a DbBackup helper for an incremental backup.
|
| Modifier and Type | Method and Description |
|---|---|
void |
endBackup()
End backup mode, thereby re-enabling normal deletion of log files by the
JE log cleaner.
|
long |
getLastFileInBackupSet()
Can only be called in backup mode, after startBackup() has been called.
|
java.lang.String[] |
getLogFilesInBackupSet()
Get the minimum list of files that must be copied for this backup.
|
java.lang.String[] |
getLogFilesInBackupSet(long lastFileInPrevBackup)
Deprecated.
replaced by
getLogFilesInBackupSet() ; pass
lastFileInPrevBackup to the DbBackup(Environment,long)
constructor. |
java.lang.String[] |
getLogFilesInSnapshot()
Get the list of all active files that are needed for the environment at
the point of time when backup mode started, i.e., the current snapshot.
|
void |
removeFileProtection(java.lang.String fileName)
Removes protection for a file in the backup set.
|
void |
startBackup()
Start backup mode in order to determine the definitive backup set needed
at this point in time.
|
public DbBackup(Environment env) throws DatabaseException
This is equivalent to using DbBackup(Environment,long)
and
passing -1
for the lastFileInPrevBackup
parameter.
env
- with an open, valid environment handle. If the environment
directory has read/write permissions, the environment handle must be
configured for read/write.java.lang.IllegalArgumentException
- if the environment directory has
read/write permissions, but the environment handle is not configured for
read/write.DatabaseException
public DbBackup(Environment env, long lastFileInPrevBackup)
env
- with an open, valid environment handle. If the environment
directory has read/write permissions, the environment handle must be
configured for read/write.lastFileInPrevBackup
- the last file in the previous backup set
when performing an incremental backup, or -1
to perform a full
backup. The first file in this backup set will be the file following
lastFileInPrevBackup
.EnvironmentFailureException
- if an unexpected, internal or
environment-wide failure occurs.java.lang.IllegalArgumentException
- if the environment directory has
read/write permissions, but the environment handle is not configured for
read/write.public void startBackup() throws DatabaseException
This method determines the last file in the backup set, which is the last log file in the environment at this point in time. Following this method call, all new data will be written to other, new log files. In other words, the last file in the backup set will not be modified after this method returns.
WARNING: After calling this method, deletion of log files in
the backup set by the JE log cleaner will be disabled until endBackup()
is called. To prevent unbounded growth of disk usage, be
sure to call endBackup()
to re-enable log file deletion.
Additionally, the Environment can't be closed until endBackup() is
called.
LogOverwriteException
- if a replication
operation is overwriting log files. The backup can not proceed because
files may be invalid. The backup may be attempted at a later time.EnvironmentFailureException
- if an unexpected, internal or
environment-wide failure occurs.java.lang.IllegalStateException
- if a backup is already in progressDatabaseException
public void endBackup()
LogOverwriteException
- if a replication
operation has overwritten log files. Any copied files should be
considered invalid and discarded. The backup may be attempted at a
later time.EnvironmentFailureException
- if an unexpected,
internal or environment-wide failure occurs.java.lang.IllegalStateException
- if a backup has not been started.public long getLastFileInBackupSet()
java.lang.IllegalStateException
- if a backup has not been started.public java.lang.String[] getLogFilesInBackupSet()
The file numbers returned are in the range from the constructor
parameter lastFileInPrevBackup + 1
to the last log file at the
time that startBackup()
was called.
EnvironmentFailureException
- if an unexpected, internal or
environment-wide failure occurs.java.lang.IllegalStateException
- if a backup has not been started.@Deprecated public java.lang.String[] getLogFilesInBackupSet(long lastFileInPrevBackup)
getLogFilesInBackupSet()
; pass
lastFileInPrevBackup to the DbBackup(Environment,long)
constructor.lastFileInPrevBackup
- file number of last file copied in the last
backup session, obtained from getLastFileInBackupSet().EnvironmentFailureException
- if an unexpected, internal or
environment-wide failure occurs.java.lang.IllegalStateException
- if a backup has not been started.public java.lang.String[] getLogFilesInSnapshot()
When performing an incremental backup, this method is called to determine the files that would needed for a restore. As described in the examples at the top of this class, this list can be used to avoid unused files after a restore, and may also be used to reduce the size of the backup set.
When performing a full backup this method is normally not needed,
since in that case it returns the same set of files that is returned by
getLogFilesInBackupSet()
.
EnvironmentFailureException
- if an unexpected, internal or
environment-wide failure occurs.java.lang.IllegalStateException
- if a backup has not been started.public void removeFileProtection(java.lang.String fileName)
fileName
- a file name that has already been copied, in the format
returned by getLogFilesInBackupSet()
.Copyright (c) 2002, 2017 Oracle and/or its affiliates. All rights reserved.


‘Kadaimuga Theerthavari’ performed
by Special CorrespondentHundreds of devotees took holy dip in the Cauvery at Bhagawath Padithurai in Kumbakonam on Saturday where “Aippasi Kadaimuga Theerthavari” of Nageswaran temple, Kumbakonam was held.
The decorated idols of Lord Nageswarar and Goddess Brahannayagi mounted on ‘rishabha vahanam’ was brought to the ghat for performing ‘theerthavari’ to mark the culmination of the month-long ‘thula snanam’ (taking bath in the Cauvery) during the Tamil month Aippasi.
After witnessing the special anointment of ‘asthra devar’ idols on the banks of the river, devotees took the final holy dip when the idol was dipped in the river.


Andrew Harris
American Politician
Mission
There is still an advantage to being able to update small areas of the page without reloading the entire content, which can be achieved via AJAX. This sometimes leads people to create interfaces with all the problems of framesets outlined above.
Election
There is still an advantage to being able to update small areas of the page without reloading the entire content, which can be achieved via AJAX. This sometimes leads people to create interfaces with all the problems of framesets outlined above.
Issues
There is still an advantage to being able to update small areas of the page without reloading the entire content, which can be achieved via AJAX. This sometimes leads people to create interfaces with all the problems of framesets outlined above.
ABSOLUTELY
NEW APPROACH
TO POLITICS
GET YOUR PARTY
MEMBERSHIP
CARD!
(800) 123 1234
(800) 123 1235
USA - LOS ANGELES
9001 East E Street
Washington.
UNITY, PROGRESS, SOLIDARITY
There is still an advantage to being able to update small areas of the page without reloading the entire content. There is still an advantage to being able to update small areas of the page without reloading the entire content.
Achieved via AJAX. This sometimes leads people to create interfaces with all the problems of framesets outlined above. There is still an advantage to being able to update small areas of the page without reloading the entire content.


{% extends 'emails/base.html' %} {% block content %}
{{ full_name }} sent a membership request to join {{ club_name }} through the Penn Clubs website. To approve this request, use the button below to navigate to the Penn Clubs website.
Approve Request {% endblock %}


You can configure a Geode cluster using either cache.xml files,
or you can use gfsh and the cluster configuration service
to configure a cluster.
This table maps cache.xml
elements to the gfsh commands that
configure and manage a cluster.
| cache.xml Element | gfsh Command |
|---|---|
| <cache>, <cache-server> | |
| <async-event-queue> | |
| <pdx> | |
| <region> | |
| <index> | |
| <disk-store> |
Table 1. Migrating cache.xml elements to gfsh commands