Known Issues in Astera 8 (Beta)
Astera8 (Beta) comes with significant changes in the product design architecture. To get more information about the features included in Astera 8, refer to the release notes.
However, we are aware of certain issues and limitations in Astera 8. These issues are either due to pending fixes or due to third-party software limitations.
Here is the list of known issues:
Name and Address parser features are not available in Astera 8 Beta. Functions not supported in the beta release are:
ParseAddress
ParseAddressUS
ParseAndCorrectAddress
ParseName
ParseNameEx
Oracle bulk load is not supported until Oracle releases the .Net Core update for the driver. You can use array insert as an alternative, which provides a similar performance benefit as the bulk load. If you need record-level logging, you can use a Single insert.
Spaces in field names will cause verification and run-time errors. You will need to replace space with a different character, for example, ‘_’, as a workaround for this issue.
Legacy DDTek providers' support is deprecated. Oracle - Legacy, DB2 - Legacy, and Sybase -Legacy providers are not supported in version 8. You are advised to use Oracle ODP and IBM DB2 drivers instead.
The Lean client can only connect to one server at a time. This is done using the Server Connection screen at the client startup. If the user needs to connect to a different server, they will need to close and restart the client, and then connect to the new server using the Server Connection screen. To see the server currently connected to, go to View > Server Explorer. The server will show under the DEFAULT cluster.
Load-balancing can be achieved using clusters of servers with a single repository database. There is no change in this functionality compared to version 7.5. However, only the currently connected server will be listed in Server Explorer, instead of all the servers in the cluster.
SOAP requests are not supported in the Web Server Transformation object.
Last updated