cancel
Showing results for 
Search instead for 
Did you mean: 

SAP ASE

narasimhankrishna
Participant
0 Kudos

Hi Experts,

We have installed the NW SAP with SAP ASE successfully. Now while login to database it's showing an error as below:

Login failed.

CT-LIBRARY error:

        ct_connect(): protocol specific layer: external error: The attempt to connect to the s     erver failed.

Thanks,

Narasimhan

Accepted Solutions (1)

Accepted Solutions (1)

Johan_sapbasis
Active Contributor
0 Kudos

Hi Krishna,

open CMD window.

change directory to your path, change SID to your SID

D:\sybase\SID\OCS-16_0\bin

then login

D:\sybase\ERD\OCS-16_0\bin>isql -Usapsa -SSID -X

Use the password you set during your install.

-U specifies the user

-S the SID DBNAME

-X For encryption.

Or are you getting this error on another location or within abap/dbacockpit?

Johan

victoria_normand
Contributor
0 Kudos

Hi,
Please ensure that the isql command has the -X flag as mentioned Johan, or let us know how are doing the access to the database.

Best regards,
Victoria.

Answers (4)

Answers (4)

crisnormand
Active Participant
0 Kudos

Hello Narasimhan,

As a Correct Answer has been marked for this thread, and to keep the thread clear for future 'readers', kindly open new threads for new requests.

Regarding the sa unlock: as mentioned before, there is no needs to unlock the "sa" user when working with SAP ASE in a Business Suite context. We need sa during updates/upgrades, but in that case this is done automatically when using saphostctrl.

But generally speaking, you shouldn't need sa login for administration tasks: in a Business Suite context, main tasks can be done via DBA Cockpit.

In a BS context, the login that has sso_role is sapsso. So you should be able to do other tasks via isql with login sapsa or sapsso.

It is not recommended to grant/revoke roles either to existing users. When you install a SAP application running on SAP ASE, all the necessary logins and users are created and required roles granted.

I hope this helps. If you have further questions about sa locking or roles, don't hesitate to open a new thread.

Thanks

Regards,

Cris


narasimhankrishna
Participant
0 Kudos

Hi Nicolaas,

Thanks, Now i am able to login successfully into DB vi isql command. But when i try to unlock the SA user it's showing the below error. Please help.

1> sp_locklogin 'sa', 'unlock'

2> go

Msg 567, Level 16, State 1:Server 'SYB', Procedure 'sp_locklogin', Line 243:

You must have the following role(s) to execute this command/

'sso_role'. Please contact a user with the appropriate role

(return status = 1)

How to assign the role sso_role to sa or saposs users.

Thanks,

Narasimhan

Johan_sapbasis
Active Contributor
0 Kudos

Hi,

To my knowledge only the SA user can assigned the roles. Is your master password from your installation not consistent?

But you can try to assign the role.

This will show current roles for sa.

sp_displaylogin sa

go

grant role sso_role to sa

go

sp_displaylogin sa

go

Something seems a bit strange here, is this a clean installation?

Johan

narasimhankrishna
Participant
0 Kudos

Hi Johan,

Thanks, When i issued the command it showing that user 'sa' is currently locked.

thssybasetst:sybadm 77> isql -Usapsa -P<password> -SSYB -X

1> sp_displaylogin sa

2> go

Suid: 1

Loginame: sa

Fullname:

Default Database: master

Default Language:

Auto Login Script:

Configured Authorization:

        sa_role (default ON)

        sso_role (default ON)

        oper_role (default ON)

        sybase_ts_role (default ON)

        mon_role (default ON)

        sa_serverprivs_role (default ON)

Locked: YES

        Date when locked: Jun 13 2015 10:57AM

        Reason: Account locked by ASE by manually executing sp_locklogin

        Locking suid: sapsso

Date of Last Password Change: Jun 13 2015  9:57AM

Password expiration interval: 0

Password expired: NO

Minimum password length: 6

Maximum failed logins: 0

Current failed login attempts:

Authenticate with: AUTH_DEFAULT

Login Password Encryption: SHA-256

Last login date: Jun 13 2015 10:57AM

Exempt inactive lock: 0

(return status = 0)

Let me know how to unlock this user.

Thanks,

Narasimhan K

Message was edited by: Maria-Cristina NORMAND Removing password.

Johan_sapbasis
Active Contributor
0 Kudos

Hi Please edit your last post never paste your actual password.


> isql -Usapsa -Premovethisfromyourlastpost -SSYB -X


So to unlock.

http://infocenter.sybase.com/archive/index.jsp?topic=/com.sybase.help.ase_15.0.sag1/html/sag1/sag160...


sp_locklogin [ {login_name | "all"}, { "lock" | "unlock" } ]


so you use the following:


sp_locklogin 'sa', 'unlock'

go

sp_displaylogin sa

go


Then see if it unlocked.


Please remove your password from all posts.


Kind Regards,


Johan


Johan_sapbasis
Active Contributor
0 Kudos

HI,

It could quite possibly be a different problem like all your db connections being fully utilized.

D:\sybase\SID\ASE-16_0\install

check the SID.log  file for errors at the end of the file.

Johan

parth_raval
Participant
0 Kudos

Hi Krishna,

Please try to login using sapsa user with isql command.

And if sapsa user is locked then unlock it using sapsso user. It will give output given below.

1> sp_locklogin 'sa', 'unlock'

2> go

Account unlocked.

(return status = 0)


You need to as syb<SID> user and connect to sybase database with sapsa (Database Administartor user) to perform out tasks.

Best Regards,

Parth Raval

victoria_normand
Contributor
0 Kudos

Hi Parth,

There is no needs to unlock the "sa" user, that would be done mainly during updates/upgrades.

Best regards,
Victoria.

parth_raval
Participant
0 Kudos

Hi Maria,

I know there is no need to unlock the sa user. But if he is asystem administrator then there is no issue to use sa user to perform tasks.

Well I thought this will help him in simple way..

I appreciate your comment Maria..keep it up..

narasimhankrishna
Participant
0 Kudos

Hi Victoria,

I am not able to login via SA user. Please help.

thssybasetst:sybadm 71> isql -Usa -SSYB -X

Password:

Msg 4002, Level 14, State 1:

Server 'SYB':

Login failed.

CT-LIBRARY error:

        ct_connect(): protocol specific layer: external error: The attempt to connect to the server failed.