> Expert > Backup and Restore Agents > Databases > Sybase

Restore Troubleshooting for Sybase

Updated

The following section provides information on troubleshooting restores.

Browse Failures

Point in time Table Browse Failures

When you have encryption enabled for the client, point in time table browse operation fails with the following error message:

Pass-phrase protection is on for client [80], but pass-phrase was not specified.

Make sure that the pass phrase is exported to the MediaAgent when encryption is enabled for the client.

  1. From the CommCell Browser, right-click the <Client> and then click Properties.

  2. Click the Encryption tab.

  3. Click Via Pass-Phrase.

  4. Click Export.

  5. In the Destination Computer box, select the MediaAgent.

  6. In the Pass-Phrase box, type the pass-phrase used for encryption.

  7. In the Re-enter Pass-Phrase box, re-type the pass-phrase to confirm.

  8. Click Export.

  9. Click OK.

Restore Failures

Failure of Backups and Restores performed from a remote desktop on Windows

Currently, backups and restores cannot be performed from a remote desktop on Windows.

Use any one of the following solutions that suits your setup:

  • Login to remote desktop using the following command:

    mstsc /v:winclient /console

  • Use netmeeting

  • Use telnet

  • Use the clients console

Full Server Restore is failing on a Windows setup

Issue:

This issue may occur when you use Sybase 15.0 ESD #7 on Windows.

Restoring an entire Sybase server may fail after changing the master database devise size with the following error message:

3952 7a8 04/24 10:28:56 1500012 CvSybDB::AlterDatabase() - ExecuteJob(alter database tempdb on master="6M" , tempdbdev="6M") failed3952 7a8 04/24 10:28:56 1500012 CvSybDBRecovery::AdjustDatabaseUsage() - AlterDatabase failed3952 7a8 04/24 10:28:56 1500012 JM Client CVJobClient::setPendingCause(). same messageid is being sent for the same job id within a short time period. so dropping the JPR3952 7a8 04/24 10:28:5Email6 1500012 CvSybDBRecovery::setPendingCause() - Failed to set the pending cause. please check the logs3952 7a8 04/24 10:28:56 1500012 CvSybSybRecovery::PostLoadDatabase() - AdjustDatabaseUsage failed3952 7a8 04/24 10:28:56 1500012 ClSybRestore::Restore() - PostLoadDatabase failed3952 7a8 04/24 10:28:56 1500012 ClSybRestore::Restore() - Completed count: 13952 7a8 04/24 10:28:56 1500012 ClAgentSybJobUnit::NotifyCommServe() - Entering..3952 7a8 04/24 10:28:56 1500012 Sending FAILED complete message to JM, 1500012

This issue may occur on a Windows setup if you change the database devise size and then take a backup of all the databases except the master database.

Resolution/Workaround:

Whenever you change the devise size on a Windows setup with Sybase 15.0 ESD #7, perform a backup of master database along with all the other databases.

Restoring multiple databases in one job may fail

Sometimes, restoring multiple databases in one job may fail if different streams are used for data and log backups. If you need to restore multiple databases in one job, use the same streams for data and log backups.

Cross Server Restores Fail

Cross server restore will fail if the max page size in destination server is different from that of the source server.

When restoring Sybase databases to a different server, the max page size of source server should be the same as the destination server.

When you browse for the destination server, you will do it based on Max page size. By default, it is 2048 (2k).

You can query in sybase server to get the max page size of the server:

Example:

1> select @@maxpagesize 2> go ----------- 4096 (1 row affected)
Restore Fails because of a Stream Error

The number of streams the restore uses is the same number that is configured on the subclient for data backup or transaction log backups. When the number of streams are not available, you will get the following JPR error.

JPR: Error Code: [62:455] Description: Drive in which Media is mounted is not ready to use. Source: leonard64, Process: MediaManager 

