ORA-28009: connection as SYS should be as SYSDBA or SYSOPER

Cause : connec tSY/Si s on lnoge ra avli dsytnax

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

Tr yconnec tSY/Sa s YSSDAB o rconnec tSY/Sa s YSSOEPR

update : 26-04-2017

ORA-28009 - connection as SYS should be as SYSDBA or SYSOPER
ORA-28009 - connection as SYS should be as SYSDBA or SYSOPER

  • ora-32142 : maximum number of iterations exceeded
  • ora-15081 : failed to submit an I/O operation to a disk
  • ora-01340 : NLS error
  • ora-00912 : input parameter too long
  • ora-22305 : attribute/method/parameter "string" not found
  • ora-07647 : sszfck: $OPEN failure
  • ora-12075 : invalid object or field
  • ora-00390 : log string of thread string is being cleared, cannot become current log
  • ora-00960 : ambiguous column naming in select list
  • ora-23438 : missing refresh group template
  • ora-01634 : rollback segment number 'string' is about to go offline
  • ora-24201 : duplicate publisher, publisher already added to the queue
  • ora-19801 : initialization parameter DB_RECOVERY_FILE_DEST is not set
  • ora-32051 : mapping service not available
  • ora-14262 : new subpartition name must differ from the old subpartition name
  • ora-12589 : TNS:connection not bequeathable
  • ora-06114 : NETTCP: SID lookup failure
  • ora-06546 : DDL statement is executed in an illegal context
  • ora-13120 : invalid face_id [string]
  • ora-14190 : only one ENABLE/DISABLE ROW MOVEMENT clause can be specified
  • ora-29850 : invalid option for creation of domain indexes
  • ora-01974 : Illegal archive option
  • ora-36706 : (XSRELTBL07) workspace object should be dimensioned by workspace object and one level dimension.
  • ora-40002 : wordsize must be string or greater
  • ora-22917 : use VARRAY to define the storage clause for this column or attribute
  • ora-13231 : failed to create index table [string] during R-tree creation
  • ora-29365 : parameters string and string cannot both be set
  • ora-09979 : skxfqhsnd: Error Sending a message to another endpoint
  • ora-30014 : operation only supported in Automatic Undo Management mode
  • ora-01031 : insufficient privileges
  • Oracle Database Error Messages

    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.