Skip to content

Commit 96b4056

Browse files
author
AbhishekMallick-MS
committed
ASE TS added
1 parent 6025466 commit 96b4056

File tree

1 file changed

+204
-0
lines changed

1 file changed

+204
-0
lines changed
Lines changed: 204 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,204 @@
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**: 1. Check if the database is online. 2. Check if the database credentials are correct . 3. if the issue still persists, please contact Microsoft Support for further assistance.
59+
60+
61+
InvalidWorkloadType
62+
ErrorCode: InvalidWorkloadType
63+
Message: Invalid workload type.
64+
RecommendedAction: Fix the input and retry the operation. If the issue persists contact support.
65+
66+
GetPluginVersionError
67+
ErrorCode: GetPluginVersionError
68+
Message: Error while getting plugin version.
69+
RecommendedAction: Retry the operation. If the issue persists contact support.
70+
71+
OperationNotSupportedError
72+
ErrorCode: OperationNotSupportedError
73+
Message: Restore Inquire Operation Not Supported.
74+
RecommendedAction: No action required. Contact support for further clarifications.
75+
76+
GeneralPluginException
77+
ErrorCode: GeneralPluginException
78+
Message: An exception occurred.
79+
RecommendedAction: Internal error. For further assistance please contact Microsoft Support.
80+
81+
DatabaseQueryExecutionError
82+
ErrorCode: DatabaseQueryExecutionError
83+
Message: An ASE exception occurred while running query on database.
84+
RecommendedAction: Please check if database is online and retry the operation. If the issue persists, contact support.
85+
86+
87+
88+
89+
ASEBackupServerNotRunning
90+
91+
ErrorCode: ASEBackupServerNotRunning
92+
93+
Message: ASE backup server is not running.
94+
RecommendedAction: Please check if database is online, backup server is running and retry the operation. If the issue persists, contact support.
95+
96+
97+
Backup Error Code
98+
UserErrorASELSNValidationFailure
99+
ErrorCode: UserErrorASELSNValidationFailure
100+
Message: Log sequence validation failed. Initiating a forced full backup now.
101+
RecommendedAction: 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, please contact Microsoft Support.
102+
DatabaseBackupOperationFailed
103+
ErrorCode: DatabaseBackupOperationFailed
104+
Message: Database backup failed.
105+
RecommendedAction: Retry backup. If error persists, please contact Microsoft Support.
106+
BackupValidationFailed
107+
ErrorCode: BackupValidationFailed
108+
Message: Database backup validation failed.
109+
RecommendedAction: Retry the operation. If error persists, please contact Microsoft Support.
110+
DatabaseExistenceValidationFailure
111+
ErrorCode: DatabaseExistenceValidationFailure,
112+
Message: Database existence validation failed.
113+
RecommendedAction: Check if database exists and is online. If not, create and make it online. For further assistance, please contact Microsoft Support.
114+
WriteToBackupStreamFailure
115+
ErrorCode: WriteToBackupStreamFailure
116+
Message: Failure while writing data to backup stream.
117+
RecommendedAction: Retry the operation. If the issue still persists, please contact Microsoft Support for further assistance.
118+
DumpHistoryCorrupted
119+
ErrorCode: DumpHistoryCorrupted
120+
Message: Dump history file is corrupted due to incorrect syntax.
121+
RecommendedAction: Check for the disk space or any incorrect format in dump history file.If the dump file is corrupted, please go through the steps mentioned in sap note to resolve the issue https://me.sap.com/notes/2167081/E . Please contact support if the issue is still not resolved.
122+
123+
GetDatabaseVersionFailure
124+
125+
ErrorCode: GetDatabaseVersionFailure
126+
127+
Message: Error while fetching database version.
128+
RecommendedAction: Check if database is in running state. Please contact support if the issue is still not resolved.
129+
130+
FullBackupNotPerformed
131+
ErrorCode: FullBackupNotPerformed
132+
Message: No previous full backups were found. Initiating a forced full backup now.
133+
RecommendedAction: An automatic full backup will be performed now. If the error persists afterward, please contact Microsoft Support.
134+
135+
LatestFullBackupIsOld
136+
ErrorCode: LatestFullBackupIsOld
137+
Message: The latest full backup is more than 15 days old. A forced full backup will be taken now.
138+
RecommendedAction: An automatic full backup will be performed now. If the error persists, please contact Microsoft Support.
139+
140+
141+
CompressionLevelNotSet
142+
143+
ErrorCode: CompressionLevelNotSet
144+
Message: Compression has been enabled but there is no associated compression level.
145+
RecommendedAction: Please run the updated pre-registration script in the virtual machine, which will add the default configuration in config and retry. If the error persists after that, please contact Microsoft Support.
146+
147+
148+
Restore Errors
149+
FailedToCreateDatabase
150+
ErrorCode: FailedToCreateDatabase
151+
Message: Failed to create database for restoring.
152+
RecommendedAction: 1. Make sure default device configured on the database instance.
153+
2.Database creation failed with model database is in error. Please resolve the error and retry.
154+
3. Enough space is not available in the default device. Please increase the size of database device (or) change the default device having free space matching the size of source database.
155+
InvalidDatabaseName
156+
ErrorCode: InvalidDatabaseName
157+
Message: Database name supplied during alternative location restore is not meeting the requirements for database creation.
158+
RecommendedAction: Database length should not exceed 30 characters.
159+
ForceOverwriteOptionNotSet
160+
ErrorCode: ForceOverwriteOptionNotSet
161+
Message: Restore failed because overwrite options is not set correctly
162+
RecommendedAction: Please choose ForceOverwrite option to perform restore on this DB as the database with same name exist.
163+
164+
InvalidOverwriteOption
165+
ErrorCode: InvalidOverwriteOption
166+
Message: Restore operation failed due to overwrite option set to null or is invalid.
167+
RecommendedAction: Please choose ForceOverwrite option to perform restore on this DB.
168+
169+
PointInTimeRestoreFailed
170+
ErrorCode: PointInTimeRestoreFailed
171+
Message: Database restore to the specified point in time failed with an internal error.
172+
RecommendedAction: Try restoring the database from a previous Full backup. For further assistance please contact Microsoft Support.
173+
174+
RestoreMasterALROLRUnSupported
175+
ErrorCode: RestoreMasterALROLRUnSupported
176+
Message: Master database cannot be restored using Alternate and original location. Please restore using restore as files.
177+
RecommendedAction: 1. Start the database in Single User mode.
178+
2. Restore the master database dump using restore as files.
179+
3. Apply the restore using the dump file.
180+
4. Restart the database in multi user mode.
181+
182+
183+
RestoreOperationFailed
184+
ErrorCode: RestoreOperationFailed
185+
Message: Database restore failed with an error
186+
RecommendedAction: Try restoring the database from a previous Full backup. For further assistance please contact Microsoft Support.
187+
DatabaseRestoreFailed
188+
ErrorCode: DatabaseRestoreFailed
189+
Message: Database Restore has failed due to an unknown error.
190+
RecommendedAction: Wait for a few minutes and then try the operation again. If the issue persists please contact Microsoft support.
191+
DatabaseOperationFailed
192+
ErrorCode: DatabaseOperationFailed
193+
Message: Database operation failed with an error.
194+
RecommendedAction: Please check database user has appropriate permissions. For further assistance please contact Microsoft Support.
195+
MultiActiveConnections
196+
ErrorCode: MultiActiveConnections
197+
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.
198+
RecommendedAction: Terminate all active connections and ensure that either there are no remaining connections or only one active connection at most. For further assistance, please contact Microsoft Support.
199+
200+
201+
202+
203+
204+

0 commit comments

Comments
 (0)