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 : 27-05-2017

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

  • ora-12628 : TNS:no event callbacks
  • ora-23609 : unable to find directory object for directory string
  • ora-30398 : illegal JOIN KEY clause
  • ora-01027 : bind variables not allowed for data definition operations
  • ora-27211 : Failed to load Media Management Library
  • ora-08462 : raw buffer contains invalid decimal data
  • ora-06028 : NETASY: unable to intialise for logging
  • ora-22162 : element at index [string] has been previously deleted
  • ora-38749 : A media recovery has been started.
  • ora-32155 : Anydata not specified
  • ora-38494 : column in the table alias and an attribute have matching names
  • ora-00401 : the value for parameter string is not supported by this release
  • ora-15166 : cluster in rolling downgrade from version [string] to [string]
  • ora-01951 : ROLE 'string' not granted to 'string'
  • ora-01622 : thread number must be specified - default not specific
  • ora-26030 : index string.string had string partitions made unusable due to:
  • ora-22801 : invalid object row variable
  • ora-22153 : source variable-length array is not initialized
  • ora-38453 : ExpFilter index should be created in the same schema as the base table.
  • ora-01269 : Destination parameter string is too long
  • ora-38474 : attribute set may not have attributes of TABLE COLLECTION type.
  • ora-19001 : Invalid storage option specified
  • ora-24757 : duplicate transaction identifier
  • ora-09750 : pw_attachPorts: port_rename failed.
  • ora-16735 : error executing dbms_logstdby.unskip_error procedure
  • ora-37100 : (XSUNCOMMITTED) You have one or more updated but uncommitted analytic workspaces.
  • ora-02477 : can not perform parallel direct load on object string
  • ora-39058 : current object skipped: string of type string
  • ora-12014 : table 'string' does not contain a primary key constraint
  • ora-38605 : FI not enough memory(stringK) for candidate generation(stringK)
  • 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.