Home » RDBMS Server » Security » ORA-28663
ORA-28663 [message #548321] Wed, 21 March 2012 06:59 Go to next message
ashishs
Messages: 40
Registered: May 2011
Member

Hey ,

I am getting this error ora-28663 cannot encrypt sys owned objects,...any solution ,how i can perform TDE.
Re: ORA-28663 [message #548324 is a reply to message #548321] Wed, 21 March 2012 07:09 Go to previous messageGo to next message
Littlefoot
Messages: 19678
Registered: June 2005
Location: Croatia, Europe
Senior Member
Account Moderator
My ORA-28663 description is somewhat different:
Oracle

ORA-28663: Logging/Nologging attribute can not be specified in the statement ALTER TABLE ADD OVERFLOW

Cause: Attempt to specify LOGGING for a Alter Table Add Overflow.

Action: don't do that


What did you do, anyway? How? What would you want to get as a result?
Re: ORA-28663 [message #548326 is a reply to message #548324] Wed, 21 March 2012 07:36 Go to previous messageGo to next message
Michel Cadot
Messages: 59403
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Yes it is a mix in figures:
ORA-28336: "cannot encrypt SYS owned objects"
 *Cause: An attempt was made to encrypt columns in a table owned by SYS.

 *Action:


This is why we ALWAYS say copy and paste; such error can't then happen.

To answer the question... hmmm what is the question?

Regards
Michel
Re: ORA-28663 [message #549185 is a reply to message #548326] Wed, 28 March 2012 08:07 Go to previous messageGo to next message
cookiemonster
Messages: 11068
Registered: September 2008
Location: Rainy Manchester
Senior Member
Have you created your own tables in sys?
Re: ORA-28663 [message #549230 is a reply to message #549185] Thu, 29 March 2012 00:25 Go to previous messageGo to next message
ashishs
Messages: 40
Registered: May 2011
Member

Yes, i create the table in sys schema..but at login time i use own user like xx as sysdba and when i create table that comes in sys schema. if u login as sysdba then default schema is SYS or if connect as sysoper then default schema PUBLIC. i don't know why table comes under sys schema.

[Updated on: Thu, 29 March 2012 00:29]

Report message to a moderator

Re: ORA-28663 [message #549231 is a reply to message #549230] Thu, 29 March 2012 00:29 Go to previous messageGo to next message
Littlefoot
Messages: 19678
Registered: June 2005
Location: Croatia, Europe
Senior Member
Account Moderator
Well, that (creating your tables in SYS) is not a very good idea. I'd suggest you to move it to your own schema.
Re: ORA-28663 [message #549232 is a reply to message #549230] Thu, 29 March 2012 00:58 Go to previous messageGo to next message
Michel Cadot
Messages: 59403
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Quote:
i don't know why table comes under sys schema


Because you connect as sysdba.

- Never ever use SYS (or SYSDBA) but for maintenance purpose (startup, shutdown, backup, recover)
- SYS/SYSDBA is special
- SYS/SYSDBA is Oracle proprietary (try to open a SR/TAR starting with "i did that with SYS/SYSDBA" and you'll see the immediate answer)
- SYS/SYSDBA does not act like any other user
- When you use SYS/SYSDBA Oracle deactivates some code path and activates others
- Whatever you do with SYS/SYSDBA will neither validate nor invalidate the same thing with any other user.

NEVER EVER use SYS/SYSDBA for anything that can be done by another user.
Use SYS/SYSDBA ONLY for something that can't be done by someone else.


Regards
Michel
Re: ORA-28663 [message #549242 is a reply to message #549232] Thu, 29 March 2012 01:56 Go to previous messageGo to next message
ashishs
Messages: 40
Registered: May 2011
Member

Sir,

I create a user and give sysdba or sysoper privileges, what this may be the reason, so it connect as a sys schema.

Re: ORA-28663 [message #549249 is a reply to message #549242] Thu, 29 March 2012 02:31 Go to previous message
Michel Cadot
Messages: 59403
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Quote:
it connect as a sys schema


It connects as SYS ONLY is you tell it using "AS SYSDBA" option which is not the way to connect but for maintenance purpose.
If this user is not intend to do database maintenance then it should not have SYSDBA privilege.

Please CAREFULLY read the documentation about this role and its usage.

Regards
Michel
Previous Topic: How to edit created Security Policy (Virtual Private Database) (merged 2)
Next Topic: create user using java shell
Goto Forum:
  


Current Time: Mon Oct 20 13:07:50 CDT 2014

Total time taken to generate the page: 0.11153 seconds