JM log: 
 1]. Level [0] flags [0] id [0] overwrite [0] append [0] CustId[0]. 
 12528 2df0 10/21 16:22:05 143280 Scheduler Ignored pending cause 
 [The operation could not be completed as there are not enough drives that are unreserved and online with an active controller.]::Client [leonard64] Application [MediaManager] Message Id
  [1040187471] RCID [0] Reservation Id [-1]. Level [0] flags [0] id [0] 
 overwrite [0] append [0] CustId[0].

Example

The subclient is configured for 4 primary backup data streams. You run a secondary copy to the table library and there are only 2 streams available. The restore fails.

SYB0006: Performing a Sybase Server Restore When You Have Deleted Databases

Symptom

Use this procedure when you want to perform a Sybase Server Restore on a backup that contains deleted databases.

This scenario can happen when you perform a backup and then delete the databases on the Sybase server. The Commvault backup contains databases that no longer exist on the Sybase server.

You can exclude the databases from the restore.

Resolution

  1. From the CommCell Browser, expand Client Computers > client > Sybase.

  2. Right-click the instance, point to All Tasks and then click Browse and Restore.

    The Browse and Restore Options dialog box is displayed.

  3. On the Time Range tab, click View Content.

  4. On the client screen:

    1. In the right pane, select the server that you want to restore.

    2. In the left pane, clear all entries for databases that you deleted after the backup completed.

    3. Click Recover All Selected.

      The Restore Options dialog box is displayed.

  5. On the General tab, select the Sybase Create Devices check box.

  6. Click OK to start the restore.

SYB0007: A Sybase Entire Server Restore May Fail after the Software Completes the Load of the Master Database

Symptom

The Sybase restore fails after the software loads the Sybase master database.

Resolution

The restore fails because the shutdown of the Sybase server does not complete before the software tries to restart the Sybase server.

Set the sSybPostLoadWait additional setting to a value that is greater than 20 seconds.

  1. From the CommCell Browser, right-click the client, and then click Properties:

    The Client Properties dialog box is displayed.

  2. On the Additional Settings tab, click Add.

    The Add Additional Settings dialog box is displayed.

  3. Enter the details for the additional setting:

    1. In the Name box, type sSybPostLoadWait.

    2. In Category box, select SybaseAgent.

    3. In the Type box, select Integer.

    4. In Value box, type the number of seconds to delay the Sybase server restart.

    5. Click OK to close the Add Additional Settings dialog box.

  4. Click OK to close the Client Properties dialog box.

SYB0008: Restore failed because of corrupt database

Symptom

If the Sybase master database is corrupt, you see the following Job Pending Reason (JPR):

Error Code: [71:40] Description: Connection to Sybase DataServer failed, Please make sure that Sybase SA user's password is empty before restoring master database or choose create device option in GUI. Source: sybserver5_3, Process: ClSybAgent

The software sends the following message.

13009 32d1 09/10 19:08:17 136542 CvSybSysRecovery::StartServerInRecoveryMode() - 00:00:00000:00000:2015/09/10 19:08:17.25 kernel The configuration area in device '/sybase/syb155/data/master.dat' appears to be corrupt. The server cannot continue and will shut down.

Resolution

Manually restore the Sybase master database.

SYB0009: Restore failed because the configuration file is not configured in the CommCell Console

Symptom

If the Sybase configuration file is not set in the CommCell Console Instance Properties for the database, you see the following Job Pending Reason (JPR):

Error Code: [71:40] Description: Connection to Sybase DataServer failed, Please make sure that Sybase SA user's password is empty before restoring master database or choose create device option in GUI. Source: sybserver5_3, Process: ClSybAgent

The following message is in the client log.

Configuration Error: Configuration file, '/usr/sybaset/sybase150/ASE-15_0', does not exist.

Resolution

Verify the Sybase configuration file location and name and set that value in the Instance Properties dialog box, Configuration File box.

SYB0010: A Restore of the Sybase syssecurity database fails

Symptom

If you restore a Sybase syssecurity database and the SA user does not have the Sybase system security officer role, you receive the following error

