No Image

Login is already in use

397 просмотров
10 марта 2020

This is on a local Oracle database. Does anyone know how I can free up this user?

  • 1730 Просмотров
  • Метки: нет (добавить)
1. Re: The user is already logged in. Please use another login name.

This is on a local Oracle database. Does anyone know how I can free up this user?

What application is this?. The database doesn’t care if the same user is logged on multiple times.

  • Мне нравится Показать отметки "Мне нравится" (0) (0)
  • Действия
2. Re: The user is already logged in. Please use another login name.

This is on a local Oracle database. Does anyone know how I can free up this user?

This behavior is a local customization & not part of any standard Oracle release.

  • Мне нравится Показать отметки "Мне нравится" (0) (0)
  • Действия
3. Re: The user is already logged in. Please use another login name.

Does anyone know? Yes, probably whomever wrote the application you’re using.

  • Мне нравится Показать отметки "Мне нравится" (1) (1)
  • Действия
4. Re: The user is already logged in. Please use another login name.

I’m not quite certain what you mean by ‘free up this user’. If you’re not the DBA then you have nothing to do but wait for whoever got to it first to finish using it. As others have mentioned Oracle doesn’t care HOW many times a particular user logs in; I can, up to the limit set for sessions, keep logging in as a user named Bertrand and Oracle will never issue that message:

SQL> select username

2 from v$session

3 where username is not null

Some pre-login process is giving you that message (meaning something in the application is checking the login credentials BEFORE the logon attempt is made).

Contact the vendor; it’s their issue, not yours.

  • Мне нравится Показать отметки "Мне нравится" (1) (1)
  • Действия
5. Re: The user is already logged in. Please use another login name.

this message is displayed on oracle database or another product

  • Мне нравится Показать отметки "Мне нравится" (0) (0)
  • Действия
Читайте также:  Стиральный порошок омо из финляндии отзывы
6. Re: The user is already logged in. Please use another login name.

I can, up to the limit set for sessions, keep logging in as a user named Bertrand and Oracle will never issue that message:

SQL> select username

2 from v$session

3 where username is not null

Hmmm – I don’t see an ‘user named Bertrand’ in there anywhere.

  • Мне нравится Показать отметки "Мне нравится" (0) (0)
  • Действия
7. Re: The user is already logged in. Please use another login name.

As others already said, it has nothing to do with Oracle database. If there is a resource limit set for the SESSION_PER_USER, then you’ll get the error message:

ORA-02391: exceeded simultaneous SESSIONS_PER_USER limit

and not that one you specified.

Are you using Primavera, because such message comes up with thst product? If yes, then please check this document, which contains the workaround/solution for this issue: https://ccsspl123-public.sharepoint.com/Support%20Documents/Project%20Management%20DB%20User%20login%20error%20-%20Solut…

  • Мне нравится Показать отметки "Мне нравится" (0) (0)
  • Действия
8. Re: The user is already logged in. Please use another login name.

That’s because all of the letters except the "B" are silent.

Note: I’ll make a BERTRAND user account next time.

  • Мне нравится Показать отметки "Мне нравится" (0) (0)
  • Действия
9. Re: The user is already logged in. Please use another login name.

As others already said, it has nothing to do with Oracle database. If there is a resource limit set for the SESSION_PER_USER, then you’ll get the error message:

ORA-02391: exceeded simultaneous SESSIONS_PER_USER limit

If there is a resource limit set for the SESSION_PER_USER, then you’ll get the error messag e the application will get an appropriate error code. What message the application chooses to return to the user is entirely up to the application. If the application is sqlplus or SQL Dev, it will choose to return the message:

Читайте также:  Вся правда о теплэко

ORA-02391: exceeded simultaneous SESSIONS_PER_USER limit

  • Мне нравится Показать отметки "Мне нравится" (0) (0)
  • Действия
10. Re: The user is already logged in. Please use another login name.

Yes, of course. In practice, I saw too many applications, which didn’t handled those exceptions correctly. They just spilled out the error message got from the database.

  • Мне нравится Показать отметки "Мне нравится" (0) (0)
  • Действия
11. Re: The user is already logged in. Please use another login name.

I’d rather that than the useless ‘application failure accessing database’ type messages that seem to be increasingly prevalent.

At a previous site there was a directive to hide error messages from the user.

Fortunately most of the apps used were so old and out of warrranty the directive was pretty much unenforcable.

I can’t get my head round why on earth you’d want to stop providing a message that helps identify the issue encountered and replace it by some generic message.

  • Мне нравится Показать отметки "Мне нравится" (2) (2)
  • Действия
12. Re: The user is already logged in. Please use another login name.

Yes, of course. In practice, I saw too many applications, which didn’t handled those exceptions correctly. They just spilled out the error message got from the database.

They just spilled out the error message got from the database

That IS the correct way. Far better that than swallowing the error and substituting their own meaningless message.

  • Мне нравится Показать отметки "Мне нравится" (2) (2)
  • Действия
13. Re: The user is already logged in. Please use another login name.

Wellllll, that depends. If you have a web page exposed to the universe, you probably don’t want the universe to see unhandled exceptions.

Читайте также:  Приложение для входящих звонков андроид

This username is already in use!
This e-mail is already in use!

Это имя пользователя уже используется!
Это электронная почта уже используется!

это имя уже используется!
это электронная почта используется уже!

My current Apple ID, for which all of my content has been downoaded (e.g., music, apps) is associated with a work email address that I will no longer have access to in the near future. In my Apple ID account, I noticed I had two alternate emails listed, one is my .me account and the other is my .gmail account. I use my .gmail account, and it is the primary email I use with friends and family. I noticed both were not verified, and when I tried to, it said they were both associated with other accounts. I was able to log into a separate Apple ID account I must have set up at tone point with my .gmail, and I changed the email address to a new one I created. I also deleted the gmail account from any other Apple-relted account I could think of. I am still gettgin the same error message when I try to add it to my current Apple ID: "This email address is already in use or you may already have an Apple ID associated with this email address. Please try again or sign in using your existing Apple ID."

My concern is this: with FaceTime and now iMessage, it seems more important than ever that I am able to use my correct email address. With iOS5 beta, I cannot enter either my .gmail or.me accounts under "You can be reached for messages at:" as I get an error stating: Unable to verify email because it is already in use."

How can I remedy this issue and assign my .gmail account to my Apple ID?

Комментировать
397 просмотров
Комментариев нет, будьте первым кто его оставит

Это интересно
Adblock
detector