|
| 1 | +--- |
| 2 | +title: Troubleshooting SAP ASE (Sybase) database backup (preview) using Azure Backup |
| 3 | +description: Learn to troubleshoot SAP ASE (Sybase) database backup using Azure Backup. |
| 4 | +ms.topic: troubleshooting |
| 5 | +ms.date: 11/23/2024 |
| 6 | +ms.service: azure-backup |
| 7 | +author: AbhishekMallick-MS |
| 8 | +ms.author: v-abhmallick |
| 9 | +--- |
| 10 | + |
| 11 | +# Troubleshooting SAP ASE (Sybase) database backup (preview) |
| 12 | + |
| 13 | +This article provides troubleshooting details for error codes that appears when protecting SAP ASE (Sybase) databases using Azure Backup. |
| 14 | + |
| 15 | +## Common Error Codes |
| 16 | + |
| 17 | +### InvalidInput |
| 18 | + |
| 19 | +**Error code**: `InvalidInput` |
| 20 | + |
| 21 | +**Error message**: Invalid input for one or more parameters was passed. |
| 22 | + |
| 23 | +**Recommended action**: Fix the input and retry the operation. If the issue persists, contact Microsoft support. |
| 24 | + |
| 25 | +### InvalidDatabaseConnectionDetails |
| 26 | + |
| 27 | +**Error code**: InvalidDatabaseConnectionDetails |
| 28 | + |
| 29 | +**Error message**: Invalid database authentication credentials were supplied. |
| 30 | + |
| 31 | +**Recommended action**: Re-run the pre-registration script with resolvable database host name (or) IP address and database user credentials having permissions to perform Backup and restore operations. |
| 32 | + |
| 33 | +### RegistrationFailure |
| 34 | + |
| 35 | +**Error code**: `RegistrationFailure` |
| 36 | + |
| 37 | +**Error message**: Registration failed on the instance. |
| 38 | + |
| 39 | +**Recommended action**: To resolve the issue, follow these steps: |
| 40 | + |
| 41 | +1. Check if the SAP ASE server is running. If not running, start the server. |
| 42 | +2. Re-run the pre-registration script with correct instance name, resolvable database host name (or) IP address and database user credentials with permissions to perform Backup and restore operations. |
| 43 | + |
| 44 | +### InvalidLogicalContainerName |
| 45 | + |
| 46 | +**Error code**: `InvalidLogicalContainerName` |
| 47 | + |
| 48 | +**Error message**: Invalid database instance name supplied. |
| 49 | + |
| 50 | +**Recommended action**: Fix the input and retry the operation. If the issue persists, contact Microsoft support. |
| 51 | + |
| 52 | +### ConfigureProtectionFailed |
| 53 | + |
| 54 | +**Error code**: `ConfigureProtectionFailed` |
| 55 | + |
| 56 | +**Error message**: Configure protection operation failed on the instance. |
| 57 | + |
| 58 | +**Recommended action**: To resolve the issue, follow these steps: |
| 59 | + |
| 60 | +1. Check if the database is online. |
| 61 | +2. Check if the database credentials are correct. |
| 62 | +3. if the issue still persists, please contact Microsoft Support for further assistance. |
| 63 | + |
| 64 | +### InvalidWorkloadType |
| 65 | + |
| 66 | +**Error code**: `InvalidWorkloadType` |
| 67 | + |
| 68 | +**Error message**: Invalid workload type. |
| 69 | + |
| 70 | +**Recommended action**: Fix the input and retry the operation. If the issue persists contact Microsoft support. |
| 71 | + |
| 72 | +### GetPluginVersionError |
| 73 | + |
| 74 | +**Error code**: `GetPluginVersionError` |
| 75 | + |
| 76 | +**Error message**: Error while getting plugin version. |
| 77 | + |
| 78 | +**Recommended action**: Retry the operation. If the issue persists contact Microsoft support. |
| 79 | + |
| 80 | +### OperationNotSupportedError |
| 81 | + |
| 82 | +**Error code**: `OperationNotSupportedError` |
| 83 | +**Error message**: Restore Inquire Operation Not Supported. |
| 84 | + |
| 85 | +**Recommended action**: No action is required. Contact Microsoft support for further clarifications. |
| 86 | + |
| 87 | +### GeneralPluginException |
| 88 | + |
| 89 | +**Error code**: `GeneralPluginException` |
| 90 | + |
| 91 | +**Error message**: An exception occurred. |
| 92 | + |
| 93 | +**Recommended action**: This is an internal error. For further assistance contact Microsoft Support. |
| 94 | + |
| 95 | +### DatabaseQueryExecutionError |
| 96 | + |
| 97 | +**Error code**: `DatabaseQueryExecutionError` |
| 98 | + |
| 99 | +**Error message**: An ASE exception occurred while running query on database. |
| 100 | + |
| 101 | +**Recommended action**: Check if database is online and retry the operation. If the issue persists, contact Microsoft support. |
| 102 | + |
| 103 | +### ASEBackupServerNotRunning |
| 104 | + |
| 105 | +**Error code**: `ASEBackupServerNotRunning` |
| 106 | + |
| 107 | +**Error message**: ASE backup server isn't running. |
| 108 | + |
| 109 | +**Recommended action**: Check if database is online, backup server is running, and then retry the operation. If the issue persists, contact Microsoft support. |
| 110 | + |
| 111 | +## Backup error code |
| 112 | + |
| 113 | +### UserErrorASELSNValidationFailure |
| 114 | + |
| 115 | +**Error code**: `UserErrorASELSNValidationFailure` |
| 116 | + |
| 117 | +**Error message**: Log sequence validation failed. Initiating a forced full backup now. |
| 118 | + |
| 119 | +**Recommended action**: Log Sequence Number validation has failed / possible log chain break, a full backup will be performed now to fix it. If error persists after that, contact Microsoft Support. |
| 120 | + |
| 121 | +### DatabaseBackupOperationFailed |
| 122 | + |
| 123 | +**Error code**: `DatabaseBackupOperationFailed` |
| 124 | + |
| 125 | +**Error message**: Database backup failed. |
| 126 | + |
| 127 | +**Recommended action**: Retry the backup operation. If error persists, contact Microsoft Support. |
| 128 | + |
| 129 | +### BackupValidationFailed |
| 130 | + |
| 131 | +**Error code**: `BackupValidationFailed` |
| 132 | + |
| 133 | +**Error message**: Database backup validation failed. |
| 134 | + |
| 135 | +**Recommended action**: Retry the operation. If error persists, contact Microsoft Support. |
| 136 | + |
| 137 | +### DatabaseExistenceValidationFailure |
| 138 | + |
| 139 | +**Error code**: `DatabaseExistenceValidationFailure` |
| 140 | + |
| 141 | +**Error message**: Database existence validation failed. |
| 142 | + |
| 143 | +**Recommended action**: Check if the database exists and is online. If not, create and make the database online. For further assistance, contact Microsoft Support. |
| 144 | + |
| 145 | +### WriteToBackupStreamFailure |
| 146 | + |
| 147 | +**Error code**: `WriteToBackupStreamFailure` |
| 148 | + |
| 149 | +**Error message**: Failure while writing data to backup stream. |
| 150 | + |
| 151 | +**Recommended action**: Retry the operation. If the issue still persists, contact Microsoft Support for further assistance. |
| 152 | + |
| 153 | +### DumpHistoryCorrupted |
| 154 | + |
| 155 | +**Error code**: `DumpHistoryCorrupted` |
| 156 | + |
| 157 | +**Error message**: Dump history file is corrupted due to incorrect syntax. |
| 158 | + |
| 159 | +**Recommended action**: Check for the disk space or any incorrect format in dump history file. If the dump file is corrupted, see the [SAP note to resolve the issue](https://me.sap.com/notes/2167081/E). If the issue still persists, contact Microsoft support. |
| 160 | + |
| 161 | +### GetDatabaseVersionFailure |
| 162 | + |
| 163 | +**Error code**: `GetDatabaseVersionFailure` |
| 164 | + |
| 165 | +**Error message**: Error while fetching database version. |
| 166 | + |
| 167 | +**Recommended action**: Check if the database is in running state. If the issue still persists, contact Microsoft support. |
| 168 | + |
| 169 | +### FullBackupNotPerformed |
| 170 | + |
| 171 | +**Error code**: `FullBackupNotPerformed` |
| 172 | + |
| 173 | +**Error message**: No previous full backups were found. Initiating a forced full backup now. |
| 174 | + |
| 175 | +**Recommended action**: An automatic full backup will be performed. If the error persists afterward, contact Microsoft Support. |
| 176 | + |
| 177 | +### LatestFullBackupIsOld |
| 178 | + |
| 179 | +**Error code**: `LatestFullBackupIsOld` |
| 180 | + |
| 181 | +**Error message**: The latest full backup is more than 15 days old. A forced full backup will be taken now. |
| 182 | + |
| 183 | +**Recommended action**: An automatic full backup will be performed. If the error persists, contact Microsoft Support. |
| 184 | + |
| 185 | +### CompressionLevelNotSet |
| 186 | + |
| 187 | +**Error code**: `CompressionLevelNotSet` |
| 188 | + |
| 189 | +**Error message**: Compression has been enabled but there's no associated compression level. |
| 190 | + |
| 191 | +**Recommended action**: Run the updated pre-registration script in the virtual machine, which will add the default configuration in the `config` file and retry. If the error persists after that, contact Microsoft Support. |
| 192 | + |
| 193 | +## Restore errors |
| 194 | + |
| 195 | +### FailedToCreateDatabase |
| 196 | + |
| 197 | +**Error code**: `FailedToCreateDatabase` |
| 198 | + |
| 199 | +**Error message**: Failed to create database for restoring. |
| 200 | + |
| 201 | +**Recommended action**: To resolve the issue, follow these steps: |
| 202 | + |
| 203 | +1. Ensure that the default device is configured on the database instance. |
| 204 | +2. If the database creation fails for model database with error, resolve the error and retry. |
| 205 | +3. If enough space isn't available in the default device, increase the size of database device (or) change the default device with free space matching the size of source database. |
| 206 | + |
| 207 | +### InvalidDatabaseName |
| 208 | + |
| 209 | +**Error code**: `InvalidDatabaseName` |
| 210 | + |
| 211 | +**Error message**: Database name supplied during alternative location restore isn't meeting the requirements for database creation. |
| 212 | + |
| 213 | +**Recommended action**: Ensure that the database name length shouldn't exceed 30 characters. |
| 214 | + |
| 215 | +### ForceOverwriteOptionNotSet |
| 216 | + |
| 217 | +**Error code**: `ForceOverwriteOptionNotSet` |
| 218 | + |
| 219 | +**Error message**: Restore failed because overwrite options aren't set correctly |
| 220 | + |
| 221 | +**Recommended action**: Choose the **ForceOverwrite** option to perform restore on this database as the database with same name exists. |
| 222 | + |
| 223 | +### InvalidOverwriteOption |
| 224 | + |
| 225 | +**Error code**: `InvalidOverwriteOption` |
| 226 | + |
| 227 | +**Error message**: Restore operation failed due to overwrite option set to null or is invalid. |
| 228 | + |
| 229 | +**Recommended action**: Choose the **ForceOverwrite** option to perform restore on this database. |
| 230 | + |
| 231 | +### PointInTimeRestoreFailed |
| 232 | + |
| 233 | +**Error code**: `PointInTimeRestoreFailed` |
| 234 | + |
| 235 | +**Error message**: Database restore operation to the specified point-in-time has failed with an internal error. |
| 236 | + |
| 237 | +**Recommended action**: Try restoring the database from a previous Full backup. For further assistance contact Microsoft Support. |
| 238 | + |
| 239 | +### RestoreMasterALROLRUnSupported |
| 240 | + |
| 241 | +**Error code**: `RestoreMasterALROLRUnSupported` |
| 242 | + |
| 243 | +**Error message**: Master database can't be restored using Alternate and original location. Please restore using restore as files. |
| 244 | + |
| 245 | +**Recommended action**: To restore the master database, follow these steps: |
| 246 | + |
| 247 | +1. Start the database in Single User mode. |
| 248 | +2. Restore the master database dump using restore as files. |
| 249 | +3. Apply the restore using the dump file. |
| 250 | +4. Restart the database in the `multi user` mode. |
| 251 | + |
| 252 | +### RestoreOperationFailed |
| 253 | + |
| 254 | +**Error code**: `RestoreOperationFailed` |
| 255 | + |
| 256 | +**Error message**: Database restore operation has failed with an error |
| 257 | + |
| 258 | +**Recommended action**: Try restoring the database from a previous Full backup. For further assistance contact Microsoft Support. |
| 259 | + |
| 260 | +### DatabaseRestoreFailed |
| 261 | + |
| 262 | +**Error code**: `DatabaseRestoreFailed` |
| 263 | + |
| 264 | +**Error message**: Database Restore has failed due to an unknown error. |
| 265 | + |
| 266 | +**Recommended action**: Wait for a few minutes and then try the operation again. If the issue persists contact Microsoft support. |
| 267 | + |
| 268 | +### DatabaseOperationFailed |
| 269 | + |
| 270 | +**Error code**: `DatabaseOperationFailed` |
| 271 | + |
| 272 | +**Error message**: Database operation failed with an error. |
| 273 | + |
| 274 | +**Recommended action**: Check if the database user has appropriate permissions. For further assistance contact Microsoft Support. |
| 275 | + |
| 276 | +### MultiActiveConnections |
| 277 | + |
| 278 | +**Error code**: `MultiActiveConnections` |
| 279 | + |
| 280 | +**Error message**: Unable to execute restore operation on database %DatabaseName; because the active connections exceed one, preventing the database from being switched to single server mode. |
| 281 | + |
| 282 | +**Recommended action**: Terminate all active connections and ensure that either there are no remaining connections or only one active connection at most. For further assistance, contact Microsoft Support. |
| 283 | + |
| 284 | + |
| 285 | + |
| 286 | + |
| 287 | + |
| 288 | + |
0 commit comments