19355 f7f9e720 11/04 17:36:22 3741916 CvSybDB::SetEnableAuditing() - ExecuteJob(exec sp_configure "auditing",0) failed 
19355 f7f9e720 11/04 17:36:22 3741916 CvSybGenRecovery::PreLoadDatabase() - exec sp_configure "auditing", 0 failed with an error [You must have any of the following role(s) to execute this command/procedure: 'sso_role' . Please contact a user with the appropriate role for help.]

Resolution

Configure the SA user to have the system security officer role.

SYB0011: A Restore of the Sybase Server Fails When Encryption is Set

Symptom

A Sybase server restore can fail when you have enabled encryption and the character set sort order has changed to non-default values. The error message looks like the following:

3769 eb9 07/29 00:23:50 2146 
 CvSybSysRecovery::UpdateCharSetAndSortOrder() - Command [/opt/sybase157/ASE-15_0/bin/charset -TEST -Usa -P binary.srt utf8 < /dev/null] 
 3769 eb9 07/29 00:23:50 2146 
 CvSybSysRecovery::ExecuteSystemCommand() - Command to execute: /opt/sybase157/ASE-15_0/bin/charset -SPIYUSHSYBSNAP -Usa -P binary.srt utf8 < /dev/null 
 3769 eb9 07/29 00:23:51 2146 
 CvSybSysRecovery::ExecuteSystemCommand() - OUTPUT: SQLServer message 1640, state 2, severity 16: 
 3769 eb9 07/29 00:23:51 2146 
 CvSybSysRecovery::ExecuteSystemCommand() - OUTPUT: Adaptive Server requires encryption of the login password on the network. 
 3769 eb9 07/29 00:23:51 2146 
 CvSybSysRecovery::ExecuteSystemCommand() - OUTPUT: 
 3769 eb9 07/29 00:23:51 2146 
 CvSybSysRecovery::ExecuteSystemCommand() - OUTPUT: SQLServer message 4002, state 1, severity 14: 
 3769 eb9 07/29 00:23:51 2146 
 CvSybSysRecovery::ExecuteSystemCommand() - OUTPUT: Login failed. 
 3769 eb9 07/29 00:23:51 2146 
 CvSybSysRecovery::ExecuteSystemCommand() - OUTPUT: 
 3769 eb9 07/29 00:23:51 2146 
 CvSybSysRecovery::ExecuteSystemCommand() - OUTPUT: CT-LIBRARY error: 
 3769 eb9 07/29 00:23:51 2146 
 CvSybSysRecovery::ExecuteSystemCommand() - OUTPUT: ct_connect(): protocol specific layer: external error: The attempt to connect to the server failed.

Resolution

  1. Edit the Sybase configuration file and set the 'net password encryption reqd' parameter to '0'.

  2. Perform the restore.

  3. Edit the Sybase configuration file and set the 'net password encryption reqd' parameter to the value that you want.

SYB0012: The Sybase tempdb database does not start after a restore and displays error 806

Symptom

After a successful Sybase server restore, the tempdb database does not start and an error message similar to the following is displayed.

7143678 1 06/04 13:57:15 284437 CvSybSysRecovery::StartServerInRecoveryMode() - 00:00000:00001:2016/06/04 13:57:15.37 server Could not find virtual page for logical page 2048 in database 'tempdb'.

Resolution

For more information on the error, go to the SAP website, Error 806.

  1. Restart the Sybase Adaptive Server when the error message indicates the tempdb, because Sybase rebuilds the tempdb database during a restart.

  2. If the restart does not work, contact your software provider.

SYB0013: A master database restore marks the tempdb suspect if the segments of the tempdb are extended on the master

Symptom

If the system tempdb is extended on the master device apart from the default allocation, a master database restore marks the tempdb suspect.

Example

The tempdb is allocated on the master database as follows

alter database tempdb on master = "10M" 
 go 
 alter database tempdb on master = "2M" 
 go 
 alter database tempdb on mytempdev = "10M" 
 go:

The following error message is displayed.

3256 ed051820 06/16 05:36:37 516499 CvSybSysRecovery::StartServerInRecoveryMode() - 00:0006:00000:00001:2016/06/16 05:36:37.64 server Database 'tempdb' cannot be opened. An earlier attempt at recovery marked it 'suspect'. Check the ASE errorlog for information as to the cause

