Also see following error messages:
EXP-00028: Failed to open %s for write
EXP-00028: Failed to open %s for write
ORA-00028: your session has been killed
You will need to reconnect in order to continue to work with your application.
At times, a database administrator might choose to kill your session, because you are holding a lock, it consumes too many resources , ...
The database administrator is doing this using the 'alter system kill session' command.
SQL> select sid, serial# from v$session where username='MYUSER';
SID SERIAL#
---------- ----------
78 6569
SQL> alter system kill session '78,6569';
System altered.
Now, if you access a new statement in your session - which is killed - you will see the error:
SQL> select * from dual; select * from dual * ERROR at line 1: ORA-00028: your session has been killed
Welcome to our forum for Oracle error: ORA-00028 Add your own message
At the moment there are no forum messages. You can add your own question.
Add your message
Ask Your Question
If you need more information about this particular error message, you can leave a forum message.
We are replying to this message whenever we have some spare time, so please do not consider this as a private 'solve my critical issue asap' service.
Should you need professional Oracle Assistance to make your project a success, please have a look at our consultancy services.
Spam Protection
In order to prevent automatic generation of messages, we are asking for a validation code. This code is unique and is generated every time a new message is asked.
If you do not enter the validation correctly, your message will not be recorded.
Forum Rules
Please be polite, do not USE ALL UPPERCASE, no insults, violance or any other threats.
