Sybase extract login errors

Introduction

Sybase extract login errors happen when the JDBC connection cannot authenticate with the Sybase server. In Kleene, this usually points to a credential, account, database, or connection configuration issue rather than a problem with the extract logic itself. The error message may be generic, so the detailed cause often needs to be confirmed from the chained SQL warnings or the Sybase server logs.

Issue description

A Sybase extract failed with the following JDBC error:

JZ00L: Login failed. Examine the SQLWarnings chained to this exception

This means the Sybase JDBC driver attempted to connect but the login was rejected. The message indicates that additional detail may be available in the chained SQL warnings, which can provide a more specific reason for the authentication failure.

Signs

You may be dealing with this issue if a Sybase extract fails before data is read from the source. The failure usually occurs during the connection or authentication stage rather than during query execution.

Common signs include login failed messages, JDBC authentication errors, references to chained SQL warnings, or repeated failures immediately after credential changes, password expiry, account lockout, or source database changes.

Basic troubleshooting steps

Start with the following checks to narrow down the cause of the error:

• Verify the Sybase username and password configured in the connector.
• Confirm whether the password has expired or recently changed.
• Check whether the Sybase account is locked or disabled.
• Confirm that the login still exists on the Sybase server.
• Test the same credentials directly using a Sybase client.
• Confirm the hostname, port, and database are correct.
• Review the chained SQL warnings or Sybase server logs for the detailed failure reason.
• Check whether the configured authentication method matches the Sybase server requirements.

Common causes and how to fix them

Incorrect username or password

The most common cause is that the connector is using credentials that Sybase does not accept. This can happen after a password change, typo, credential rotation, or copy/paste error.

How to fix it: re-enter the connector credentials and test the same username and password directly with a Sybase client. If the direct test fails, the issue is with the credentials or account rather than Kleene.

Expired or changed password

Sybase may reject a login if the password has expired or was changed outside the connector configuration. The connector may still be using the old value.

How to fix it: confirm the current password with the database owner or DBA, update the connector credentials, and re-run the extract.

Locked or disabled account

The login may be locked after repeated failed attempts, disabled by an administrator, or restricted by a database policy.

How to fix it: ask the DBA to check the login status on the Sybase server. If the account is locked or disabled, it must be unlocked or re-enabled before the extract can connect.

Login removed from the database

The login may exist at the server level but no longer have access to the target database, or it may have been removed entirely.

How to fix it: confirm that the login exists and has permission to access the database used by the connector. Recreate or re-grant access if required.

Wrong Sybase instance or database

If the connector points to the wrong hostname, port, instance, or database, valid credentials may fail because they are being checked against the wrong environment.

How to fix it: confirm the hostname, port, database name, and environment with the customer or DBA. Make sure the connector is pointing to the same Sybase instance used when testing the credentials manually.

Authentication method mismatch

Some Sybase environments may require a specific authentication method or connection configuration. If the connector is not using the expected method, the login can fail even when the credentials are correct.

How to fix it: confirm the required authentication method with the DBA and update the connector configuration if needed.

Practical troubleshooting workflow

1. Read the full JDBC error and confirm it contains JZ00L: Login failed.
2. Check whether any chained SQL warnings are available in the logs.
3. Verify the connector username and password.
4. Test the same credentials directly using a Sybase client.
5. Ask the DBA to confirm whether the account is active, unlocked, and not expired.
6. Confirm that the login still exists and has access to the target database.
7. Check that the connector hostname, port, database, and environment are correct.
8. Review Sybase server logs for the detailed login failure reason.
9. Update the connector credentials or configuration as required.
10. Re-run the extract and confirm that authentication succeeds.