Resolution

For more information on the error, go to the SAP website, Error 806.

  1. Shut down the database and start it in recovery mode

  2. See the SAP recommended KB article https://launchpad.support.sap.com/#notes/2195104 or run the following queries.

This query returns a value that indicates that the tempdb is marked suspect 

select status from master..sysdatabases where dbid = 2 
 go

After this query, only the first row is affected.

use master go begin transaction go update sysdatabases set status = status ^ 256 where status & 256 = 256 and name="tempdb" 
 go

Check the status of the tempdb. The value is 77 or another value.

select status from master..sysdatabases where dbid = 2 
 go 
 commit transaction 
 go

SYB0015: A load transaction operation fails when a cumulative backup was run on the same database

Issue

When you perform a restore operation, a load transaction operation fails when a cumulative backup was run on the same database.

Resolution

SAP recommends that you do not use the no_truncate option for a dump transaction. If the operation has been run, you must restore to disk (application free restore), and then manually load the database by using the override parameter. For more information, go to the SAP knowledge base, 226903 – Error 4334.

SYB0016: A Restore of an Entire Sybase Database Fails When It Loads a Temporary Database

Issue

A restore of an entire Sybase database fails when it loads a temporary database. The following error appears:

Description: Loading database failed :[Temporary databases cannot be loaded. ]

Resolution

Sybase has a restriction that prevents temporary databases from loading. You must clear the check box for all temporary databases when you select the data to restore. After the restore completes, you can manually create the databases by using the "create temporary database" command.

SYB0017: A Sybase Full Restore fails When There are User Temporary Databases

Issue

A full server restore might fail because the Sybase software cannot load the user temporary databases. The following error appears:

[Loading database failed :[temporary database cannot be loaded]

Resolution

Use browse to select all the database except the user temporary databases for the restore operation. Select the Sybase Create Devices check box (Restore Options dialog box, General tab) when you perform the restore.

SYB0018: A Sybase Full Server Restore Operation Might Fail with Connection Errors If Net Password Encryption Required Is Set to 2

Issue

A full server restore might fail with connection errors because the net password encryption required is set to 2. The following error appears:

7356  19b8  01/03 14:54:17 ### ClSybBrowseAgent::SybBrowse() - The read buffer is: <ERROR>Adaptive Server requires encryption of the login password on the network. Login failed. </ERROR>
    

7356  19b8  01/03 14:54:17 ### ClSybBrowseAgent::ParseReturn() - Extracted error string is: Adaptive Server requires encryption of the login password on the network. Login failed.

Resolution

Before running a restore operation, set the network password encryption to zero using the command below:

net password encryption reqd=0

Then, rename the ocs.cfg file located at sybase home/OCS dir/config.

SYB0019: A Sybase Restore Operation for Databases that are Sharing A Device Might Fail with Drop Device Failure Error

Issue

A Sybase restore might fail with drop device failure error for databases sharing a device. The following error appears:

6048  212c  02/14 14:07:52 3827 CvSybDB::DropDevice() - Failed to drop the database [test]
    

6048  212c  02/14 14:07:52 3827 CvSybDB::DropDevice() - Drop Device Command: sp_dropdevice saidata
    

6048  212c  02/14 14:07:52 3827 cv_syb_servermsg_cb() - Message String: Device is being used by a database. You can't drop it.

Resolution

Manually drop databases and device that is shared between multiple databases using the commands below:

drop database <database_name1>, <database_name2>
    

sp_dropdevice <device_name>

Then, run the restore operation again.

SYB0020: A Sybase Restore Operation on Windows Fail if Multiple Sybase Home Exist at Destination Client

Issue

A Sybase restore might fail on a Windows operating system if multiple Sybase home exist on the destination client. The following error appears:

12712 31a4  10/03 15:34:31 ### cv_syb_clientmsg_cb() - Message String: ct_connect(): directory service layer: internal directory control layer error: Requested server name not found.

Resolution

Make entries for all the Sybase servers in each Sybase home (.ini) file.